Google Play Developer
API Documentation: Google Play Developer API Documentation
The Google Play Developer Reporting API provides access to key app performance metrics, including crash rates, ANRs, and other vitals. It lets you generate custom reports to monitor technical quality and user experience over time.
Source Setup Guide
Click in the Edit Source form to the left.
Step 2
Follow the authentication flow (OAuth) on Google’s website to grant Extract the required permissions.
Step 3
Confirm you can see your email and profile picture, and that the source is Connected.
Step 4
Create your custom reports
This connector supports custom reports only, in accordance with the limitations of the Google Play Developer Reporting API.
To create a custom report:
- Enter a report name.
- Select your desired metric set and dimensions.
- Click Save to finish.
Each metric set is compatible with specific dimensions only. To see which dimensions are supported for each metric set, refer to Google’s official documentation.
Store listing reports: If you use the storeListingMetricSet, Google may not have data available up to “yesterday” for validation and syncing. Extract automatically queries the latest available end date for this metric set.
Data Streams
This connector syncs Google Play Developer Reporting data. It exposes the following streams:
- apps: A list of apps available in the Google Play Developer account (includes
package_nameanddisplay_name). - reports: Daily reporting rows for each app and selected metric set. Each row includes:
date(the start date of the daily aggregation period)app_id(the app package name)- Zero or more dimension fields (when dimensions are requested). Dimension fields are emitted as:
<dimension>_string_value<dimension>_value_label(when provided by the API)
- One or more metric fields (as returned by the API for the selected metric set)
If no dimensions are configured for a report, the connector omits the dimensions parameter in the API request and returns only the date/app identifiers plus metrics.
For the storeListingMetricSet metric set, the connector supports the following dimensions:
trafficSourcesearchTermutmSourceutmCampaignstoreListinglanguageCoderegionCodecustomAudience