Custom Product Pages (CPP): the underused ASO weapon
Custom Product Pages (CPPs) are the most under-used App Store feature for indie devs in 2026. Each app can have up to 35 different variants of its listing - different screenshots, different promo text, different app preview videos - each with a unique URL. They're free, they're trackable, and most of your competitors don't use them. Here's how we approach them.
What CPPs are
A Custom Product Page is a variant of your App Store listing - same app, same metadata fields you can't change (title, subtitle, keyword field) - but with custom screenshots, app preview videos, and promotional text.
Each CPP has its own URL: apps.apple.com/app/idXXXXXX?ppid=YYYY. You can drive traffic from ads, social media, your own website, or email - and the user lands on a tailored listing.
Use case 1: ad-targeted CPPs
If you run Apple Search Ads or any paid acquisition: each ad creative should land on a CPP that mirrors the ad's claim. If your ad screenshot says 'Track water with Live Activities,' the CPP should have Live Activities as the first screenshot.
Conversion lifts of 15-30% from CPP-matched ads vs default-page ads are common in our experience.
Use case 2: feature-focused landing
Different audience segments care about different features. A power user landing from Hacker News wants to see export, automation, and shortcuts. A casual user from a TikTok landing wants to see beauty and ease.
Two CPPs, one URL each, two different acquisition flows.
Use case 3: localized hero copy
App Store metadata is localized at the country level (one variant per country). CPPs let you go finer - a 'Spanish for power users' variant, a 'Spanish for casual users' variant.
Limit: ~35 CPPs per app and you must have unique screenshots/text for each. Don't over-engineer.
Setup workflow
In App Store Connect → your app → Custom Product Pages → +. Give it a name, upload screenshots, write promo text. Submit for review (yes, every CPP goes through App Review separately). Approval is usually 24 hours.
Once approved, the CPP gets a URL. Use UTM parameters (or App Store Connect's analytics) to track which page each visit came from.
Measurement gotcha
App Store Connect's CPP analytics show impressions and conversion rate per page, but not the full funnel back to first-week revenue. Pair with a third-party attribution tool (or your own UTM logging post-install via deeplinks) for the full picture.
Without measurement, CPPs are useless. With measurement, they're one of the highest-ROI things you can ship in an afternoon.
Our default
For every app of ours that gets meaningful paid acquisition, we run at least 3 CPPs:
- Power user CPP - emphasizes export, automation, advanced features
- Privacy CPP - leads with 'all data stays on your device'
- Visual CPP - leads with the most screenshot-friendly screen
We retire CPPs that underperform within 30 days. App Store Connect makes the comparison straightforward.