You can access Google Play Console metrics through 2 different endpoints:

• Google Play Console - Store Performance returns Store Listing Visitors and Store Listing Acquisitions with a breakdown by acquistion channel
• Google Play Console - Organic Search returns organic keyword performance by providing Store Listing Visitors and Store Listing Acquisitions per keyword

Available history

We fetch historical data up to February 2020.

Update frequency

Based on the email AppTweak e-mail address that you have invited on your Google account you will have different update frequencies. Go to your Google Play Console and go on the section "Users and permissions" on the left menu to find back the AppTweak email address you've invited. You can refer to the following table to find the correspondance between the update frequency and the email address:

Delay in the Data

You may notice a couple of days' delay between today and the last registered data point. Two different reasons may cause this:

• Google has not yet provided the data for the most recent date (most common), or
• AppTweak has not yet fetched the data.

Delay due to Google
Google never provides the data until today, there is usually a 3-day difference between the last available data in the console and today. This delay can sometimes be longer.

Delay due to AppTweak

Extra delay can be expected depending on the email used for the integration (see Update Frequency).

Moreover for Goole Play Console - Organic Search we have seen that such data changes a lot over its first days. Therefore, we have decided to wait 6 days before tracking the data, giving it sufficient time to stabilize.

Google Play Console - Store Performance

Understanding the metrics

Google Play Console now reports store listing performance with two sets of metrics, and this endpoint returns both:

1. New metrics (console group: Store listing performance): Visitors (installs) and Unique user install clicks. Unique user install clicks counts the moment a user taps Install, whether or not the download finishes. These metrics replace the legacy ones in the console.
2. Legacy metrics (console group: Legacy Store listing performance): Store listing visitors and Store listing acquisitions. Store listing acquisitions counts a completed install.

API field ↔ Google Play Console metric

📘

Two "visitors" metrics

install_visitors and visitors have the same definition, but Google computes them in two separate reports, so their values differ. Always use install_visitors with unique_user_install_clicks, and visitors with acquisition.

New and returning users

Each metric above is also returned with a _new and a _returning suffix (e.g. install_visitors_new, acquisition_returning). These match the user type filter in the console:

* Legacy _new and _returning metrics may only be available from December 2024 if your integration was completed before that date. For integrations from January 2025, data is available from February 25, 2020 onward.

Channels

Use the channels query parameter to choose which traffic sources to return. If you don't pass it, all channels are returned. Each channel is returned as its own key in the response, under app and country.

Computing rates

Use the matching user type on both sides (e.g. unique_user_install_clicks_new / install_visitors_new for new users).

🚧

Don't mix the two sets

Do not divide unique_user_install_clicks by visitors, or acquisition by install_visitors. Expect the click-through rate to be higher than the legacy conversion rate: more users tap Install than complete the download.

Where to find these metrics in your Google Play Console

Legacy Store Listing Visitors visitors or Store Listing Acquisitions acquisition can be found in the App Statistics of your Google Play Console under Legacy store listing performance section.

To compare your data with the data from the API, make sure to filter out for a specific country.

Visitors (installs) install_visitors and Unique user install clicks unique_user_install_click can be found in Store Listing performance section of the App Statistics page of your Console.

📘

Inconsistent data

Google regularly updates console data retroactively. This can cause differences between the API and the console for the most recent dates. They are resolved the next time we fetch the data.

Response format

The response for the playstore performance report request will be a JSON which contains all the info related to the google play console, without pagination. This information is organized by app, country and then channel. Both "Store Listing Visitors" and "Store Listing Acquisitions" are returned in the response.

{
  "result": {
    "dummy.app.com": {
      "us": [
        {
          "search": {
            "start_date": "2026-10-01",
            "end_date": "2026-10-02",
            "visitors": [4955, 4610],
            "visitors_new": [4004, 3720],
            "visitors_returning": [951, 890],
            "acquisition": [1488, 1352],
            "acquisition_new": [941, 860],
            "acquisition_returning": [547, 492],
            "install_visitors": [3043, 2875],
            "install_visitors_new": [1999, 1890],
            "install_visitors_returning": [1044, 985],
            "unique_user_install_clicks": [2188, 2040],
            "unique_user_install_clicks_new": [1300, 1215],
            "unique_user_install_clicks_returning": [888, 825]
          },
          "all": {
            "start_date": "2026-10-01",
            "end_date": "2026-10-02",
            "visitors": [16550, 15420],
            "visitors_new": [14259, 13300],
            "visitors_returning": [2291, 2120],
            "acquisition": [4743, 4410],
            "acquisition_new": [3150, 2930],
            "acquisition_returning": [1593, 1480],
            "install_visitors": [15131, 14205],
            "install_visitors_new": [10894, 10230],
            "install_visitors_returning": [4237, 3975],
            "unique_user_install_clicks": [7111, 6680],
            "unique_user_install_clicks_new": [4484, 4210],
            "unique_user_install_clicks_returning": [2627, 2470]
          }
        }
      ]
    }
  },
  "metadata": {
    "request": {
      "path": "/api/public/integrations/accounts/android/store-analysis",
      "params": {
        "start_date": "2026-10-01",
        "end_date": "2026-10-02",
        "id": "{api-account-id}",
        "apps": ["dummy.app.com"],
        "countries": ["us"],
        "channels": ["search", "all"]
      },
      "cost": 1,
      "max_credit_cost": 1,
      "status": 200
    },
    "response": null
  }
}

