How App campaigns interact with Play custom store listings
Expert: with sources and numbers. Plain: the same, without them, for beginners.
The page where Play ASO and Google UA actually meet. And the one topic in this section worth full attention.
This is the reason section 95 exists. Everywhere else, App campaigns are a UA topic. Here they are an ASO topic, because the landing page is a store listing you control.
The mechanism
A Ads-targeted custom store listings are available for App campaigns for installs promoting Android apps. The landing page is a custom store listing created in the Play Developer Console, and it directs users to a custom landing page with consistent ad-to-app creative messaging. (About Ads-targeted Custom Store Listings, verified 2026-09-18)
A Setup: select the listing from the Select a Custom Store Listings dropdown under Custom Store Listings in Advanced options during ad group creation. Same source.
A Timing: after creation, a custom store listing goes through review in Google Play, and once approved it can take up to 6 hours to become available for selection in Google Ads. Same source.
A Custom store listings are created in Play Console, up to 50 per app, and can vary app name, icon, short and full descriptions and graphic assets. (Create custom store listings, verified 2026-09-18) See 60-02.
Why this matters
You can match the landing page to the ad. The ad promises something; the listing it lands on can say the same thing, including a different app name and icon, which iOS custom product pages cannot vary (60-01).
It is the same asymmetry as iOS, in reverse. On iOS, custom product pages carry keywords and are addressed by URL. On Play, custom store listings carry more identity and are addressed by targeting. Both exist to stop paid traffic landing on a page written for someone else.
It closes an attribution gap. Traffic arriving on a dedicated listing is separable in Play’s listing reporting, so the campaign’s store-side conversion is measurable rather than buried in the default listing’s total (60-05).
The operational constraints
Two review queues, in sequence. A Play review, then up to 6 hours to appear in Google Ads. Plan for up to 7 days for Play listing review (20-07) and add the 6 hours on top. A campaign launching Monday needs the listing submitted the previous week.
Country exclusivity still applies. A A country can be targeted by only one custom store listing at a time (Create custom store listings, verified 2026-09-18). If a country-targeted listing already exists in a market, that is the constraint on what the ad-targeted one can do there.
A But the ad-targeted listing wins where they overlap: “By default, an ads-targeted custom store listing will take priority over a country-targeted one.” And the pairing is one to one: “You can only link one custom store listing per ad group.” (About Ads-targeted Custom Store Listings, verified 2026-09-20)
Both halves matter for structure. The priority rule means a campaign landing page overrides the market page for that traffic, so the two have to say compatible things about the same app. The one-per-ad-group rule means the ad group is the unit of creative targeting on Play, exactly as it is in Apple Ads (90-08), splitting an audience across listings means splitting it across ad groups first.
No automatic translation. A Same source. Every localized variant is manual work.
Android only, installs only. A Ads-targeted custom store listings are for App campaigns for installs promoting Android apps (About Ads-targeted Custom Store Listings). Not engagement campaigns, not iOS.
Deep links
A Google Ads requires a non-redirecting link, an App Link or Universal Link, as the final URL, and third-party solutions relying on redirects are not supported. (Set up deep links for App campaigns, verified 2026-09-18)
That is a technical requirement with an ASO consequence: the assetlinks.json association has to be correct and redirect-free (60-03), or the campaign cannot route users properly.
Who owns this
The listing lives in Play Console, owned by ASO. The campaign lives in Google Ads, owned by UA. The handoff is where it breaks, a campaign launched before the listing clears review, or a listing edited mid-campaign and sent back for review.
Agree who creates the listing, who selects it in the ad group, and what the lead time is, before the first campaign.
What goes wrong
Creating the listing the day before launch. Play review plus up to 6 hours.
A country-targeted listing blocking the ad-targeted one. Exclusivity applies per country.
Expecting it on iOS or on engagement campaigns. Android installs only.
Redirecting final URLs. Not supported.
Nobody owning the handoff. The most common failure, and organisational rather than technical.
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.
This is the entire reason this section exists at all. Everywhere else, this kind of advertisement is purely someone else's job. Here, it's genuinely your own job too, because the landing page is a second window you yourself control.
The mechanism
A specially-targeted second window is available for exactly this kind of install-focused advertisement. Its landing page is a second window you built yourself, directing a visitor to a custom page with writing that genuinely matches the advertisement itself.
Setting it up: you pick that specific second window from a dropdown, under an advanced setting, while building your group.
Timing: after you build it, a second window goes through the centre's own review, and once approved, it can take a further short stretch of time before it's even selectable in the advertising tool at all.
Your second windows are built directly on your own shopfront, a generous allowance per shop, and can vary your sign, your icon, your pitch line and full leaflet, and your photos.
Why this actually matters
You can match the landing page to the advertisement. The advertisement promises something specific; the window it lands on can say the exact same thing, including a genuinely different sign and icon, which the other centre's own second windows can't vary at all.
It's the same asymmetry as the other centre, just reversed. There, a second window carries filing words and is reached by its own address. Here, a second window carries more of your actual identity and is reached by deliberate targeting instead. Both exist for the same reason: to stop paid traffic landing on a page written for somebody else entirely.
It closes a real measurement gap. Traffic arriving on a dedicated window is genuinely separable in your own listing reporting, so that advertisement's own shopfront-side conversion becomes measurable, instead of being buried inside your default listing's overall total.
The real operational constraints
Two separate review queues, one after the other. Your own review first, then a further short wait before it's even selectable in the advertising tool. Plan for roughly a week for the first review, and add that further wait on top. An order launching on a Monday needs its second window submitted the previous week.
Country exclusivity still genuinely applies. A single country can only be targeted by one second window at a time. If a country-specific window already exists in a market, that's a real constraint on what an advertisement-targeted one can do there.
But the advertisement-targeted window wins wherever they overlap. By default, a window targeted at this advertisement takes priority over one targeted purely by country. And the pairing is strictly one-to-one: you can only link a single second window per group.
Both halves of that matter for how you structure things. The priority rule means an advertisement's own landing page overrides the country-specific one for that traffic, so the two windows have to genuinely say compatible things about the same shop. The one-per-group rule means the group is really the true unit of creative targeting here, exactly as it is on the other centre's own paid billboard, splitting one audience across several windows means splitting it across several groups first.
No automatic translation. Every language version here is manual work, same as always.
This is specific to install-focused advertisements only. Not for engagement-focused ones, and not available at all on the locked side of the centre.
Doors
The final address this advertisement points to has to be a genuine, non-redirecting door straight into the shop, an outside solution relying on a detour along the way simply isn't supported at all.
That's a technical requirement with a real consequence for this whole job: the proof-of-ownership file has to be correct and completely free of detours, or the advertisement genuinely can't route visitors properly at all.
Who actually owns this
The second window itself lives in your own back-office, owned by whoever handles being found and chosen. The advertisement itself lives in a separate advertising tool, owned by whoever handles paid growth. The handoff between the two is exactly where this breaks, an advertisement launched before its window clears review, or a window edited mid-campaign and sent right back for another review.
Agree in advance who builds the window, who actually selects it inside the group, and what the real lead time is, before the very first order goes live.
What tends to go wrong
Building the window the day before launch. Its own review plus a further wait on top.
A country-specific window silently blocking the advertisement-targeted one. Exclusivity genuinely applies per country.
Expecting this to work on the locked side, or on engagement campaigns. Install-focused advertisements only, on this one side of the centre.
A final address with a detour built in. Simply not supported.
Nobody actually owning the handoff between the two teams. The single most common failure here, and it's organisational, not technical at all.