What custom store listings are for
The store listing is the landing page of every install campaign, and it is a page the advertiser does not fully control. The default listing is written for everyone: people searching the store, people browsing charts, people following a friend's link, people from every ad. A single page that tries to serve all of them leads with the app's broadest promise, which is rarely the promise a particular ad made.
Custom listings solve that by giving a campaign its own page. As the ASO guide describes, Apple's custom product pages and Google's custom store listings are variants of the page built for a particular audience or campaign, each with its own URL. The install campaigns guide adds that an ad for a specific audience or feature can land on a page whose screenshots lead with it, and that Apple Search Ads can use a custom product page as an ad's destination. The principle is the one the message match guide sets out for web landing pages: the page should repeat the promise and the look of the ad that sent the visitor, so they know in a glance that they arrived in the right place. Message matchHow closely a landing page repeats the promise and wording of the ad or link that sent the visitor. on a store listing is mostly a matter of the first screenshots.
| Tool | What it does | When to use it | Covered in |
|---|---|---|---|
| Default listing | Serves store search, browse and any traffic without its own page | Always; it stays optimised for search | App store optimisation |
| Custom listing | A variant with its own address for an audience or campaign | When a campaign's promise differs from the default page's lead | This tutorial |
| Listing experiment | Splits visitors between the current page and a variant | When deciding what a page should become | App store screenshot test |
The details of custom listings vary by store and change over time: how many each store allows, which parts of the page can differ, how they are reviewed and how long that takes, and how each store treats them in search. This tutorial does not rely on any of those. Check the current documentation on the App Store developer site and in Play Console Help before building, and plan around what it says on the day.
Before you start
Gather the inputs. First, the list of live and planned install campaigns, with each one's audience, the promise its creative makes and its share of spend; the RACE plan for app installs usually has this in its Reach and Act stages. Second, the default listing's current conversion rate by traffic source from each store console; the conversion rate calculator for app store listings shows how to work it out as installs over product page views, kept apart by source. Third, access to App Store Connect and Play Console with permission to edit listings, and to the ad accounts that will point at them. Fourth, the screens and captions the default listing already uses, and the designer who will produce new ones.
Agree who owns each page: who briefs it, who approves its claims, who links campaigns to it and who retires it. A custom listing with no owner outlives its campaign and quietly misleads the next one.
The steps
List the campaign themes and audiences that differ
Write one row per campaign theme, not per ad: the audience it reaches, the job or feature its creative leads with, the network it runs on and its spend. Group ads that make the same promise to the same kind of person into one theme. A language app might find a handful of themes, such as travel phrases, exam preparation and work English, spread across many ads. A campaign whose promise is the same as the default listing's lead needs no row.
Decide which themes earn their own listing
A theme earns a page when its promise differs clearly from the default listing's first screenshots and it carries enough paid traffic for the page's conversion to be readable. Start with the themes that meet both tests and carry the most spend. Resist one page per ad: each page has to be built, reviewed, linked, read and eventually retired, and splitting traffic thinly leaves every page too small to judge. Check the store's current documentation for any rules on how many pages can exist.
Brief the screenshots around each ad's promise
For each page, the first screenshots should repeat the ad's promise in its words and show the screen that delivers it. The ASO guide's caption-led pattern applies: one short benefit statement in large type above a framed screen that proves it. The first screenshot answers the question the ad raised; the next show the core action for that audience; the rest can follow the default listing's story. Brief the designer with the ad beside the page, and ask for the first frame to be recognisably the same promise at a glance, in the same colours where the brand allows.
Write the text within the review guidelines
Where the store lets the page's text differ, write it for the theme's audience. Both stores' review rules bound what a listing may say: the ASO guide notes that Apple's guidelines cover the accuracy of metadata, the use of other apps' names and the claims a listing may make, and that the Play policies cover the same ground. A campaign promise that is fine in an ad can still be a claim the listing cannot support, such as a feature the app does not yet have, a price that does not match, or a rival's name. Have someone who did not write the ad check every claim against the app as it ships.
Build the listing in each store's console
Create the page in App Store Connect and in Play Console following each store's current documentation, and record its address, the theme it serves, the date it went live and its owner in a shared register. Keep the default listing unchanged while you do this; the point is a page beside it, not a replacement. Before submitting, run the page through the app store listing checklist, which covers the text, screenshots, privacy details and attribution links in one pass.
Link each campaign to its listing
Point every ad in the theme at the page's address, using whatever destination setting each network provides. The install campaigns guide notes that Apple Search Ads can use a custom product page as an ad's destination; for other networks, follow the setup their own documentation and the site's platform pages describe, such as the Meta Ads setup for app installs and the Google Ads setup for app installs. Record in the register which campaigns point at which page, so that a page is never retired while ads still send people to it.
Pair each listing with a deferred deep link
The page persuades; the first session has to deliver. The app stores page for app installs pairs each campaign listing with a deferred deep linkA link that opens a specific screen inside a mobile app rather than its home screen., so that a new user opens on the screen the ad showed rather than a generic start. The deep links and app analytics guide explains how deferred links carry the destination through the install and why a default first screen is needed when matching fails. Test each route on a fresh device with the deep link testing tutorial before the campaign spends.
Read listing conversion per page against the default
Once each page has had enough visitors to read, compare its conversion rate (CVRShare of visits or clicks that convert.), installs over page views, with the default listing's rate for the same kind of traffic. Read it from the consoles' reports, which the install campaigns guide describes as showing whether paid visitors convert like organic ones; check the current console documentation for how each store breaks results out by page and source. Compare like with like: paid traffic to the custom page against paid traffic that reached the default, not against store search, which converts very differently. Then follow the installs through to activation, because a page can win installs by promising more than the first session delivers. The effect on cost per install (CPIAverage ad cost of each app install.) follows from the conversion: a page that converts more of the same clicks makes each install cheaper.
Test larger changes with the store's listing tests
A custom page compared with the default is not a controlled test: the traffic differs, the timing differs and the campaign itself changes. When a page's direction is in doubt, or a new idea should replace the default's first screenshots, use the stores' own listing tests, which the ASO guide describes as the only reliable way to know what moves store conversion. The app store screenshot test builds such an A/B TestControlled comparison of two variants. around one priority traffic source with installer retention as a guardrail. Where the store documentation allows tests on custom pages, the same method applies.
Retire listings when their campaign ends
When a theme's campaigns stop, check the register: if nothing still points at the page, retire it, or keep it only if the next campaign in that theme will use it unchanged. Before retiring, move any useful finding into the default listing's next test. Pages left live after their campaign tend to carry seasonal claims, old screens and offers that have ended, and they still receive visitors from old links and saved ads.
A simple register keeps the pages and campaigns in step.
| Page | Theme and audience | First screenshot promise | Campaigns pointing here | Deep link | Owner | Live since | Review date |
|---|---|---|---|---|---|---|---|
| Default listing | Everyone else | The app's main job | None (search, browse, referrals) | Not applicable | Store lead | Always | Each release |
| Custom page A | First theme | The first theme's promise, in the ad's words | Campaign names | Destination screen | Named person | Date | Date |
| Custom page B | Second theme | The second theme's promise | Campaign names | Destination screen | Named person | Date | Date |
A language app's campaign listings (illustrative)
Zinniqua Languages builds three campaign listings
Zinniqua Languages, an invented language-learning app, runs 18 install ads that group into three themes: travel phrases for holiday-makers, exam preparation for students and English for work. Its default listing leads with "Learn a language in ten minutes a day", which none of the three ads says. It builds one custom listing per theme on both stores. The travel page opens on "Order, ask, get around: phrases for your trip" over the phrasebook screen; the exam page on "Practise the speaking test with feedback" over the mock-exam screen; the business page on "Sound confident in meetings" over a role-play screen. Each campaign points at its page, and each page has a deferred link to the matching first lesson. After six weeks, paid visitors to the exam page convert at 38% against 27% for paid visitors to the default listing, and 61% of exam installers finish a first mock test. The travel page converts at 29%, within noise of the default. The business page converts at 24%, below the default; reviews of the ad show the creative promised live tutors the app does not offer, so the team rewrites the ad rather than the page. Zinniqua keeps the exam page, merges travel back into the default and queues a screenshot test of the exam promise on the default listing.
The pages built here sit inside the wider listing work in the app marketing hub, and the glossary entry on message match is a quick reference for briefing designers who have not worked on landing pages.
If paid visitors convert worse than they used to, the guide to a falling app store conversion rate checks whether campaigns still land on matching pages before blaming the screenshots or the rating.
Common mistakes
- One page per ad. The work multiplies and the traffic splits until no page can be read. Build pages for themes.
- Changing the default listing instead. The default serves search and every other visitor; build a page beside it.
- Matching the caption but not the screen. The first screenshot has to show the screen that delivers the ad's promise, not just repeat its words.
- Claims the app cannot support. An ad's promise still has to pass the review rules on the listing. Check every claim against the app as it ships.
- No deep link behind the page. The page persuades; a new user who then lands on a generic start screen loses the reason they installed.
- Comparing the page with store search. Paid and search visitors convert differently. Compare paid with paid.
- Treating the comparison as a test. Use the stores' listing tests when a decision depends on the difference.
- Relying on store rules nobody checked. Limits, editable fields, review and search treatment are in each store's current documentation, not in this tutorial.
- Pages left live after the campaign. Old claims and ended offers keep reaching people through old links. Retire pages from the register.
