Custom Product Page (CPP)

What is a Custom Product Page?

A Custom Product Page (CPP) is a variant of an iOS app’s App Store product page. Each variant can have different screenshots, app preview videos, and promotional text, but shares the app name, subtitle, icon, description, and other metadata with the default page.

Apple introduced Custom Product Pages in iOS 15. Each app can have up to 35 CPPs, each identified by a unique URL with a query parameter (?ppid=<id>). In Apple Search Ads, CPPs are assigned at the ad-group level as the landing page for ads in that group.

Why CPPs matter for Apple Search Ads

The single biggest lever for lowering CPI without lowering bids is tap-to-install conversion rate (CR). A 5-point lift in CR (from 35% to 40%) lowers effective CPI by 12-15%.

The reason: even if a user is highly engaged enough to tap your ad, they decide whether to install in the first 3-5 seconds on the product page. The default product page is optimized for organic browsers — generic enough to convert across many audiences. A targeted product page that speaks directly to the intent behind the keyword can lift CR substantially.

Typical CPP strategies

Strategy	Example	CR lift (typical)
Use-case targeting	A finance app with separate CPPs for “budgeting”, “investing”, “credit score”	10-25%
Audience persona	A fitness app with separate CPPs for runners, lifters, yoga	8-20%
Vertical-language	E-commerce app with category-specific CPPs (fashion, home, electronics)	5-15%
Promotional timing	Holiday CPP highlighting seasonal feature or sale	15-30%
Competitor conquest	CPP that explicitly addresses “switching from X”	10-25%
Localization deepening	Region-specific CPPs even within same language	5-15%

Mapping CPPs to ad groups

The mapping rule is: one CPP per intent cluster, not one CPP per keyword.

A finance app might have:

Ad group	Keywords	CPP
Brand	”[app name]”, variants	Default (already optimized for brand)
Budgeting	”budget app”, “expense tracker”, “money management”	CPP-Budgeting
Investing	”stock app”, “investing for beginners”, “etf tracker”	CPP-Investing
Credit	”credit score”, “credit monitoring”, “free credit report”	CPP-Credit
Competitor conquest	”[competitor name] alternative”	CPP-Switching
Search Match Discovery	(auto-matched)	Default

How to A/B test CPPs

Apple does not provide built-in A/B testing for CPPs the way Product Page Optimization (PPO) does for organic listing. To compare CPPs:

1. Build two CPP variants with the change you want to test (e.g., screenshot order).
2. Create two parallel ad groups with identical keywords, bids, and budgets.
3. Assign one CPP per ad group.
4. Run for 14-21 days or until each ad group has ≥1,000 taps for statistical significance.
5. Compare conversion rate in the Apple Search Ads dashboard.

Note that this consumes paid impressions, so isolate the test to a single ad-group pair.

Common failure modes

• Same CPP across all ad groups. Defeats the purpose; the default product page is already what you have.
• Too many CPPs (≥10) without enough impression volume per CPP. Each CPP needs ≥500-1000 taps to read clearly. Start with 3-5 CPPs and add more once data justifies.
• Forgetting to update CPPs when the default page changes. A new feature added to the default product page won’t propagate to existing CPPs — you must update each one.
• Using CPPs as A/B tests for organic. CPPs only affect paid traffic. Use Product Page Optimization (PPO) for organic A/B tests.

How ASAPilot helps

ASAPilot’s Account Health Audit specifically checks:

• Whether high-volume ad groups still point at the default product page (likely missed CR opportunity)
• Whether any CPP shows substantially lower CR than the default — a signal to either remove it or rebuild
• Whether assigned CPPs are still in Approved status (a rejected CPP silently falls back to the default)

See pricing for plan tiers, or read the keyword research playbook for how to structure ad groups that align with a CPP strategy.

Related terms

• Apple Search Ads — the platform
• CPI — the metric CPPs most directly improve