自5月7日起Google Play Console全应用数据异常的技术求助

Hey there, sorry to hear you're facing this frustrating data anomaly on Google Play Console starting May 7th—going from ~500 new/churned users to just 10-20 is definitely alarming. Let’s break down what you can check to figure out if this is a platform-wide issue or something specific to your app:

• Double-check your data filters first
  It’s easy to accidentally tweak the date range, app version, region, or acquisition channel filters on the stats page. Make sure you’ve selected "All" for versions, regions, and channels, and confirm the date range includes the pre-May 7 period for accurate comparison. Sometimes a tiny filter change can make data look way worse than it is.

• Cross-verify with other analytics tools
  If you use third-party analytics (like Firebase Analytics, or your own internal tracking) pull the same user acquisition data from there. If those tools still show your usual ~450-500 new users, then the problem is likely with Play Console’s data reporting itself. If they match the low numbers, then you’ll need to look into changes on your end.

• Check for platform-wide outages or unannounced changes
  Even if you didn’t see an official notice, head over to Google’s Play Developer Status Dashboard to see if there’s a reported issue with analytics or data processing. Sometimes platform bugs take a bit to be documented, and other developers might be reporting the same problem in the official Play Developer Community forums.

• Rule out your own app changes
  Think back to May 7 or the days leading up to it: did you push a new app update, adjust your marketing campaigns (like pausing ads), or modify any user tracking code (like install attribution or event logging)? Any of these could directly impact how Play Console counts your users.

• Reach out to Google Play Support if needed
  If you’ve checked all the above and still can’t pinpoint the issue, submit a support ticket through your Play Console. Include clear screenshots of the before/after data, your app’s package name, and details about when the anomaly started—this will help Google’s team investigate faster.

If you see other developers posting about the same May 7 data drop in community spaces, that’s a strong sign it’s a widespread platform issue, and you’ll just need to wait for Google to resolve it. Otherwise, focusing on your app’s recent changes should lead you to the root cause.

内容的提问来源于stack exchange，提问作者NullPointerException