Google Play metrics library
Go to Play Console

Acquisitions

Grow users

Acquisitions on Google Play measure the number of successful user or device installations of your app in a given time period. They are driven by your brand and performance marketing efforts both on Play and beyond, and supported by Play's reach, distribution and discovery capabilities.

Key use cases

  • Closing the loop on marketing efforts: Breaking down acquisitions by traffic source allows you to distinguish between acquisitions driven by Play's discovery features (Explore), vs your investment in brand or advertising (Paid & direct), and other sources.
  • Measuring total distribution of your app on Play: The total number of acquisitions in a given time period reflects Play's reach and distribution capabilities.

When not to use acquisitions:

  • Measuring content performance on Play: For this you should use click and click-through-rate (CTR) metrics, not acquisitions because multiple content types can contribute to a single user acquisition. Install click and CTR metrics use indirect attribution to capture the full contribution of all content to a given acquisition.
  • Reconciliation with other platforms: Platforms outside Play, including Google Ads, can't track when an acquisition occurs, only when an app is opened. This is downstream of an acquisition and will not accurately reflect your actual acquisitions. Play tracks 'First opens.' Learn more about First opens.

User vs. device acquisitions

Acquisitions can be viewed by user or device:

  • User acquisitions: Users who installed your app and didn't have it installed on any devices at the time. This includes users who activate a new device where the app was preinstalled, or reactivated a device on which your app was installed. For example, a user acquisition isn't counted if a user has your app on their phone and installs it on their tablet or a new phone.
  • Device acquisitions: Devices on which users install your app for the first time. This includes initial activation of devices on which your app is preinstalled as well as reactivations.

We typically recommend using Device acquisitions as this captures new installs as well as when existing users install your app on a new device. It is also aligned with the way other platforms track installs.

Is it possible to have a device acquisition without a user acquisition?

Yes, a user may have multiple devices and is installing your app on another of their devices.

Is it possible to have a user acquisition without a device acquisition?

Yes, it is rare but possible to have a user acquisition without a device acquisition. An example of how this could happen is with a multi-user device, such as a TV or a tablet, where one user on the device may already have your app installed, but another user can also install it.

New vs. returning users and devices

Acquisitions can be further segmented by new and returning users:

User Device
New Users who installed, preinstalled, or reactivated your app for the first time Devices on which your app was installed, preinstalled, or reactivated for the first time
Returning Users who installed, preinstalled, or reactivated your app after having previously uninstalled your app from all their devices Devices on which your app was installed, or reactivated after having previously being uninstalled

Metrics

The metrics for tracking acquisition on Google Play are:

Metric (UI name) API name Definition
User acquisitions userAcquisition Users who installed your app and didn't have it installed on any devices at the time. This includes users who activated a new device, or reactivated a lapsed device, on which your app was installed. For example, a user acquisition isn't counted if a user has your app on their phone and installs it on their tablet or a new phone.
Device acquisitions deviceAcquisition Devices on which users install your app for the first time. This includes initial activation of devices on which your app is preinstalled as well as reactivations.
Incremental acquisitions from featuring (user-level only) N/A Users who installed your app due to featuring as a result of promotional content, who wouldn't have installed it otherwise. This is a statistical calculation that relies on comparing behaviour between an experiment and control group of users, where the control group was not exposed to featuring treatment.

See Appendix for information on legacy acquisition metrics, including Store listing acquisitions.

Dimensions

You can view acquisition metrics more granularly by breaking them down by dimensions.

Notes:

  • These dimensions are currently not available for incremental acquisitions metrics.
  • Device dimensions are attributed differently across metrics. E.g., user acquisition only attributes the first device on which the user installed the app. Daily active users attributes all devices on which the user engaged with the app.
Dimension (UI name) API name User acquisition specific dimension description Device acquisition specific dimension description
Country/region regionCode The country or region the user is based in at the time of acquisition.
Android version apiLevel The Android version on the device at the time of acquisition.
Device deviceModel The device model at the time of acquisition.
Form factor deviceType/FormFactor The form factor of the device at the time of acquisition
Language language The device's set language at the time of acquisition.
App version versionCode The app version on the device at the time of acquisition
Carrier N/A The device's mobile carrier or network at the time of acquisition
Acquisition mechanism acquisitionMechanism The method of acquisition (install, preinstall, reactivation). Learn more How the app was last acquired on the device. For example, by installation, preinstallation, or reactivation. Learn more
Traffic source trafficSource How the user initially discovered your store listing. For example by searching Google Play. Learn more How the app was discovered on device for your store listing. For example by searching Google Play. Learn more

