Google has changed how Play Console calculates DAU, MAU and related engagement metrics to compensate for users who’ve opted out of data-sharing. Instead of simply excluding opted-out devices from the count, Play Console now estimates their activity and folds it back in — which means the DAU and MAU figures on your dashboard can move up or down purely because of a methodology change, with zero difference in actual user behaviour. Teams that don’t know this happened will see a jump or drop in engagement metrics and go looking for a cause that doesn’t exist.
This matters most for anyone running a longitudinal engagement dashboard, alerting on week-over-week DAU/MAU changes, or reporting these numbers to stakeholders as a proxy for product health. A compensation methodology change is a step function in the data series, not a trend, and any anomaly detection or historical comparison that treats it as one will generate false signals. It’s also a reminder that first-party platform metrics like Play Console’s aren’t a fixed ground truth — they’re computed values that can be redefined underneath you, which is exactly why running your own independent event tracking alongside store-provided numbers matters.
Data Points to Track
- Daily and monthly active user counts from your own analytics, computed independently of Play Console, so you have a second series to compare against when platform methodology shifts
- Opt-out rate for data-sharing, if your SDK can observe it, since a market or cohort with a high opt-out rate will see a larger compensation adjustment than one with low opt-out
- The date each Play Console metric definition last changed, sourced from Google’s release notes, kept as an annotation on your internal dashboards so a step change has an obvious explanation attached
- DAU/MAU ratio (stickiness) rather than raw counts alone, since a ratio computed consistently on both sides of a methodology change is more stable than either raw number
- Cohort-level retention curves, which are far less sensitive to a global compensation adjustment than aggregate DAU/MAU and give you a behaviour-based sanity check
Setup Steps
- Annotate your dashboards with the date Google’s opt-out compensation change took effect, so anyone reviewing historical DAU/MAU trends sees the methodology break rather than assuming it’s real.
- Run your own DAU/MAU calculation from first-party event data in parallel with Play Console’s, even if it’s a simpler unique-devices-per-day count, purely as a cross-check.
- Segment engagement metrics by market, since data-sharing opt-out rates vary significantly by region and regulatory environment, meaning the compensation effect won’t be uniform across your user base.
- Pause automated anomaly alerts on raw DAU/MAU for the period immediately around a known Play Console methodology change, and re-baseline afterward rather than let a step change trigger a false incident.
- Document the change in your internal metrics glossary so future team members interpreting a historical DAU chart know why a jump exists at a specific date with no corresponding product change.
Actionable Insights
If your Play Console DAU/MAU moved but your independent first-party count didn’t, the platform’s methodology is the explanation, not a real shift in engagement — stop the investigation there rather than searching for a phantom cause. If both numbers moved together, something in the product or market genuinely changed and the coincidence with Google’s announcement is just timing. And if your opt-out rate is notably higher in one market, expect that market’s Play Console numbers to be more volatile around any future compensation adjustment than markets with low opt-out — worth flagging before a regional team reacts to noise.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert