Shop Storefront Brief · Issue 5

Custom Product Pages are your ASA landing-page kit. Screenshot localization is the work most indie teams skip.

2026-08-27 · Fortune Insight, LLC · Operator intel for indie iOS teams. This page covers Custom Product Pages (CPP), screenshot localization in App Store Connect, and Apple Search Ads creative packing — not a commission or IAP rate change. If you only track fee worksheets, Connect rules did not change because of this note.

What happened

Apple's fall Creative Assets rollout (Issue 4) adds new header and search-result surfaces on top of your existing product page. But most indie teams still send Apple Search Ads traffic to the default listing — one screenshot set, one subtitle, one promotional text block — even when Connect keyword analytics show different search intents converting at different rates.

Custom Product Pages have been live since 2021 and remain the primary operator tool for matching ad creative to landing-page creative before Creative Assets arrive. Each CPP gets its own App Store URL, its own screenshot set (per device class), and optional subtitle and promotional text overrides. You can publish up to 35 CPPs per app and link each one to a specific Apple Search Ads ad group or campaign.

This issue is a practical packing guide: how CPP differs from Product Page Optimization (PPO), how screenshot localization fits in Connect, and how to use the keyword analytics Apple turned on in July to decide which CPP to ship first.

CPP vs PPO vs default listing — operator map

Three different Connect tools. Mixing them up is the most common indie mistake after enabling China or adding a second locale.

Surface	What it is	Who sees it	Typical indie use
Default product page	Your primary listing — name, subtitle, description, screenshots, app previews	Organic search, browse, and ASA taps when no CPP is assigned	Baseline storefront. Keep this stable; do not A/B chaos here.
Custom Product Page (CPP)	Alternate product page with unique URL (apps.apple.com/app/id…?ppid=…)	ASA ad groups you explicitly link; shareable campaign URLs	Keyword-specific screenshot sets — e.g. "budget tracker" vs "expense report" — each with matching overlay copy
Product Page Optimization (PPO)	Connect-run A/B test on subtitle, promotional text, or screenshots against the default page	Random sample of organic traffic only — not ASA-assigned CPP traffic	Test one hypothesis on organic visitors; wait for statistical significance before promoting a winner

Rule of thumb: use CPP for paid traffic you control (ASA, influencer links, email campaigns). Use PPO for organic experiments you want Connect to split automatically. Do not run a PPO screenshot test and a CPP screenshot set on the same keyword intent at the same time — you will not know which surface moved conversion.

Screenshot localization in Connect — what "localized" actually means

Screenshot localization is not automatic when you add a language row. Each locale in App Store Connect has its own screenshot matrix per device class (iPhone 6.7", 6.5", iPad, etc.). A CPP inherits the locale of the storefront the buyer is on — if your zh-Hans row has English screenshot overlays, the CPP shows English overlays too.

Operator checklist for one CPP + one locale:

• Default listing row complete first. CPP cannot fix a missing zh-Hans name or empty keyword field — it only overrides subtitle, promotional text, and screenshots within an existing locale.
• Per-device screenshot sets. Upload screenshots for every device class your CPP will serve. An iPad buyer on a CPP with iPhone-only assets sees the fallback set — often your English default.
• Overlay copy is part of the image. Connect does not localize text baked into PNGs. If overlays say "Track expenses" in English, translate and re-export before uploading to the zh-Hans CPP variant.
• App Preview captions are separate. Each preview localization has its own caption track. A localized screenshot set with English preview captions still looks half-localized on the storefront.
• 4+ ceiling applies. CPP screenshots and any Creative Assets you attach later must meet the 4+ rating ceiling published in Issue 4 — even when the app itself is 12+ or 17+.

Packing Apple Search Ads creative to a CPP

Apple Search Ads lets you assign a CPP URL at the ad-group level. When a user taps your ad, they land on the CPP screenshot set — not the default page. This is the highest-leverage pairing most indie teams underuse.

