Google Play Console just shipped its biggest analytics overhaul in years: the traditional “acquisitions” metric on the store-listing performance page has been replaced with click-based metrics, alongside a new lifecycle overview page and Gemini-generated chart explanations bolted onto the Statistics page. For most product and ASO teams, the immediate problem isn’t the new metric itself — it’s that historical trend lines built on the old methodology don’t line up with the new one. A dashboard that showed a steady acquisition curve last month can show a step change this month that has nothing to do with actual install performance and everything to do with how Google now counts a click.
This is the kind of change that quietly invalidates month-over-month and year-over-year comparisons unless someone flags exactly when the methodology shifted. Teams that don’t track the cutover date end up debugging a “sudden acquisition drop” that’s actually just two incompatible metrics stitched into one chart. And because Gemini’s auto-generated explanations on the Statistics page will happily narrate whatever the chart shows, a methodology break can get explained away with a plausible-sounding but wrong story — “engagement dropped in this region” — instead of the real cause, which is that the metric definition changed underneath the data.
Data Points to Track
- Metric definition version, tagging every acquisition data point with which methodology (legacy acquisitions vs. click-based) produced it, so historical charts can be split rather than silently blended
- Cutover date marker, recording the exact date Play Console switched your account to click-based metrics, since Google’s rollout isn’t simultaneous across all developers
- Click-to-install conversion rate under the new definition, tracked separately from the old acquisition-to-install rate so the two aren’t compared as if they measure the same funnel stage
- Store-listing page view vs. click delta, since the new methodology’s emphasis on clicks changes what counts as a meaningful listing interaction versus a passive impression
- AI-generated insight accuracy spot-checks, logging cases where Gemini’s auto-explanation on the Statistics page was verified against raw data versus taken at face value
Setup Steps
- Snapshot your last full month of legacy acquisition data before Play Console fully migrates your account, so you retain a clean pre-change baseline.
- Record the exact cutover date the new click-based metrics went live for your app, and store it alongside your analytics pipeline’s metadata, not just in a memo.
- Split all historical acquisition dashboards at the cutover date rather than plotting old and new methodology as one continuous line.
- Re-baseline alerting thresholds for acquisition metrics, since a threshold tuned to the old definition will misfire against click-based numbers that move differently.
- Establish a manual review habit for Gemini-generated Statistics explanations, spot-checking any insight that will inform a budget or roadmap decision against the underlying raw numbers.
Actionable Insights
Treat this as a metric-definition change, not a performance change, until you’ve confirmed otherwise. The single highest-value action is tagging the cutover date and refusing to let any dashboard plot legacy and click-based acquisitions as one unbroken trend line — that one habit prevents most of the false alarms and false confidence this kind of methodology shift causes. Once the split is in place, the new click-based view is genuinely more precise about store-listing intent than the old acquisitions metric was, but only for teams that didn’t let the AI-generated narrative paper over the seam.
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