The 52 billion download headline crosses platforms

Sensor Tower’s release describes 52 billion game downloads across mobile, PC and console, while its $82 billion revenue figure concerns mobile IAP. The two figures do not share an automatic denominator.Release.

Reject the convenient division

Dividing the mobile revenue figure by the combined download total would produce a neat number, but not a defensible mobile revenue-per-install benchmark. The platform populations differ, and period revenue need not come only from that period’s newly downloaded users.

Our recommendation is to state both problems before performing any calculation. A useful acquisition metric requires an aligned population and horizon: which users were acquired, when they arrived and which revenue is attributed to their cohort. A market-wide spending total answers a different question.

Preserve the report’s wider context

The publisher’s State of Mobile page discusses app-market activity separately. Its existence does not license mixing totals from different reports or scopes. A second page from the same vendor is additional context, not an independent census.

The card is deliberately a compatibility check rather than a derived chart. It records why the tempting calculation is not performed. For a studio’s planning model, substitute its own properly aligned cohort revenue and installs. Keep vendor market totals in the market-context section, where they can inform scale without pretending to reveal the value of a newly acquired player.

Inspect the evidence

Download the source-population and comparability card. The extraction separates documented facts from our analysis and unknowns.

Further reading in the existing archive: UA metrics explained: CPI, ROAS, LTV and payback; Blended ROAS Calculation: Where It Quietly Goes Wrong. These links provide background; this check does not independently verify their full contents.

Frequently asked questions

How should UA teams read a 52 billion download headline that crosses platforms?

Sensor Tower’s release describes 52 billion game downloads across mobile, PC and console, while its $82 billion revenue figure concerns mobile IAP — the two figures do not share an automatic denominator. Dividing mobile revenue by the combined download total would produce a neat number, but not a defensible mobile revenue-per-install benchmark: platform populations differ, and period revenue need not come only from that period’s newly downloaded users. State both alignment problems before any calculation. A useful acquisition metric needs an aligned population and horizon — which users were acquired, when they arrived, and which revenue is attributed to their cohort. A market-wide spending total answers a different question. The publisher’s State of Mobile page discusses app-market activity separately; a second page from the same vendor is additional context, not an independent census. Keep vendor market totals in the market-context section and substitute the studio’s own aligned cohort revenue and installs for planning.