Step	Connect / ASA action
1 · Pick intent from keyword analytics	Connect → Analytics → App Store search → sort keywords by impressions × conversion rate (Issue 4). Pick the top term where conversion is below your app median — that is your first CPP candidate.
2 · Build one CPP per intent	Connect → your app → Custom Product Pages → Create. Name it internally (e.g. asa-budget-keywords). Upload screenshot set with overlay copy matching that search intent.
3 · Copy the CPP URL	After App Review approves the CPP, copy the ?ppid= link from Connect. Test it on device in the target storefront locale before spending.
4 · Assign in ASA	Apple Search Ads → Ad Group → Ad Settings → Custom Product Page → select your CPP. Search Match and broad campaigns should stay on default; exact and brand ad groups get CPP assignments.
5 · Match ad creative to landing screenshots	Your ASA custom product page ad creative (if enabled) and CPP screenshots should show the same value prop. Mismatch — ad says "invoice scanner," landing shows "habit tracker" — kills tap-through conversion even when the keyword is cheap.

Operator catches: CPP review is separate from app version review but still goes through App Review — budget 24–48 hours. CPP analytics appear in Connect under the CPP name, not merged into default page metrics. You cannot assign a CPP to Search Match automatically; each ad group is manual.

Using Issue 4 keyword data to prioritize CPP work

Connect keyword analytics (live since 2026-07-01) give you per-keyword impressions, tap-through rate, conversion rate, and retention cohorts for your own app. Use them to rank CPP candidates before you design new screenshot sets:

• High impressions, low conversion: screenshot/message mismatch — build a CPP with overlays addressing that keyword's intent.
• High conversion, low impressions: discovery problem — ASA or metadata work, not a CPP priority.
• High impressions, high conversion: protect with a CPP anyway if you run ASA on that term — prevents a competitor's ad from sending traffic to your generic page.
• Retention drop at 7 days on a keyword: CPP will not fix product-market fit; do not build landing pages for terms that attract churny installs.

Export the top 10 keywords weekly. If fewer than three terms have enough impressions to judge, your sample size is too small for CPP splits — stick to one default CPP for your highest-spend ASA ad group instead.

What this is not

• Not a new US or EU commission rate. EU unified terms still land 2026-10-01 — see Issue 0.
• Not a Creative Assets submission guide — headers and search slots arrive with iOS 27 this fall; see Issue 4.
• Not a guarantee that CPP will improve ASA ROAS. Better landing-page match helps; bid strategy and keyword relevance still dominate spend efficiency.
• Not App Store Connect API automation for CPP — API support exists, but most indie teams should ship manually before scripting uploads.
• If you only sell US IAP inside the App Store and do not run ASA: no need to build CPPs this week unless you plan paid acquisition next quarter.

Launch pricing snapshot (GetAppNiche prepaid median vs new apps)

GetAppNiche published a prepaid-app pricing median estimate of about $2.99 on 2026-07-16. The table below is observed listing prices this week — snapshots, not revenue or download promises.

App	Observed price
CloudGear	$1.99/mo · $14.99/yr · $39.99 (lifetime tier)
Frankensketch	IAP ~$2.99 (estimate)
Optic Illusion	Free
Stonegate	$7.99 unlock

The median is a reference line, not a guarantee that you should price at $2.99. CPP and ASA spend decisions are independent of IAP tier — do not reprice because of this table.

Calendar recap (already covered — not new this issue)

These items appeared in prior issues or Apple announcements. Listed here for cross-check only — not new scoops.

• Creative Assets fall launch: headers, search slots, Asset Library — Issue 4 · Apple · App Store asset best practices
• Connect keyword analytics: live since 2026-07-01 — Issue 4
• EU 2026-10-01: Unified EU terms — Issue 0
• US link-out 15% proposal: Epic court filing — Issue 2
• Brazil CADE response (2026-08-24): alternative distribution step-count — Issue 3
• Sonar launch offer: through 31 Aug — Issue 1

What an indie can do this week

• Export your top 10 Connect keywords by impressions. Mark any term where conversion rate is more than 20% below your app average — that is CPP candidate #1.
• Create one CPP with a screenshot set whose overlay copy matches that keyword intent. Keep overlays inside the 4+ ceiling — no price callouts, no unverifiable badges.
• If you run ASA: assign the approved CPP to your highest-spend exact-match ad group. Leave Search Match on the default page until you have baseline CPP data.
• If you localize for zh-Hans or other storefronts: verify the CPP screenshot matrix is filled for every device class in that locale — not just iPhone 6.7".
• Do not rebuild checkout or reprice IAP because of CPP or ASA packing — this is a marketing-surface workflow, not a commission update.

Sources: Apple · Custom Product Pages · Apple · Product Page Optimization · Apple · App Store search · Apple · App Store asset best practices · Apple Search Ads · Use Custom Product Pages