Acquisition mechanism and traffic source

The Acquisition mechanism and traffic source dimensions can be used to find out where your acquisitions come from.

Acquisition mechanism options are:

  • Install - Users or devices that installed your app by searching or navigating to it.
  • Reactivation - Users or devices that have checked in with Play (a background process where your device connects to Google's servers) after having not checked in for more than 30 days. This can happen if a device is turned off and isn't used for more than 30 days (lapsed user/device) and is then turned back on and then used.
  • Preinstall - Users or devices that preinstalled your app on the device system image.
  • Peer-to-peer Install - Users or devices that installed your app via transfer from another device.

Traffic source options are:

  • Paid and direct - Acquisitions coming from an ad, referral, or search on Google Play containing your brand.
  • Google Play explore - Acquisitions from your app being discovered from browsing Google Play, without searching for it by name. This includes users who discovered your app on home pages, suggestions and top charts, or by searching for a category of apps, for example, 'racing game'.
  • Not attributed - We don't have enough information to attribute these acquisitions to the correct traffic source category. This includes reactivations and installs from Play backup and restore, where the traffic source for the original acquisition is not known, preinstalls, and instances where the traffic source was not recorded.

Common scenarios: When and how acquisitions are counted

The following are common scenarios to help explain the nuances of when a user or device acquisition is counted:

Multiple installs by the same user on different devices

If a user installs your app on multiple devices, they are only counted as a single user acquisition. Each install on a new device will count as a device acquisition.

Multiple family members create their own profiles on an Android TV

It's rare but possible to have a user acquisition without a device acquisition. For example, if a user with your app already installed on their phone, installs your app on a multi-user device, such as an Android TV.

A child is given a device from their parent

If a parent gives their child a device, where your app was already installed, and the child then creates their own phone profile and downloads your app, that will count as a user acquisition and not a device acquisition.

A user gets a smartwatch or tablet

If a user gets a smartwatch or a tablet and installs your app, while already owning a phone with the app installed, that will count as a device acquisition and not a user acquisition.

A user turns a device on after 30+ days

If a user doesn't use a device for 30 or more days and then turns on and uses that device, that will count as a Reactivation which counts as both a user acquisition and a device acquisition (if the user didn't use any other Android devices during that time). In the case of a reactivation, all apps on the device will log a reactivation.

Where can I find acquisition metrics in Google Play Console?

Acquisition metrics can be found in the following areas of Google Play Console:

  • Grow overview page - The Grow overview page is specifically tailored to show your app's growth on Google Play. This includes acquisitions and many more growth-related metrics. Grow users
  • Statistics page - The Statistics page can be used to view a number of metrics, including acquisition metrics. Statistics
  • Play Console app - You can choose to view acquisition metrics by using the Choose KPI screen.

Appendix: Past acquisition updates

Store listing acquisitions deprecation — Jul 29, 2026

Previously, Play reported Store listing acquisitions, a metric that measured acquisitions from users who clicked on the store listing to install. This metric was deprecated in favour of a new store listing install clicks metric.

Metric Status Description Notes
Store listing acquisitions Deprecated

This metric only exists on the Statistics page. It is being maintained for now.

Users who successfully acquired your app, whose last click was on Store listing

This metric was deprecated because it undervalues how much the store listing influences user intent and successful acquisitions.

It has two main limitations:

  1. It doesn't account for Store listing's role in multi-step acquisition journeys where store listings are viewed but not the last click
  2. It ignores install clicks if the acquisition was unsuccessful, even though this directly shows user intent
Store listing clicks (NEW Jul 2026) Maintained in Google Play Console. Coming to the API at a later date. Users who viewed your store listing during a session which resulted in an install click for your app This metric provides a full view of how Store listings contribute to acquisitions in multi-step journeys, directly reflects user intent, and is consistent with all other content performance metrics, allowing comparison across content types.