Google Play revenue to BigQuery

Netice delivers Google Play revenue data into your BigQuery dataset using separate workflows for Estimated Sales and Earnings. Choose Daily App Sales for daily operational estimates, or Platform Finance for monthly Earnings events. Both can coexist with separate table contracts.

Connect the report bucket, not just an app

Google Play financial exports live in the Play Console reporting bucket. The source connection needs access to those reports; access to your destination dataset alone is insufficient. Follow Google Play reporting access setup, then configure the BigQuery destination and staging bucket.

1. Verify the reporting bucket and financial-report permissions for the source identity.
2. Select Daily App Sales or Platform Finance in Netice.
3. Choose the customer-owned BigQuery dataset, output table and reporting currency.
4. Start with a period for which the relevant provider report is available.
5. Inspect the first rows and quality fields, then enable recurring refresh.

Estimated Sales: daily activity inside monthly files

Google adds recently charged or refunded activity to monthly Estimated Sales exports. A file can change after the date of the underlying activity. A successful read today therefore does not prove that every transaction for yesterday has arrived.

Netice’s daily output uses revenue_date and exposes report-currency estimates with their methods. The recurring date window allows recent reporting to be refreshed. If you discover an older correction outside that window, select the relevant historical rerun.

Earnings: retain the event ledger

In Platform Finance, Google Earnings fees, taxes and adjustments remain separate events. native_net_proceeds holds the signed merchant-currency amount for the event; report_net_proceeds holds the corresponding converted amount when available.

A query that filters to event_type = 'SALE' before summing proceeds discards other financial events. Group the complete relevant event set by reporting period and currency, and count missing amounts alongside the total. Do not multiply these proceeds by quantity; Google Earnings quantity is unavailable in this contract.

Explore Google Earnings example rows and BigQuery SQL to see how signed fee, tax and adjustment events contribute to finance proceeds.

Keep report month separate from transaction date

The Earnings report month and a row’s transaction date answer different questions. Netice preserves period and date-basis fields so you can choose the intended grouping. Do not assign every row to a calendar month by casting one convenient timestamp.

The Google Play report-family reference covers source currencies, timing and date conventions. Use the finance dictionary and SQL examples for downstream modeling.

Check source availability before debugging SQL

When rows are absent, first verify that the selected source report exists and the connection can read it. Then check the requested period, destination run outcome and table selection. A missing report, failed delivery and true zero revenue are different states.