NETICE DOCUMENTATION
App revenue files in Google Cloud Storage and S3
Reviewed
Netice delivers normalized app-store revenue reporting into customer-owned Google Cloud Storage or Amazon S3. Daily App Sales produces managed CSV output. Platform Finance produces a separate CSV with supporting files. Raw Reports delivers provider-native rows and columns in managed files with a separate file contract.
Choose the output family before building a downstream loader: a normalized CSV and a provider’s native export do not share column names, encoding or row semantics.
| Output | File contract | What a refresh means |
|---|---|---|
| Daily App Sales | CSV using the daily schema | Merge existing history with refreshed rows, replacing the relevant source/date scope. |
| Platform Finance | Main finance CSV plus a support folder | Replace selected report periods and source scope; preserve data outside that scope. |
| Raw Reports | Provider-specific files and columns | Refresh the selected native report artifacts as the provider makes them available. |
GCS and S3 setup
| Destination | Prepare | Verify |
|---|---|---|
| Google Cloud Storage | The destination bucket/path and the Google Cloud identity used for it. | The identity can read the managed history and write the selected output location. |
| Amazon S3 | The bucket, region, output prefix and destination access configured in Netice. | Bucket and identity permissions allow the required reads and writes at that prefix. |
Keep source credentials separate from destination access. Google Play’s reporting bucket is the source; your GCS bucket is the destination, even though both use Google Cloud Storage. Check those two locations independently when troubleshooting.
Daily CSV is managed history
A recurring run can update recent reporting without dropping older output outside the refresh scope. A rerun can replace rows you previously consumed. Do not blindly append every downloaded copy of the managed CSV into an append-only database table: repeated history would be duplicated.
Either replace your downstream representation of the managed file or implement a deliberate scope-aware load. If you require every historical version, configure your own archive or snapshot process. Current normalized Daily App Sales object-storage delivery is CSV; do not build this integration expecting Parquet.
Platform Finance includes completion context
The finance export has a main CSV and a same-stem support folder with a manifest, schema, period status and materialized views. The manifest records counts and hashes and is written after the other export components.
Use the manifest and period status when checking a completed delivery rather than treating the appearance of one file as evidence that every component is ready. Object storage does not make a group of independently written files a single transactional snapshot.
Preserve raw when source fidelity matters
A normalized file follows Netice’s schema. A native report retains the provider’s structure. Use Raw Reports for provider-specific analysis; maintain separate loading rules for Apple and Google report families. Retain separate snapshots if you need earlier versions of the managed files.
Before querying normalized output, review the daily dictionary, finance dictionary and missing-amount semantics. CSV format alone does not tell you whether zero is observed, estimated or assumed.