Subscription reports: a versioned query is part of revenue provenance

A revenue spreadsheet is only as current as the extract feeding it. Apple’s historical subscription-report transition is a useful audit point for game subscriptions, particularly where a reporting job has outlived its original owner.

Trace the file into the decision

Find the command that requests the report, the version parameter, the parser and the destination table. A filename alone does not show which schema the pipeline expected. Our recommendation is to preserve an actual sample file and the parser version used for the reconciliation.

Compare the output against the business question. A subscription report can support a subscription analysis; it does not automatically represent every purchase, advertising receipt or cash transfer in a game. Avoid labelling a partial revenue stream as total monetisation simply because it arrived through an official interface.

Investigate discontinuities before changing targets

If a historical series breaks around a reporting migration, first check the extraction and transformation rules. That is a diagnostic suggestion, not a claim that this particular version change altered any studio’s reported revenue. A stable source may still be transformed differently by a local parser.

The artifact preserves the source version change and its date. It leaves the studio’s current query and reconciliation result unobserved. A practical next check is to reproduce one report period from source file to planning table and have the revenue owner explain each adjustment before a growth team uses the output to set payback expectations.

The governing record is Transition from subscription reports version 1.2 to 1.3. This edition checks the provider documentation; it does not inspect a studio account or certify a shipped build.

Inspect the evidence

Download the applicability and deadline record. The extraction separates documented facts from our analysis and unknowns.

Further reading in the existing archive: Blended ROAS Calculation: Where It Quietly Goes Wrong; ROAS targets versus payback windows. These links provide background; this check does not independently verify their full contents.