NETICE DOCUMENTATION
Raw App Store and Google Play reports to S3 and GCS
Reviewed
Netice Raw Reports keeps selected Apple App Store and Google Play report families as stable managed files in your S3 or Google Cloud Storage destination. It preserves provider-supplied rows and columns, without applying the Daily App Sales schema, Platform Finance schema or currency conversion.
Raw output is useful when you want to build your own transformations, inspect provider fields alongside normalized output, or retain source-shaped data in infrastructure you control. Refreshes can replace the same managed files. This is not an immutable snapshot of every provider download: Netice may decode, combine reporting periods and recompress tabular exports.
Choose raw output for source-shaped data
| Need | Use | What Netice delivers |
|---|---|---|
| Provider columns for your own parsing and models | Raw Reports | Provider-specific managed files in S3 or GCS |
| Comparable daily app-sales analytics | Daily App Sales | A normalized daily schema with amount methods and reporting currency |
| Monthly platform proceeds and finance events | Platform Finance | A separate event-based finance schema with period and currency context |
Create separate raw tasks for Apple and Google Play. Raw tasks do not merge the providers into a shared revenue file, even when both tasks write into the same storage service.
Select the report families you need
| Provider | Report family | Setup and interpretation |
|---|---|---|
| Apple App Store | Daily Summary Sales, Subscription, Subscription Event and Subscriber | Core daily Sales and Trends families in the recommended Apple bundle; availability depends on relevant source activity. |
| Apple App Store | Monthly Financial and Finance Detail | Select the finance families and supply finance-region scope. These retain Apple’s finance-period meaning. |
| Google Play | Estimated Sales | Monthly source files updated with recent sales activity; useful for provider-native daily sales inputs. |
| Google Play | Earnings | Monthly finance ledger exports, separate from Estimated Sales. |
| Google Play | Subscription statistics | Provider subscription reporting with its original dimensions, rather than the daily normalized revenue contract. |
The task’s family selector shows the choices available for that provider. For the distinctions behind the revenue families, see the Apple report map and Google Play report map.
Set up a raw delivery task
- Select Apple Raw Reports or Google Play Raw Reports, then choose S3 or Google Cloud Storage as the destination.
- Select or create the source connection. Use the Apple access guide or Google Play access guide.
- Choose Recommended raw bundle for the default provider selection, or Custom report families for an exact set. Complete extra scope fields for selected Apple finance families.
- Configure your destination bucket and optional destination folder. Source-report access and bucket-write access are separate permissions.
- Choose the initial history and recurring refresh windows. Use Quick test to review a small delivery before selecting a larger history range.
- Save the task and inspect its delivery status and managed files. Confirm the report families and period coverage before connecting downstream processing.
Keep separate provider accounts in separate tasks and destination folders. Netice rejects switching an existing raw task to another source account while retaining its destination. Create a new task and folder when moving to another source account.
What the destination contains
Apple tabular report output uses compressed text files; Google Play tabular output uses compressed CSV. Files retain source columns rather than Netice’s normalized amount fields. Filenames are managed by Netice, so downstream processing should use the files actually delivered rather than reconstructing names from app IDs or source filenames.
Apple output is organized by report family. New Google Play raw tasks keep separate logical source streams, including distinctions needed for packages, report dimensions and financial report periods. That prevents one stream’s refresh from replacing a different stream’s data.
A status manifest accompanies the output. Use it together with task status to distinguish delivered reports from unchanged, pending or failed reports. An unchanged file is not a missing delivery, and a pending provider report is not a zero-revenue record.
Refresh updates managed files
Recurring Apple raw refresh checks recent daily report days; selected monthly families are checked by eligible report month. Google Play raw refresh checks recent eligible monthly exports, even when those exports contain daily rows. The initial history selection and recurring window control different parts of the task.
Later backfills use the same managed-output contract and can update existing files. Editing a task’s saved setup does not itself queue a historical run; use Run Backfill from My Tasks for a bounded older window. See backfill and refresh behavior.
If you require immutable retention of every delivered version, establish that retention in your own storage workflow. Do not assume the current managed file is a history of all earlier file versions.
Check coverage before interpreting absence
- No file yet: check provider publication timing, the requested family and period, and source permissions.
- Only some families delivered: inspect each family; sales access does not establish finance or app-specific report coverage.
- Delivery failed: check write access to the selected destination bucket and folder separately from provider access.
- Older reports unavailable: verify provider retention before extending the backfill. Netice cannot retrieve a report the provider no longer exposes.
- A parser fails after a refresh: inspect the delivered provider columns. Raw output deliberately retains the provider’s schema rather than imposing the normalized daily contract.
Compare normalized Daily App Sales and Platform Finance, or see Netice’s product workflow.