NETICE DOCUMENTATION
How Netice delivers app-store revenue data
Reviewed
Netice retrieves Apple App Store and Google Play reports, prepares the selected reporting output, and delivers it into a customer-owned destination. Daily App Sales, Platform Finance and Raw Reports are separate workflows: they answer different questions and preserve different source semantics.
Choose the report family before choosing a table or dashboard. A daily revenue trend, a monthly platform-finance review and provider-shaped report data are three different deliverables.
- 1. Source reportsApple Summary Sales or finance reports; Google Estimated Sales or Earnings.
- 2. Netice workflowSelect the reporting family, source access, reporting currency where applicable, and refresh scope.
- 3. Your destinationQuery managed tables in BigQuery or Snowflake, or read delivered files in GCS or S3.
Choose the output you need
| Workflow | What arrives | Use it for |
|---|---|---|
| Daily App Sales | A common 38-field sales output, including estimated amounts, source context and estimation methods. | Operational revenue trends across the two stores. |
| Platform Finance | A separate 49-field monthly event output, including signed proceeds, report periods and currency context. | Platform-finance analysis and inputs to your close process. |
| Raw Reports | Provider-supplied rows and columns in managed files, using the selected raw report contract. | Source checks and provider-specific transformations. |
Raw Reports may decode, combine periods and recompress exports. Its managed files can be replaced on refresh; they are not byte-identical archives of every provider download.
The workflow comparison explains why aggregating daily estimates does not reproduce monthly finance.
Before configuring a destination, inspect example output, field lists and SQL in the warehouse explorer.
Set up a reporting workflow
- Connect the source. Provide the Apple reporting access or Google Play report-bucket access required by the selected family. An app identifier alone does not authorize downloads.
- Connect the destination. Select your warehouse or storage location. Warehouse setup includes the access needed to stage and write the managed output.
- Choose the family and currency. Keep daily and finance outputs separate. A report currency controls analytical presentation; it is not a guarantee of your bank’s eventual payout currency.
- Select history and recurring refresh. Backfills can only retrieve history still available from the source. Recurring runs revisit a reporting window to incorporate changes.
- Inspect the first output. Check source, dates, currency, row coverage and amount semantics before connecting a dashboard.
Connections and tasks have different jobs
A saved connection holds reusable source or destination access. A task defines what reports to retrieve and where to deliver them. Reusing a connection avoids entering the same credentials for each workflow; it does not make sales and finance interchangeable.
When replacing credentials, check every task using the connection. Confirm a successful source read and destination write before retiring the previous access. The access guide separates source authorization from destination permissions.
What changes on a rerun
Managed normalized output refreshes the selected scope while retaining data outside it. Daily output is date-scoped; finance output is report-period and source-scoped. Reprocessing a window is different from appending a second copy of everything that was previously delivered. See refresh, backfill and rerun behavior before designing downstream snapshots.
What remains in your stack
You own the destination and the SQL, BI models and accounting decisions built on it. Netice supplies platform-reported data and its documented transformations. It does not turn daily estimates into settlement evidence or replace reconciliation with accounting and bank records.