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.
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.
Two systems measuring genuinely overlapping things with different definitions. As with the other centre's own paid billboard, the answer is to pick one system of record per question, rather than trying to reconcile them.
What the advertising tool reports
Installs and in-shop conversions credited to the advertisement, with cost, and performance against whichever target you set.
The centre's own diagnostic for a constrained order: your achieved cost closely tracking or occasionally exceeding your target, or your target return consistently higher than what you're actually achieving.
Reporting at the level of individual material exists, but it's deliberately coarse, the system itself is deciding how to allocate attention, and the reporting reflects that rather than offering you real per-item control.
What your own back-office reports
Traffic split into this centre's own search, its own browsing, ads and referrals, plus people who visited your listing and first-time installers.
A specially-targeted second window's own performance only shows up once it's crossed a real minimum amount of visitor volume, and the centre notes that these targeted windows typically pull in fewer visitors than a broader campaign would.
The main measurement here also shifted recently from actual acquisitions to clicks. Comparing any campaign result from before that shift to one measured after it compares two genuinely different events.
Why the two numbers will never actually match
Genuinely different attribution models and windows. The advertising tool credits things on its own model; your own back-office counts listing visits and installs on its own separate definitions entirely.
Your own back-office counts people; the advertising tool counts conversions.
The "ads and referrals" bucket isn't just your own campaign. It contains every kind of paid traffic and referral, including entirely different networks.
The advertising tool sees conversions your own listing simply doesn't. In-shop actions after the install, which your listing's own acquisition reporting never covers at all.
Don't try to build a reconciliation between them. Use the advertising tool for optimising the campaign itself, your own back-office for the shopfront-side conversion of windows you actually control, and an outside measurement partner for comparing across every network at once. Always say which system any given number actually came from.
What's genuinely measurable from the being-found-and-chosen side
Conversion on a dedicated, specially-targeted second window. Traffic arriving there is genuinely separable, so the shopfront-side conversion for that specific advertisement is real, subject to the usual minimum volume threshold.
Whether paid is genuinely displacing your unpaid results. Your own back-office's traffic split lets you watch your own unpaid search and browsing numbers while ad spending changes. The exact same reasoning as on the locked side's own paid billboard, and the only genuinely honest answer is still a real holdout.
The install referrer. This centre's own mechanism for passing campaign information through to the shop once it's actually installed.
What tends to go wrong
Trying to reconcile the advertising tool and your own back-office. Genuinely different definitions underneath.
Reading the "ads and referrals" bucket as if it were just your own campaign. It's every paid source at once.
Comparing across the point where the main measurement changed.
Expecting real per-item credit. The system allocates on its own; the reporting simply reflects that.
Judging a specially-targeted window purely on raw volume. The centre states plainly that these generate fewer visitors, and may sit below the reporting threshold entirely.