Measurement

Expert: with sources and numbers. Plain: the same, without them, for beginners.

What App campaigns report, what Play reports, and why the two will not agree.

Verified 2026-09-18 · 39 days ago android google-ads analytics attribution

Two systems measuring overlapping things with different definitions. As on iOS (90-11), the answer is to pick a system of record per question rather than to reconcile them.

What Google Ads reports

Installs and in-app conversions attributed to the campaign, with cost, and performance against your target, tCPI, tCPA or tROAS.

A Google’s own diagnostic for a constrained campaign: achieved CPI or CPA closely tracking or intermittently exceeding the target, or tROAS consistently higher than achieved ROAS. (Best practices for App campaigns, verified 2026-09-18)

Asset-level reporting exists but is coarse by design, the system is deciding allocation, and the reporting reflects that rather than offering per-asset control.

What Play Console reports

A Traffic split into Google Play search, Google Play explore, ads and referrals, and store listing visitors and first-time installers (Understand and grow your app’s user base, verified 2026-09-18).

A Custom store listing performance requires sufficient visitor volume to appear, and Google notes ad-targeted listings typically generate fewer visitors than broader campaigns (Create custom store listings, verified 2026-09-18).

A Since July 2026 the primary store listing metric is clicks, not acquisitions (Understand and grow your app’s user base). Any campaign comparison spanning mid-2026 compares different events. See CONFLICT-013.

Why the numbers will not match

Different attribution models and windows. Google Ads attributes on its own model; Play counts listing visits and installs on its own definitions.

Play counts users; Google Ads counts conversions.

The “ads and referrals” bucket is not your campaign. It contains all ad traffic and referrals, including other networks.

Google Ads sees conversions the Play listing does not, in-app events after install, which Play’s acquisition reporting does not cover.

Do not build a reconciliation. Use Google Ads for campaign optimisation, Play Console for store-side conversion of the listings you control, and an MMP for cross-network comparison (97-02). Say which system each number came from.

What is genuinely measurable from the ASO side

Conversion on a dedicated custom store listing. Traffic arriving there is separable, so store-side conversion for that campaign is real, subject to the volume threshold (95-03).

Whether paid is displacing organic. A The Play traffic split lets you watch Google Play search and explore while ads spend changes. The same reasoning as iOS cannibalisation (90-12), and the only honest answer is still a holdout.

Install referrer. Play’s mechanism for passing campaign information through to the installed app (97-04).

What goes wrong

Reconciling Google Ads and Play Console. Different definitions.

Reading “ads and referrals” as your campaign. It is every ad source.

Comparing across the July 2026 metric change.

Expecting per-asset attribution. The system allocates; the reporting reflects that.

Judging an ad-targeted listing on volume. Google states these generate fewer visitors and may fall below reporting thresholds.

In short

Every fact on this page in one line, with its evidence tier, source and verification date, 4 A. Generated from the claim register, so it cannot drift from the page above.

A Google's diagnostic for a bid-constrained App campaign: achieved CPI or CPA closely tracking or intermittently exceeding the set target, or tROAS consistently higher than achieved ROAS.
GADS-BID-002 · verified 2026-09-18
A Play Console reports the search terms users searched before navigating to a store listing, split across Google Play search, Google Play explore, ads and referrals, and all traffic sources. Terms without enough visitors to report individually are grouped into an 'Other' bucket.
PLAY-ACQ-001 · verified 2026-09-18
A From July 2026 Google Play store listing performance reports focus on clicks rather than acquisitions. The primary metric is Unique user Install Clicks: the number of unique users who clicked the Install button from the store listing. Legacy acquisition data remains available in Statistics and exports.
PLAY-ACQ-002 · verified 2026-09-18
A A country can be targeted by only one custom store listing at a time. Custom store listings have no automatic translation. Ad-targeted listings currently show only on AdMob, not on Google Play search ads. Performance reporting requires sufficient visitor volume.
PLAY-CSL-003 · verified 2026-09-18

Think your app deserves better?

Send the App Store link.
The audit comes back within two working days, whether you hire us or not.

Free, and we mean it. No card, no call required.