Google Play Console - Organic Search

The Organic Search endpoint returns the search terms that brought users to your store listing, for any connected app, over the requested date range. For each search term, you get daily visitor and install metrics, split by traffic source (Google Play search vs. Google Play explore).

Understanding the metrics

Google Play Console now reports store listing performance with two sets of metrics, and the API returns both:

1. New metrics (console group: Store listing performance): Visitors (installs) and Unique user install clicks. Unique user install clicks counts the moment a user taps Install, whether or not the download finishes. These metrics replace the legacy ones in the console.
2. Legacy metrics (console group: Legacy Store listing performance): Store listing visitors and Store listing acquisitions. Store listing acquisitions counts a completed install.

❗️

Keyword coverage is very different between the two sets

• New metrics (install_visitors, unique_user_install_clicks) are available for all keywords, in every country.
• Legacy metrics (visitors, installs) are only available for the top 50 keywords globally.

As a result, most keywords in the response will have values for the new metrics and null for the legacy ones. For keyword analysis, we recommend using the new metrics.

API field ↔ Google Play Console metric

📘

Two "visitors" metrics

install_visitors and visitors have the same definition, but Google computes them in two separate reports, so their values can differ. Always use install_visitors with unique_user_install_clicks, and visitors with installs.

Note: this endpoint uses installs for Store listing acquisitions, while the Store Performance endpoint uses acquisition for the same console metric.

Traffic sources

Each metric is also returned with a _search and an _explore suffix (e.g. install_visitors_search, installs_explore). These match the traffic source filter in the console:

The total (no suffix) is usually close to _search + _explore, but not always strictly equal, because Google computes each value separately.

Computing rates

Use the matching traffic source on both sides (e.g. unique_user_install_clicks_search / install_visitors_search for search).

🚧

Don't mix the two sets

Do not divide unique_user_install_clicks by visitors, or installs by install_visitors. Expect the click-through rate to be higher than the legacy conversion rate: more users tap Install than complete the download.

null vs 0

• 0 means Google reported no activity for that keyword, traffic source and day.
• null means Google returned no value. Most often, this is because the keyword is not in the top 50 keywords globally, so the legacy metrics are not available for it. It can also happen when the volume is too low to be reported, or for dates before Google introduced the new metrics.

Where to find these metrics in your Google Play Console

You can simply find the same metrics in your own Console by setting the breakdown by Search term.

Input parameters

You can find all the required and optional query parameters in the "QUERY PARAMS" section of the endpoint definition.

Response format

The response is a JSON object without pagination, grouped by app, then country, then keyword. Each metric is an array with one value per day; the first entry corresponds to start_date.

{
  "result": {
    "dummy.app.com": {
      "BE": {
        "puzzle game": [
          {
            "start_date": "2023-05-09",
            "end_date": "2023-05-10",
            "visitors": [23, 19],
            "visitors_search": [19, 15],
            "visitors_explore": [4, 4],
            "installs": [3, 4],
            "installs_search": [3, 3],
            "installs_explore": [0, 1],
            "install_visitors": [25, 20],
            "install_visitors_search": [21, 16],
            "install_visitors_explore": [4, 4],
            "unique_user_install_clicks": [4, 5],
            "unique_user_install_clicks_search": [3, 4],
            "unique_user_install_clicks_explore": [1, 1]
          }
        ],
        "word game": [
          {
            "start_date": "2023-05-09",
            "end_date": "2023-05-10",
            "visitors": [null, null],
            "visitors_search": [null, null],
            "visitors_explore": [null, null],
            "installs": [null, null],
            "installs_search": [null, null],
            "installs_explore": [null, null],
            "install_visitors": [110, 72],
            "install_visitors_search": [94, 63],
            "install_visitors_explore": [16, 9],
            "unique_user_install_clicks": [25, 16],
            "unique_user_install_clicks_search": [22, 14],
            "unique_user_install_clicks_explore": [3, 2]
          }
        ]
      }
    }
  },
  "metadata": {
    "request": {
      "path": "/api/public/integrations/accounts/android/organic-search.json",
      "params": {
        "start_date": "2023-05-09",
        "end_date": "2023-05-10",
        "id": "{api-account-id}",
        "apps": ["dummy.app.com"],
        "countries": ["be"]
      },
      "cost": 1,
      "max_credit_cost": 1,
      "status": 200
    },
    "response": null
  }
}

