Book a call

News · July 31, 2019

Google Play Console reworks its install and user metrics

// ios.news :: 2019

Google has rebuilt the core statistics in the Play Console, adding returning users, new install methods and flexible aggregation. Android teams get cleaner numbers to reconcile against their attribution and analytics tools.

What happened

  • According to the Android Developers Blog, the Play Console now offers core install and uninstall metrics by user and by device, and includes data on returning users and devices for the first time.
  • Google said the update adds install methods such as pre-installs and peer-to-peer sharing, lets developers aggregate and deduplicate metrics over periods that fit their business, and clarifies definitions such as acquisitions versus losses and events versus uniques.
  • New change analysis charts automatically highlight the largest movements in a period, and saved reports, suggested reports and CSV downloads are available, Google said, with benchmarks for core stats to follow.
  • Google had previewed the core metrics refresh at I/O in May, alongside peer benchmarking in Android vitals and planned curated peer sets for conversion and uninstall rates.

Why it matters

Store-side numbers rarely match what an MMP or product analytics tool reports, mostly because of different definitions of users, devices and re-installs. Having returning users and explicit definitions in the Play Console makes it much easier to explain the gaps instead of arguing about them.

We would use the change: agree on one definition of a new user across store, attribution and analytics, set up a saved report that matches it, and check it weekly against paid campaign data. Returning users are also worth tracking as a separate segment, since reactivation often hides inside paid install numbers.

Sources

This post is CMM’s own summary and commentary on publicly reported news. Facts are attributed to the sources linked above; please read them for full details. CMM is not affiliated with these publishers or with the companies mentioned, and trademarks belong to their owners. Prepared with AI assistance. Corrections or requests: [email protected]. See our editorial policy.

Want help with this?

Tell us what you need, and we will suggest the right team model on a short call.

Talk to us