NETICE DOCUMENTATION
Apple App Store revenue to BigQuery
Reviewed
To analyze Apple App Store revenue in BigQuery with Netice, connect App Store Connect reporting access, choose Daily App Sales or Platform Finance, and deliver the output into your own dataset. Daily Summary Sales powers operational trends; Apple finance reports power the separate monthly finance output.
This guide is for revenue reporting. Apple reviews are a different source family and do not become revenue rows in the daily or finance tables.
Choose the Apple report family
| Your question | Netice workflow | Apple-specific check |
|---|---|---|
| Daily sales by app, country and currency | Daily App Sales | Summary Sales amounts can be per-unit inputs; normalized amounts incorporate signed units. |
| Proceeds for a finance period | Platform Finance | Apple uses fiscal periods; preserve the report’s start and end dates. |
| Apple source columns for your own transformations | Raw Reports to object storage | Native artifacts have their own contract, separate from normalized BigQuery tables. |
Inspect an Apple daily-sales example in BigQuery to see signed sales and refunds alongside net_method.
Configure the pipeline
- Prepare the App Store Connect API key and vendor access. Finance access must match the vendor/report scope.
- Prepare your BigQuery dataset and GCS staging destination.
- Create the chosen workflow with Apple as a source. Select the reporting currency and available historical scope.
- Run a bounded window. Check report dates, source family, identifiers and currencies in the delivered table.
- Enable recurring refresh and schedule downstream transformations after successful delivery.
Interpret Apple daily proceeds correctly
Customer currency and developer-proceeds currency can differ. In Netice Daily App Sales, native_currency is not a promise that every Apple monetary input used that currency. Separate apple_proceeds_currency and apple_proceeds_native fields retain the proceeds context.
A local component can be null when its currency differs from the row’s selected native currency. Report-currency estimates have their own method fields. See the currency reference before joining these fields to an exchange-rate table or comparing them with the App Store Connect interface.
Check refunds and reporting dates
Do not remove negative rows merely because they lower a total. Refund direction and signed units are part of reporting semantics. Also avoid treating Summary Sales as a complete transaction-level order ledger: the provider can aggregate activity.
For monthly finance, group by fiscal_period when reconciling the source report. Use transaction or effective revenue dates only when your model intentionally changes the attribution basis. The Apple report-family reference explains the difference.
Plan history before reports expire
Apple limits downloadable Sales and Trends history. A Netice backfill cannot recreate a report Apple no longer supplies. Preserve required native archives separately and use reruns to refresh retrievable periods.
After setup, query the daily contract or finance contract rather than assuming that Apple’s original column names are the warehouse column names.