Google Play

For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.

Prerequisites

A Google Play account with Owner permissions on at least one application.
The Google Cloud Storage bucket ID, where all the Google Play reports are stored.
The read-only permission on the required reports and GCS buckets. Read Cloud Storage Authentication.

Note: Reports available in a GCS bucket have the same access and restrictions to data access as your Google Play account. Therefore, to retrieve the reports from the GCS bucket, you must have Owner access to view the report in your Google Play dashboard.

Configuring Google Play as a Source

Note: You need to create separate Pipelines for every app hosted on the Google Play Store.

Perform the following steps to configure Google Play as the Source in your Hevo Pipeline:

Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Google Play.
In the Configure your Google Play Account page, click + ADD GOOGLE PLAY ACCOUNT.
In the Sign in with Google dialog, select the Google Play account to log in to.
Click Allow to enable Hevo to access your Google account to read the reports data for the applications within this account.
In the Configure your Google Play Source page, specify the following:
- Pipeline Name: A unique name for the Pipeline.
- Bucket ID: ID of the bucket that holds the reports, which you retrieved from Google Play.
  
  All the reports available in the selected bucket are listed under different heads in the adjacent Reports drop-down.
- Reports: Modify the selection, if needed. By default, all reports are selected.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.

Retrieving the Google Cloud Storage Bucket ID

Sign in to your Google Play account. You can see all the Google Play applications configured within your account.
In the left navigation pane, under Game services, click Download Reports.
In the right pane, click in the Select an app field and select the relevant application name.
Scroll to the end of the page to the Direct Report URIs section and copy the bucket ID. Your bucket ID begins with pubsite_prod_. For example: pubsite_prod_1234567898765432100.

Data Replication

Historical Data: The first run of the Pipeline replicates all existing data for the selected Reports to the Destination data warehouse.

Incremental Data: Google uploads new records once daily to your report. Once the historical records are replicated, you can define the frequency at which you want to ingest the incremental changes. To do this:

Click the icon in the Pipeline Summary.
Select a schedule between 3 hrs to 72 hrs. Google refreshes the records once every 24 hrs. Therefore, we recommend a setting of 24 hrs.

Data Refresh: Google Play does not support data refresh. However, Hevo allows you to reload a report starting from a specific month. For each report that you need to refresh:

Click the icon next to the report.
Click Change Position.
Select the Month and Year to load the report from and click Update. The object is queued to be re-ingested. Note: Any report data earlier than the month you select is left as is and not wiped out during the refresh.

Data Model

The following is the complete list of reports available on Google Play.

Note: The financial reports, Estimated Sales, Earnings, and Rewarded Products, include all applications within the account. If you have multiple Google Play Store applications, you can choose to include Financial reports in only one of them to avoid ingestion of same data multiple times.

Detailed Reports

No.	Report Type	Report Name	Description
1	Financial	Estimated Sale	Contains in-app product or subscription sales before deducting taxes or Google fees from the totals.
2	Financial	Earning	Contains previous months’ payouts and transactions such as Charges, and Google Fee in original, and converted amounts against invoices.
3	Financial	Rewarded Product	Contains earnings and the number of products claimed, broken down by date and product.
4	Reviews & Subscription	Cancellation Survey Response	Contains subscription cancellation data.
5	Reviews & Subscription	Reviews	Contains app reviews posted on Google Play Store.

Aggregate Reports

Aggregated reports can be viewed across multiple dimensions. Read Commands & file formats for aggregated reports

No.	Report Type	Report Name	Description
1	App Statistics	Crashes	Get daily app crash analytics data across the following dimensions: - App Version Code - Device - Android OS Version
2	App Statistics	Installers	Get detailed daily app installation analytics across the following dimensions: - Acquisition Channel - Country - Country (Play Store organic) - Play Store (organic) Search - Tracked Channels (UTM)
3	App Statistics	Ratings	Get app ratings data across the following dimensions: - App Version Code - Carrier - Country - Device - Language - Android OS Version
4	App Statistics	Subscription	Get app subscription analytics across the following dimensions: - Country - Device
5	User Acquisition	Buyers	Get daily app buyer analytics across the following dimensions: - Acquisition Channel - Country - Country (Play Store organic) - Play Store (organic) Search - Tracked Channels (UTM)
6	User Acquisition	Installs	Get daily app Installation analytics data across the following dimensions: - App Version Code - Carrier - Country - Device - Language - Android OS Version

Schema and Primary Keys

A column __hevo_id representing a unique ID for Source data is added to all reports.

Primary Keys

The primary keys of each report object are derived as follows:

Detailed Reports: Hash of report name and row number. The row number prevents Hevo from loading duplicates in case the same records are ingested multiple times.
Aggregated Reports: Hash of field values for Date, Package Name and the corresponding dimension.

Limitations

None.

Revision History

Refer to the following table for the list of key updates made to this page:

Date	Release	Description of Change
May-05-2021	1.62	Updated the schema to include the columns, `_hevo__source_file_name` and `__hevo__source_file_row_number` in all objects.

Last updated on 19 Jan 2022