NETICE DOCUMENTATION
Google Play reporting access setup
Reviewed
Netice reads Google Play revenue reports from the private reporting bucket associated with your Play Console account. Setup needs two things: access for a service account to the required Play reports, and the correct reporting bucket. Configure the output destination separately.
Daily App Sales reads Estimated Sales; Platform Finance reads Earnings; Google Play Raw Reports syncs the selected provider-native exports. Choose the workflow before granting access so the first verification tests the report family you will actually use.
1. Find the Play reporting bucket
- Open the correct developer account in Play Console.
- Go to Download reports → Financial and locate the relevant report section.
- Use Copy Cloud Storage URI. The source bucket begins with
pubsite_prod_rev.
Google documents the location in its monthly report export instructions. This bucket is the Google Play source, not the GCS bucket or S3 bucket where you want Netice to write output.
2. Grant read access to the reporting identity
If your Netice connection flow provides a managed Google Play identity, follow that flow and grant access to the identity it displays. For the uploaded-credential path, create a dedicated service account in your Google Cloud project and obtain its JSON key through your organization’s approved process.
- In Play Console, open Users and permissions and invite the service-account email associated with the Netice connection.
- Under account-level permissions, enable View app information and download bulk reports (read-only).
- Grant the account-level financial-data permission needed to download Estimated Sales or Earnings. Google calls the account-level permission View financial data, orders, and cancellation survey responses; the report guidance requires financial access to be global.
- Save the invitation and permissions. Confirm that any access-expiry date matches the intended recurring operation.
Use Google’s permission definitions to distinguish account-level bulk-report access from app-only visibility. These are read permissions; release management, store editing and order-management actions are not required for report ingestion.
3. Configure the source in Netice
- Create the appropriate Daily App Sales, Platform Finance or Google Play Raw Reports task.
- Under Choose Google Play access, select a saved connection or set up new access.
- For the uploaded-credential path, provide the JSON key in Google Service Account Key (JSON). Its service-account email must match the account you granted access to in Play Console.
- Enter the reporting bucket in the field shown. Daily/finance setup can label this Google Play Pubsite Number/Bucket Suffix; Raw Reports uses Google Play reports bucket. Use the bucket identity, not a particular monthly report object’s path.
- For Raw Reports, choose the recommended bundle or the exact report families you need. A saved reports bucket can be reused; check it before overriding it for the task.
Save the connection for recurring use. It remains dependent on the Play Console permissions of its reporting identity; saving access cannot make an unpublished report available.
4. Set destination access independently
Google Play source access does not grant write access to your BigQuery dataset, Snowflake schema, GCS bucket or S3 bucket. Choose a saved or new destination connection and verify the target used by this task.
Managed Google Play access is source-only. If you deliberately reuse an uploaded service-account JSON for a Google Cloud destination, that identity also needs the destination permissions, and Netice’s explicit reuse option must be enabled. The simpler separation is a source reporting identity and a dedicated destination connection.
5. Verify a published period before expanding history
For daily analysis, start with a recent day allowing for Google’s reporting delay. For finance, choose an Earnings month that already exists in Play Console. For raw output, the Quick test history preset checks a small set of eligible report months. Review the resulting task status and destination before requesting a larger backfill.
| Symptom | Check |
|---|---|
| Report access is denied | The exact service-account email invited in Play Console, account-level bulk and financial permissions, and access expiry. |
| The source bucket cannot be found | The bucket copied from the selected developer account. Do not enter the customer-owned destination bucket here. |
| Estimated Sales exists; Earnings is missing | The selected Earnings month, publication timing and financial-report access. Test Earnings directly rather than relying on a daily-sales success. |
| Recent transactions are absent | Provider processing delay and the recurring refresh window; the monthly source file can be updated after the first read. |
| Source read succeeds; delivery fails | Destination credentials, selected target and write permissions. |
See Estimated Sales versus Earnings for report timing and field interpretation, and backfills and reruns for ongoing operation.
Keep reporting access revocable
Manage recurring access through saved connections. Update or replace the saved credential when rotating a customer-managed key. Removing a Netice connection does not remove the service account’s Play Console permission; revoke that permission separately when access should end.