App Store Custom Product Pages: ads landing and review notes
CPP use cases, asset differences, consistency with default page, review and campaign handoff. For teams running paid acquisition. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
Growth teams often ask: “Can we give this ad creative its own store page?” On Apple that often means Custom Product Pages (CPP)—different screenshots, preview, or positioning from the default product page, paired with Apple Search Ads and other traffic so the store experience matches the ad. It is not a second app or a shadow build to evade review; same binary and capability boundary, different store presentation per channel.
Goee (goee.cc) wrote this for growth, paid media, and listing ops. How many CPPs you can create, which fields can diverge from default, and whether assets review with the build change in console—official pages rule. CPP does not promise looser review or higher conversion; it solves channel story misaligned with default page in a compliant split.
What this guide solves
Common CPP mistakes—not “don’t know how to click Create” but treating CPP as a side battlefield for exaggeration:
- Default page sells feature A; CPP screenshots show B—review compares to build.
- CPP changes promotional pricing/subscription language vs in-app IAP display.
- Many ad creatives share one CPP—landing still mismatches each creative.
- Assume CPP is not reviewed; use next-version UI mock while build is old.
- Default page metadata rejection; swap CPP screenshots quietly—“two stories, one build.”
- No map of Campaign → CPP URL—cannot attribute later.
CPP sits in the same rack as ASO and listing materials: when worth doing, asset sharing with ASO basics and screenshot specs, and submit/campaign timing.
Who should read
- Growth and ASA: land Search/display traffic on a page that reflects the ad, not five generic screenshots.
- Product: channel selling points still inside current build—no drawing features for CPP.
- Design/marketing: per-channel screenshot copy and preview order—must match submitted UI.
- Listing: create CPP in Connect, shared fields vs default, review state before handing URL to media.
- Agency: is CPP in scope; does ASC role cover it?
If default page fields are unclear, read iOS metadata checklist first—CPP does not replace name, description, privacy labels.
Core practice
Default page broken, or creative broken?
CPP has maintenance cost. Before creating:
- Can default screenshot #1 already carry your largest channel story?
- Is difference only “emphasize secondary flow” already in first description lines?
- Can you update all CPPs each release, or only default?
If “default page needs work,” run single-variable tests on default via product page optimization. CPP fits stable channel narrative that coexists without contradicting main story—e.g. default “all-in-one productivity,” channel only buys “scan PDF.”
Consistency red lines (same build)
CPP may reorder screenshots, on-image copy, preview emphasis—but not:
| Dimension | Channel variation OK | Do not split |
|---|---|---|
| Feature exists | Emphasize paths/scenes | Screenshots of UI not in build |
| Subscription/price | Emphasize a tier’s use case | Prices/cycles not shown in app |
| Account/login | Common login path for channel users | Imply paid features without account |
| Privacy/permissions | Do not over-claim | Less disclosure than default |
| Age/content | Match rating questionnaire | “Lighter” creative to dodge rating |
Trademark, competitor keywords, exaggeration risks same as default—trademark metadata risks. CPP is not a trademark bypass.
Create flow (practical order)
Buttons and required fields per official UI. Recommended:
- Lock build: CPP ties to uploaded/TestFlight-demonstrable build; capture only that UI.
- One-line channel brief: internal doc matching ad headline.
- Screenshot set: usually same device masters, new order/titles; 1–2 scene shots still real UI.
- Preview: optional shorter CPP cut—App Preview tips.
- Create in ASC: fixed naming (
ASA-brand-scan-2026Q2). - Review state: confirm before turning on spend—not “in review” URLs to media.
- Campaign bind: log URL/CPP ID per creative for product page optimization retros.
Apple Search Ads
- Keywords match CPP: “scanner” search → CPP first frame proves scan.
- Brand vs category: brand often fine on default; scenario/category words suit dedicated CPP. Competitor bidding has policy/complaint risk—official policy; no competitor names on CPP title cards.
- Metrics: installs alone—empty fold description kills post-download conversion.
Review and version updates
Major release: default + all CPP on one “materials sync” sheet. Stale CPP = two UI eras live.
Metadata reject fix on default—check every CPP for same inflated claim. Resubmit note: “Default and CPP screenshots updated to match build” beats default-only edit.
Copy-paste templates
CPP charter (internal)
Channel/campaign:
Ad platform:
CPP internal code:
One sentence to prove (matches ad):
Bound build:
Diff vs default (order/copy/preview only):
Screenshot 1–3 each proves:
Subscription scene: Y/N (screenshot #):
Created:
ASC state (draft/pending/live):
Campaign owner:
Next version sync milestone:
Release CPP patrol
Version:
Default page updated: Y/N
CPP list:
- code: ___ updated: Y/N old build: Y/N
- code: ___ updated: Y/N old build: Y/N
Pause ads pending assets: Y/N
Patrol owner/date:
Review note snippet
Default App Store product page and Custom Product Pages (if any) use screenshots from the same build;
CPP only changes scene order, no features not in the build.
Common mistakes
| Mistake | Outcome | Fix |
|---|---|---|
| CPP as “second product page” | Metadata reject | Same capability as default/build |
| Many CPPs never maintained | Misleading old UI | Sync on each release |
| Design mock not device | Review/bad reviews | Submitted build only |
| Spend before CPP live | Wrong landing | Confirm state first |
| Inflate “free” subscription | IAP conflict | IAP notes |
| Assume CPP exempt | CPP cited in rejection | Follow review state |
| No campaign map | No ROI | Charter + campaign notes |
| CPP to dodge default reject | Trust/account risk | Fix default and build first |
FAQ
CPP limits—how many?
Caps/billing official pages. Start 1–2 high-traffic scenes; each needs an owner.
Long default description—another for CPP?
Which fields can diverge per console. Most teams change visuals only; conflict is materials mismatch, not “having CPP.”
Android equivalent?
Play store listing experiments—do not assume symmetry.
CPP in TestFlight phase?
Usually after default page stable; beta UI churn is expensive. See TestFlight and review notes.
Broken CPP hurt default?
Same app, different entry—policy per console. Fix offending CPP; scan siblings for same wording.
Next steps
Channel CPP, ASC access, submit/campaign timeline: Telegram @hagee66. No approval promise; official pages govern.
Back to guide library