Connect Google Play Data to Revenue Sensor for Revenue Reporting
Sign in with Google, pick your apps, and paste your Play financial reports URI so real revenue can be imported.
Google Play needs two things: a Google sign-in with access to your Play Console, and the Cloud Storage URI where Google writes your financial reports. Refunds arrive from the sign-in alone, but real in-app purchase revenue only exists in those reports, so the setup asks for the URI before it finishes. In the console this source is called Google IAP.
Before you begin
- A Google account that is a Play Console user with permission to view app information and to view financial data. Without financial data access, the Financial reports page does not appear at all.
- Nothing to create in Google Cloud: no project, service account or key file is needed.
Sign in and pick your apps
- 1
Start the connection
Integrations → Google IAP → Connect in the Revenue Sensor console, then click Connect on the Authorize step and sign in with the Google account you use for the Play Console.
- 2
Approve read-only access
On Google's consent screen, approve access to view app information, purchases and subscriptions, and your financial reports in Cloud Storage. Revenue Sensor never changes releases or billing.
- 3
Pick your apps
Choose the apps you want to sync. Each app becomes a row in your revenue reports.
Add the Cloud Storage URI
- 1
Open the financial reports
In the Play Console sidebar, expand Download reports and click Financial.
- 2
Copy the right URI
Scroll to Estimated sales reports and click Copy Cloud Storage URI next to that heading. Do not use the button under Korean Play balance funded reports: it points at a different bucket with no sales data.
- 3
Paste it exactly
On the Revenue step, paste the value as copied (it looks like gs://pubsite_prod_ followed by a long number), with no trailing slash or folder, and click Save & continue. We check it against Google before saving.
More than one developer account
Each Play developer account has its own bucket. Add one URI per developer account under the account's Config tab → Revenue buckets.
Final Play revenue lags by four to five weeks
Google publishes the final earnings report once a month, after the month closes, so final revenue lags up to four to five weeks. Until then the current month is filled from Google's provisional sales report, which Google updates during the month, and is replaced by the final figure when the earnings report lands. Refunds arrive in near real time.
What gets imported
| Field | Notes |
|---|---|
| Revenue | The Charge and Charge refund amounts from the monthly earnings report, per app and country. Months without an earnings report yet use the provisional sales report. |
| Refunds | Voided purchases (refunds and chargebacks) from the Play Developer API, in near real time. |
| Buyer tax | Taken from the sales report and stored separately, so you can include or exclude it with the revenue basis. |
| Google fee | Stated in the earnings report, so the Payout basis can take it off. A month without an earnings report yet reads before the Google fee. |
Troubleshooting
- “Revenue needs your Play reports bucket”: no Cloud Storage URI is saved, so only refunds sync. Add the URI on the account's Config tab.
- “Play reports bucket not found”: the saved URI is wrong or this login cannot read it. Check the URI on the Config tab.
- “N apps not found in your Play reports”: those apps belong to another developer account. Add the Cloud Storage URI of the account that owns them.
- “Google Play won't share financial reports”: the login was refused access to the reports. Reconnect and grant access to financial reports.
- Nothing yet for a brand-new developer account: Google may not have published any report yet. Revenue fills in on the next publish.