For years, Custom Product Pages on iOS were a paid acquisition tool - send Apple Search Ads traffic to a tailored screenshot set for a specific audience. Useful, but optional.
That changed. Apple now lets you assign keywords from your keyword field to specific CPPs. When your app ranks organically for that term, users can see a page built for that intent - not your default listing.
With the limit raised to 70 CPPs per app (doubled from 35 in late 2025), this is a genuine ASO lever. If you're still running one default page for every search intent, you're leaving rankings and conversion on the table.
What is a Custom Product Page?
A Custom Product Page (CPP) is an alternate App Store product page for the same app. Same app ID, same reviews, same core metadata - but different screenshot order, preview video, and promotional text where applicable.
Users reach a CPP through:
- Organic search - when the CPP is keyword-assigned and you rank for that term
- Apple Search Ads - when you link an ad group to a specific CPP
- Links from your site, email, or campaigns - App Store Connect analytics break out CPP performance by source
Think of it as landing page variants inside the App Store - without publishing a separate app.
Why did CPPs become an ASO tool?
Apple's 2025–2026 update added keyword-to-CPP mapping - you assign terms from your 100-character iOS keyword field to a CPP, and the store can surface that page when you rank for the term.
Practical example: A fitness app ranks for "home workout" and "gym log." Default screenshots lead with home workouts. A CPP assigned to "gym log" leads with logging features, rep tracking, and progressive overload - creative that matches why someone searched that term.
Same app. Different intent. Higher conversion.
This is why CPP strategy belongs in your ASO workflow, not only in your ASA account structure. Broader context: App discovery in 2026.
When are CPPs worth the effort?
CPPs pay off when you have multiple distinct use cases, rank for terms that need different proof points in screenshots, want ASA and organic aligned on the same keyword theme, or see conversion gaps on segments that drive search volume.
Skip CPPs (for now) when you have a single use case and audience, your default listing already converts above ~35% for most of your relevant keywords, or you cannot maintain distinct creative.
Quality beats quantity. We typically start with 3–8 CPPs mapped to highest-intent keyword clusters, then expand based on App Store Connect analytics.
How do you build a CPP that converts?
Same rules as default listing creative, with tighter intent match:
- First screenshot = search intent - if the keyword is "invoice scanner," screenshot one shows scanning an invoice, not your logo animation.
- Headline copy on screenshots - benefit in five words or fewer. Match the language of the assigned keyword where natural.
- Social proof where relevant - ratings snippet, "trusted by X businesses," category badge if you have one.
- Preview video optional - only if it adds clarity for that segment; don't reuse generic brand video by default.
- Measure in Connect - CPP analytics now break out impressions, conversion, and proceeds by source (organic, Apple Ads, web referrer). Use filters; don't guess.
Apple's March 2026 analytics expansion made CPP reporting usable without exporting to third-party tools for most teams.
How do CPPs work with Apple Search Ads?
ASA still supports CPP deep links per ad group. The efficient pattern:
- Build CPP for a keyword theme
- Assign keywords for organic surfacing
- Point ASA discovery and category campaigns at the same CPP
When organic ranking kicks in, you stop paying for some clicks you were buying last quarter. That's compounding ASO + paid working off the same asset.
Our Apple Search Ads service runs this structure routinely - ASA validates CPI while CPP + metadata work toward organic share.
What are the most common CPP mistakes?
One CPP, renamed weekly. CPPs need stable data to learn. Pick a hypothesis, run 4–6 weeks, read conversion by source.
Keyword assignment without ranking potential. Assigning "best fitness app" to a CPP when you rank #180 wastes a slot. Map terms you rank 10–50 for first - that's where creative lift moves installs.
Ignoring default listing. CPPs extend your default page; they don't fix broken icon or vague subtitle on the main listing.
Creative duplication. If every CPP uses the same five screenshots reordered, you won't see conversion differences. Each page should prove a different value prop.
Where do CPPs fit in your 2026 ASO plan?
We sequence CPP work after metadata and default creative baseline:
- Keyword research and competitor gap analysis
- Default listing optimisation (icon, screenshots, video)
- CPP map - keyword clusters → creative briefs → build in App Store Connect
- ASA linkage where paid budget exists
- Quarterly review - expand, retire, or refresh based on Connect data
CPPs are one layer in a broader discovery picture. Store search, paid, and AI-mediated discovery all send traffic to pages that must convert. CPPs improve match between intent and creative for iOS search specifically.
Need help prioritising CPPs?
If you're unsure which keyword clusters deserve a CPP vs a metadata tweak, apply for a strategy call. We can look at your current rankings, conversion data, and creative capacity - and tell you whether CPPs should be your next priority.