Custom Product Pages: The Complete CPP Strategy Guide

ASO ASO Creative & Conversion Optimization

Jessica Abbadia 24 September 2026

Custom Product Pages used to be a paid-traffic-only tool: a variant listing you could only reach through an Apple Search Ads click or a shared campaign link. Two updates changed that. Since 30 July 2025, you can assign keywords to individual pages and have them surface in organic search, and on 29 October 2025, Apple doubled the per-app limit from 35 to 70.

Only 31% of apps use even one CPP. That is the number worth sitting with, because it makes this one of the least contested conversion levers in the App Store.

What follows is what a CPP actually lets you change, how the organic integration works, how to structure a program, and how to measure one without fooling yourself.

What Are Custom Product Pages?

A Custom Product Page is a variant of your app’s default App Store listing with its own creative, reachable through a unique URL or through matching organic search terms.

Apple’s App Store Connect documentation is the authority on what a page can carry, and it is short enough to read in full.

A CPP is a creative variant, not a metadata variant. If your plan depends on changing the subtitle per page, it will not work, and you will spend an afternoon looking for a field that is not there.

Because metadata is inherited, organic ranking is not split across pages. Our App Store ranking factors guide covers what the default listing is being ranked on. Each page is localizable, and must be localized for a market to appear in that market’s search results.

Every CPP goes through App Store Review before publishing, and so does any deep link attached to it. Updating an existing CPP’s screenshots or text does not require a new binary submission, and most submissions clear within 24 to 48 hours when the content matches the app’s existing review history.

One workflow detail that catches teams out: while a page is under review you cannot modify its screenshots, previews, promotional text or keywords. Withdrawing the submission makes the page editable again, then you resubmit. Plan around that if a campaign date is fixed.

The Organic Search Integration

Before 30 July 2025, a CPP only appeared when someone arrived via its unique URL. That made it a paid-and-owned-channel tool and nothing more. Since that update, assigning keywords from your existing App Store Connect keyword field to a CPP makes that page eligible to surface organically for matching searches, replacing your default product page for that term.

One rule governs everything else here: each keyword must be assigned to exactly one CPP. Assign the same term to two pages, and you are cannibalizing yourself. This is the constraint that decides how a multi-page program is structured, and it is the reason 70 available slots do not translate into 70 useful pages.

To monitor which CPPs are showing organically, go to App Analytics, then Acquisition in App Store Connect. Impressions, downloads, and conversion rate breakdown per product page variant. One threshold to know: CPP data requires at least five first-time downloads before it reports at all.

The tradeoff for your default page is real. As more of your top keywords route to dedicated CPPs, the default listing increasingly serves branded search, direct navigation, and any term you have not assigned.

CPP Strategy Framework

70 slots is a ceiling, not a target. The one-keyword-per-page rule means the real constraint is how many distinct, well-researched intents you have. Practitioners running real programs tend to land between 5 and 15 active pages, not 70.

That range holds up in practice.

“It really depends on the client’s campaign structure,” said Moburst’s VP of Organic, Jessica Abbadia. “Each concept, branded, competitor, feature, gets its own CPP, so the total can scale with how many campaigns a client is running. That said, if I had to give a number for the learning curve; run at least four or five CPPs, they don’t need to be simultaneous, before you have enough data to actually see the value. On longevity, we don’t kill a CPP at a fixed point. If it’s working, we keep it running, and it’s normal for a page to stay live six months before we refresh the creative on the same concept. If it’s not working, we pull it and try something else.”

Deep Linking with CPPs

A deep link attached to a CPP sends a user who taps Open after installing straight to a specific in-app destination rather than a generic home screen, matching the pre-install promise to the first thing they actually see.

This requires iOS 18 or iPadOS 18 and later, per Apple’s own documentation. If a meaningful share of your install base sits below that, the mechanism behind the retention argument is not available to you yet.

That match between promise and first screen is the reasoning behind reported retention gains. A user whose first in-app experience matches what convinced them to install has less reason to bounce in week one than one who has to go hunting for it.

Two mistakes recur. The first is pointing every CPP’s deep link at the same generic destination regardless of what that page promised, which defeats the entire approach. Apple’s guidance is to use a universal link rather than a custom URL, and to avoid URL shorteners or anything else adding redirects. Their suggested test is blunt and works: paste the URL into Notes and tap it.

The second recurring mistake is testing only the fresh-install path. A fresh install and an existing user reopening the link behave differently, and the link can break silently for one while working for the other.

Measuring CPP Performance

App Store Connect reports impressions, conversion rate and downloads per page, and also retention and average proceeds per paying user by which variant drove the install. That last pair is the useful one: it tells you whether a page is attracting the right users, not just more of them. If conversion is the bottleneck rather than traffic, start with conversion rate optimization.

Compute your own baseline. Apple’s conversion rate column uses its own denominator and will not reconcile with anything you calculate. Derive it yourself: default baseline = (total downloads minus CPP downloads) divided by (total page views minus CPP views). Then divide each page’s downloads by its views and compare. Anything under 1x is losing you installs. Reroute that traffic.

Underperformance isn’t rare, and it isn’t always obvious from the dashboard alone.

“Yes, it happens,” Abbadia said. “Usually, it’s because the concept wasn’t very different from the default page, or the default page ends up pulling in broader search intent than what we built the CPP around. We get data after two weeks of testing. When a CPP underperforms, we go back to the drawing board, rebuild the creative, and retest. I can’t think of a case where the same concept failed twice. Every test feeds the next one.”

On A/B testing. Apple gives you no native way to test CPPs against each other. Our guides to mobile app A/B testing and A/B testing app store creatives cover the method. Traffic is not split evenly and pages rarely run under matched conditions, so what looks like a winner may be noise. Testing means building a second page and splitting traffic at the ad-platform level. Product Page Optimization is the separate Apple feature that tests your default page: one test at a time, up to three treatments, up to 90 days.

Attributing organic against paid. Paid traffic arrives via the campaign’s unique CPP URL with its own tracking parameters. Organic CPP traffic arrives via a matching search term inside the App Store. App Store Connect’s per-page analytics distinguish the two.

One structural limit for paid: only one active custom ad runs per ad group at a time, alongside the always-on default product page.

Google Play Equivalent: Custom Store Listings

Google allows broader field customisation. Apple allows faster iteration.

CPP Best Practices Checklist

Do

1. Map each page to a genuinely distinct intent or audience. A page that doesn’t differ from your default in creative or targeting isn’t earning its slot.
2. Assign each keyword to exactly one page. This is a rule, not a preference.
3. Compute your own conversion baseline rather than relying on Apple’s column, and track retention alongside installs.
4. Match the deep link to each page’s specific promise, and test it across both fresh-install and returning-user paths.

Don’t

1. Build more pages than you can maintain and test. Five to fifteen actively reviewed pages beat fifty neglected ones.
2. Assume a CPP beats your default. Some lose. Measure before you scale.
3. Ignore the organic side once pages exist for paid campaigns. Assigning keywords to pages you already have is a low-effort way to capture traffic you’re currently paying Apple Search Ads to reach.

For managing pages at scale, use a naming convention tied to the keyword or segment each page targets, and set a recurring review to retire pages that are not earning traffic.

FAQs

Jessica Abbadia

Jessica is Moburst's VP of Organic. She specializes in enhancing organic performance for apps and games all over the world, while actively developing innovative methods for increasing app visibility and conversion, as well as offering her vast knowledge for the benefit of the mobile community. She graduated from law school and now serves as an animal rights activist who also loves reading books while sipping a strong coffee and holding one - or more - of her three cats.

Sign up to our newsletter

Δ

Email(Required)