Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Custom Store Listing

A variant of an app's store page, with its own address and screenshots, built for a specific campaign, audience or feature.
Paid Mediaplatform featureUpdated

Definition

A custom store listing is a variant of an app's listing in Google Play, and a custom product page is the App Store version, each built for a particular audience or campaign with its own URL. The guide to app store optimisation describes them this way and sets them beside the default listing, which stays optimised for store search. What each variant may change, how many an app may have, how they are reviewed and how each store treats them in search and browse are set by the stores and change over time, so the site's guides leave those details to the App Store developer pages and Play Console Help cited on this page.

The feature is a landing page, not a test. A custom listing sends a chosen audience to a different page; a store listing experiment splits visitors to one page between versions to learn which converts better.

In practice: one page per theme, linked from each campaign

The working unit is the campaign theme, not the individual ad. Ads that make the same promise to the same kind of person share one page, and a theme earns its own page only 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 read. The tutorial on building custom store listings for campaigns works through the full routine: choosing themes, briefing screenshots around each ad's promise, writing text within the stores' review rules, linking campaigns, keeping a register of pages and owners, and retiring pages when their campaigns end.

Each page is then pointed at by the campaigns in its theme. The app install campaigns guide notes that Apple Search Ads can use a custom product page as an ad's destination, and other networks are linked through their own destination settings. The app stores page for app installs pairs each campaign listing with a deferred deep link, so the new user opens the app on the screen the ad and the listing showed.

Why the store listing is an install campaign's landing page

On the web, an advertiser controls the landing page. For an app, the page between the ad and the install is the store listing, and the default one is written for everyone at once. A visitor who tapped an ad about one feature and arrives at screenshots about another has to work out whether they are in the right place, and many leave. A custom listing repeats the ad's promise in its first screenshots, so the visitor recognises it at a glance.

Each page is read on its conversion, installs divided by page views, against the default listing's conversion for the same kind of traffic: paid against paid, never against store search, which converts very differently. That comparison is not a controlled test, because the traffic and timing differ. When the direction of a page is in doubt, the stores' own listing tests are the reliable method, which the app store screenshot test builds around one priority traffic source.

Illustrative example — not a real result

A budgeting app gives its reminder ads their own listing

Pennysprout Budget Planner runs ads about never missing a bill, but its default listing opens with spending charts. Over four weeks, 12,000 paid visitors reach the default page and 2,160 install, a conversion rate of 18%. The team builds a custom listing whose first three screenshots show bill reminders, in the ads' wording and colours, and points the reminder campaigns at it. In the next four weeks, 11,500 paid visitors reach the new page and 3,105 install, or 27%. On the same £6,000 of spend, cost per install falls from £2.78 to £1.93. The team then checks the first week: 44% of the new installers set a reminder, against 41% before, so the page did not overpromise.

ASO covers the default listing and its search visibility; custom listings sit beside it for paid traffic. Message Match is the principle behind them, carried over from web landing pages. A Deep Link continues the same promise after the install by opening the matching screen. CPI falls when a page converts more of the same clicks, which is the main financial effect of a better-matched listing.

Common confusions

  • A custom listing is an A/B test. It sends a chosen audience to a different page; store listing experiments are the method for testing versions against each other.
  • It replaces the default listing. The default keeps serving search, browsing and unlinked traffic, and stays optimised for those.
  • One page per ad gives the best match. It multiplies the pages to build, review and retire, and splits traffic too thinly to read.
  • More installs means the page worked. A page can win installs by promising more than the app delivers, so new users are followed into their first sessions.
  • The details are the same in both stores. Apple and Google name, limit and review them differently, and both change their rules; check the current documentation.

More terms to look up

Where this term is used

Sources

  1. App Store — Apple Developer
  2. Google Play Console Help — Google

Related