What App Store custom product pages are

A custom product page is an alternate storefront for the same app. Shoppers who arrive through a unique CPP URL (from ads, email, QR codes, or partner links) see that page’s creative and copy instead of — or layered with — your default product page experience for that localization. The app binary, ratings, and reviews stay shared; the marketing surface can differ.

  • Same app, alternate storefront: useful for paid UA, seasonal pushes, and feature-specific stories.
  • Unique URL per CPP: you distribute that link in campaigns; organic search still lands on the default page.
  • Locale-aware: each CPP can carry localized metadata and screenshots per App Store localization you enable.
  • Cap and lifecycle: Apple limits how many CPPs you can have active; treat them as campaign assets, not infinite landing pages.
  • Not a second app: do not use CPPs to invent a different product identity that App Review would reject on the default page.

CPP localization is not a dump of your default page into another language. It is rewriting a campaign-specific story so a shopper in that storefront language understands the same offer your ad promised — within App Store rules.

Which fields localize on a custom product page

Treat a CPP as a focused product-page subset. Exact availability can shift with App Store Connect updates, so verify in ASC for your account — but the localization jobs usually look like this:

  • Promotional text: short, rotatable message above the description — often the first string you localize per campaign.
  • Screenshots and app previews: the highest-impact CPP differentiator; localize UI language, captions, and cultural framing, not only crop.
  • Deep link / custom product page destination: ensure the path still works for that market’s build and onboarding.
  • Default page fields you do not override still come from the localization’s default listing (name, subtitle, description, keywords, what’s new) — keep those strong so any fallback still converts.
  • Icon and primary listing identity: shared with the app; do not expect a CPP to rebrand the whole product.

When you plan to localize App Store custom product pages, inventory every creative and string the CPP actually owns, then map each to locales you will fund. Gaps (English screenshots under a German CPP URL) feel broken, not “international.”

When to use a CPP vs the default product page

Default pages win broad discovery and brand consistency. CPPs win when the click context is specific.

  1. Use the default page for organic search, browse, and generic brand links — keep it localized and evergreen.
  2. Use a CPP when paid or partner traffic arrives with a promise the default gallery does not lead with (e.g. a new feature, vertical, or seasonal offer).
  3. Use separate CPPs when creatives conflict (B2B vs consumer screenshots) so neither story dilutes the other.
  4. Skip a new CPP when you only need a keyword tweak — that belongs in default metadata localization, not another page.
  5. Retire or refresh CPPs when the campaign ends so stale screenshots do not become the face of paid traffic.

If every ad could land on the default page without confusion, you may not need a CPP. If the ad shows a feature the default screenshots bury, localize a CPP — do not hope shoppers scroll.

App Store Connect workflow for CPP localization

Operational discipline matters as much as copy quality. A workable sequence:

  1. Confirm the default localizations you need already exist and pass App Review for metadata — CPPs lean on that foundation.
  2. Create the custom product page in App Store Connect and name it for humans (campaign + date), not for shoppers.
  3. Add or enable localizations on the CPP for every storefront where the campaign will spend.
  4. Upload locale-specific screenshots and previews; verify device sizes and that UI language matches the localization.
  5. Write promotional text (and any other CPP-owned copy) per locale — short, campaign-true, review-safe.
  6. Generate and store the CPP URL; attach it only to ads and placements for that story and those countries.
  7. Submit for review when required; do not assume English approval covers every new locale creative.
  8. QA with a VPN or regional tester: open the CPP URL in the target storefront language and confirm screenshots, text, and install path.

Teams that already localize default listings with a structured pipeline — spreadsheets or tools like App Store Localizer (https://asolocalization.com) — should extend the same locale checklist to CPP assets so campaign pages do not become the weak link.

ASO tips for localized custom product pages

CPPs do not replace default-page ASO, but they still convert. Apply the same craft:

  • Message match: the first screenshot and promo text should echo the ad’s promise in that language — not a generic brand reel.
  • One job per CPP: do not stuff three features into one gallery; run another page if the story changes.
  • Locale-native screenshots: translated UI and captions beat English UI with a translated caption bar.
  • Keep default metadata strong: keywords and description still matter when shoppers bounce to the standard page or discover you organically.
  • Measure per CPP and locale: install rate and CPA by page URL and country beat blended dashboard vanity.
  • Align with subtitle and name: CPP creatives should not contradict the localized identity on the default page.

Localized custom product pages ASO is coherence under pressure: paid traffic is impatient. If the storefront language and the creative language disagree, you paid for confusion.

Common mistakes that waste CPP and locale budget

  • English-only CPPs pointed at non-English campaigns — high spend, low trust.
  • Reusing default screenshots that do not show the advertised feature.
  • Translating promo text literally until it truncates or sounds like a slogan generator.
  • Leaving stale seasonal CPPs live after the campaign — shoppers land on last quarter’s story.
  • Creating too many near-duplicate CPPs instead of localizing fewer stronger ones.
  • Skipping review/QA in the target locale and discovering broken deep links after spend starts.
  • Treating CPP localization as a one-off design task instead of part of the same metadata release train as name, subtitle, and description.

Avoid those, and App Store Connect custom product page localization becomes a repeatable growth surface: same app, sharper story, language that matches the click.

A simple CPP localization checklist

  1. Campaign promise written in one sentence per priority locale.
  2. Screenshot set that proves that promise with localized UI.
  3. Promo text within limits, review-safe, and on-message.
  4. CPP URL mapped to ads by country and language.
  5. Default listing localizations already healthy for fallback and organic.
  6. Post-launch check: open the CPP in each funded storefront before scaling spend.

If you want help turning default and campaign metadata into consistent locale packs, App Store Localizer at https://asolocalization.com is built for that workflow — including the listing fields CPPs still depend on when shoppers explore beyond the custom page.