In one line
A Custom Product Page (CPP) is an Apple feature that lets you build several versions of your product page for one app and serve a different one depending on where the visitor came from. Apple allows up to 35 per app, each with its own URL.
Why it exists
When the ad's promise and the store page's content diverge, people drop off in that gap.
Someone who tapped an ad emphasising running features and lands on a default page whose first screenshot shows meal tracking pauses to check they have the right app. They have to scroll to find running, and some of them leave during that scroll.
CPP closes the gap by attaching a page built for that creative. The message carries straight through from ad to page.
Easy to confuse with PPO
The names are similar but the purposes are not.
- CPP — serves different pages to different sources. It declares no winner; the goal is matching a page to an audience.
- PPO (Product Page Optimization) — tests which variant performs better by splitting the same traffic at random.
Because CPP has no control group, it cannot answer "how much better did this get". Measuring the gain means splitting before and after by source or running a separate experiment.
Where it is used
- Attaching different CPPs per Apple Search Ads campaign or ad group so the page matches keyword intent
- Giving influencer or partnership traffic a dedicated landing page
- Shifting which feature leads, per creative, for apps that do several things
What to watch out for
Maintenance grows with page count. An app update that changes screenshots can mean revising all 35. Attach them only where the traffic actually performs differently.
CPP is also separate from the keyword indexing of the default page that appears in search results. Adding custom pages does not lift organic search rank.
Go deeper
How to actually establish that a store page change worked is covered in Store Listing Experiments.