FAQs

How do I fetch Store Listing Visitors and Acquisitions for an app from Google Play Console via API?

Use AppTweak's Google Play Console - Store Performance endpoint (GET /accounts/android/store-analysis). It returns daily arrays per app, country and channel for two sets of metrics: Google's new metrics (install_visitors, unique_user_install_clicks) and the legacy ones (visitors, acquisition). Each metric also has _new and _returning splits for new versus returning users. Required parameters are id (the integrated account) and apps; countries, channels, start_date and end_date are optional and default to all countries, all channels, and the 90 days ending yesterday.

What's the difference between the new and the legacy Google Play Console metrics?

Google now reports store listing performance with two sets of metrics, and AppTweak's API returns both. The new metrics, in the console's Store listing performance group, are Visitors (installs) and Unique user install clicks, returned as install_visitors and unique_user_install_clicks. The legacy metrics, in the Legacy Store listing performance group, are Store listing visitors and Store listing acquisitions, returned as visitors and acquisition (Store Performance) or installs (Organic Search). You can see both groups in the Statistics section of your Google Play Console. Google is replacing the legacy metrics with the new ones in the console.

What's the difference between unique user install clicks and store listing acquisitions?

Unique user install clicks count the tap on Install; store listing acquisitions count a completed install. A user who taps Install but whose download fails or is cancelled counts as an install click, not an acquisition. As a result, unique_user_install_clicks is usually higher than acquisition / installs, and the install click-through rate (unique_user_install_clicks / install_visitors) is higher than the legacy conversion rate (acquisition / visitors).

Why are there two visitors metrics, install_visitors and visitors?

Each one belongs to a different set of Google Play Console metrics. install_visitors is "Visitors (installs)" from the new metrics and goes with unique_user_install_clicks. visitors is "Store listing visitors" from the legacy metrics and goes with acquisition / installs. Both count users who visited your store listing without already having your app installed, but Google computes them in separate reports, so the values differ. To compute a rate, always divide by the visitors metric from the same set.

How do I break down Google Play store visitors by acquisition channel?

Use the channels parameter on the Store Performance endpoint. Pass one or more of search (Google Play search), explore (Google Play explore), referrals (third-party referrals) or all; if you leave it out, all channels are returned. Each channel comes back as its own key in the response, nested under app and country, with the full set of new and legacy metrics. A single call can therefore return search and explore side by side, without separate requests per channel.

How do I retrieve which keywords are driving organic installs on Google Play via API?

Use AppTweak's Google Play Console - Organic Search endpoint (GET /accounts/android/organic-search.json). It groups results by app, country and keyword, and returns daily arrays of install_visitors and unique_user_install_clicks (new metrics, available for all keywords in every country). It also returns visitors and installs (legacy metrics, available for the top 50 keywords globally only). Each metric is also split by traffic source with the _search and _explore suffixes. Required parameters are id and apps; countries, start_date and end_date are optional, with start_date defaulting to 90 days ago.

Why are visitors and installs null for most keywords in the Organic Search endpoint?

Google only provides the legacy Store listing visitors and acquisitions for the top 50 keywords globally. Any keyword outside that top 50 returns null for visitors and installs, but usually has values for install_visitors and unique_user_install_clicks, which Google provides for all keywords in every country. For keyword-level analysis, use the new metrics.

What's the difference between the Store Performance and Organic Search endpoints?

Store Performance returns overall visitors and installs per channel; Organic Search breaks organic traffic down per keyword. Store Performance splits traffic into search, explore, referrals or all, with new and returning user splits, but only at the channel level. Organic Search covers organic traffic only (Google Play search and Google Play explore) and returns one series per keyword, so you can see which search terms brought visitors and installs, not just how many came from search overall.

Why don't the API values match my Google Play Console for recent dates?

Google updates console data retroactively, and AppTweak waits before fetching some data. Google usually provides data with about a 3-day delay, and can revise recent values afterwards; differences are resolved the next time we fetch the data. For the Organic Search endpoint, we also wait 6 days before tracking the data so it has time to stabilize. Your update frequency also depends on which AppTweak email address you invited in your Google Play Console (see Update frequency).

Who can pull first-party Google Play Console data through the API?

Google Play Console data is available only on AppTweak's Unlimited API plans, not on the low-touch Small, Medium, or Large tiers. This applies to both the Store Performance and Organic Search endpoints. Within Unlimited, the Unlimited Analytics API (tied to an ASO Enterprise subscription) covers reporting and monitoring use cases; building software on this data, or reselling it, requires the separate, higher-tier regular Unlimited API.