Custom Product Pages for Japan: A CPP Strategy

Custom Product Pages (CPPs) let you create up to 35 alternative product pages with different screenshots and promotional text per locale. For Japan, CPPs are one of the highest-leverage tools available — JP users are creative-sensitive, and matching the listing to the traffic source improves conversion meaningfully.

For broader Japanese ASO context, see the Japanese ASO complete guide.

What CPPs Are (Briefly)

Apple's Custom Product Pages are alternate versions of your default product page. Each CPP can have:

A different set of screenshots.
A different preview video.
Different promotional text.
The same app name, subtitle, description, keyword field as the default.

Each CPP gets a unique URL you can use as a landing page from ads, partner links, or share links. Apple records install conversion per CPP for measurement.

CPPs do not affect organic search ranking. Organic search always uses the default page. CPPs only matter for traffic you direct to a specific URL.

Why CPPs Matter More for Japan

Three reasons:

1. JP users are creative-sensitive. They notice and react to screenshot/copy differences more than US users. Personalizing the listing to the traffic source improves CR more in JP than in the US.

2. Apple Search Ads is well-developed in JP. ASA users are landing on the default product page, but they came in via a specific keyword. A CPP tailored to that keyword's intent converts noticeably better.

3. JP users have specific use-case identities. "For students," "for working parents," "for freelancers" — JP users look for apps that match their identity. CPPs let you signal "this is for you" to a segment.

A Workable CPP Plan for Japan

For a typical mid-sized consumer app targeting Japan, this CPP setup covers the major leverage:

CPP 1: Default page (organic search)

Optimized for the user who arrived via App Store search. Screenshots emphasize the most-searched feature; promotional text addresses the most-likely user intent.

CPP 2: Apple Search Ads — primary keyword

Tailored to your top-volume search keyword. If the keyword is 「家計簿」, the CPP screenshots lead with the budgeting feature and the promotional text is optimized for someone actively searching "household budget app."

CPP 3: Apple Search Ads — secondary keyword

Same logic for your second-priority keyword theme. If you target both 「家計簿」 and 「貯金」, the second CPP leads with the savings feature.

CPP 4: Web inbound (your own marketing site)

For users who tap "Download on the App Store" from your marketing site. They've already seen marketing copy; the CPP can be more feature-detailed and less hook-heavy.

CPP 5: Use-case A (e.g., for students)

Screenshots show the app being used by a student demographic; promotional text addresses student-specific value props. Used in marketing campaigns or partner placements targeted at students.

CPP 6: Use-case B (e.g., for working parents)

Same logic for the second segment.

This is 6 CPPs. You can scale further (up to 35) if you have meaningful UA channels or segments to support. But the diminishing returns kick in fast — going from 1 to 6 is high impact; going from 10 to 25 is mostly noise.

What to Vary Across CPPs

The variables you control:

Element	Vary?
App name	No (fixed across CPPs)
Subtitle	No
Description	No
Keyword field	No
Screenshots	Yes
Preview video	Yes
Promotional text	Yes

The biggest leverage is screenshots. The promotional text is a bonus — Apple shows it at the top of the description, so use it to add a CPP-specific hook.

What to vary in screenshots

The first 3 screenshots (the ones the user sees before scrolling).
The tagline copy (matched to the traffic source's intent).
The trust signals featured (relevance to the audience).
The order of features highlighted.

The remaining screenshots (4–8) can stay similar across CPPs — they're for users who scroll deep, and depth-readers tend to convert similarly across CPPs.

CPP + Apple Search Ads

Apple Search Ads is the single best use case for CPPs in Japan. ASA campaigns target specific keywords; tailoring the landing page to the keyword's intent measurably improves conversion.

A workable setup:

Campaign 1 (exact match: 家計簿) → CPP 2 (家計簿-tailored)
Campaign 2 (exact match: 貯金) → CPP 3 (貯金-tailored)
Campaign 3 (search match) → Default page (low-precision traffic)
Campaign 4 (brand keyword) → Default page (already-aware traffic)

Within each campaign, set the CPP at the keyword/ad-group level in App Store Connect. ASA measures install rate per ad-group, letting you iterate on CPP creative based on real data.

We measure 10–25% conversion lift from properly targeted CPPs in JP ASA campaigns, depending on category.

CPP for Custom Audiences (Web)

If you run paid social or content marketing pointing to the App Store, use CPPs to match the campaign's narrative.

Examples:

Twitter/X campaign about a new feature → CPP leading with that feature.
Influencer partnership → CPP with promotional text mentioning the influencer.
Press feature → CPP with promotional text crediting the press source.
Seasonal campaign → CPP with seasonal screenshot variants.

Each campaign URL points to its CPP; you measure CPP-specific install conversion.

Promotional Text on CPPs

The 170-character promotional text is per-CPP. Use it for:

Time-bound campaign callouts ("3月キャンペーン中、3か月無料").
Channel-specific framing ("公式サイトをご覧の皆様へ").
Use-case context ("学生限定の特典あり").
Social proof relevant to the traffic source ("〇〇メディアで紹介されました").

What not to put:

Generic marketing copy that's the same across CPPs.
Information that should be in the description (it'll get truncated).

Avoiding CPP Pitfalls

Pitfall 1: Treating CPPs as A/B tests

CPPs are not A/B test variants. Apple's Product Page Optimization (PPO) is a separate feature for A/B testing. CPPs are for traffic-source-specific landing pages.

Pitfall 2: Building CPPs without traffic plans

A CPP with no traffic source pointing to it is wasted creative work. Plan the traffic before building the page.

Pitfall 3: Inconsistent voice across CPPs

The user can theoretically navigate from a CPP to your full description. If the CPP is breezy and the description is formal, the inconsistency is jarring. Pick a brand voice and stay close to it across CPPs.

Pitfall 4: Running CPPs without measuring

Apple gives you per-CPP install attribution. Use it. If a CPP doesn't outperform the default for its traffic source, kill it and retry.

Localization Quality Bar for JP CPPs

Each CPP screenshot set needs the same localization rigor as the default page:

Native Japanese taglines, not translations.
JP-style screenshot layout (see Japanese App Store screenshots).
Localized promotional text.
App-side screens in the CPP screenshots showing Japanese UI.

A CPP shipped with rushed creative typically underperforms the default page even with good targeting — the quality bar matters.

Measurement

Track per-CPP:

Impressions (how many people saw the page).
Install conversion rate (installs per impression).
Tap-through rate from screenshots (Apple provides scroll/interaction signals).
Post-install retention by CPP source (best measured via deep-link attribution to identify which CPP a user came from).

Compare each CPP to the default page for its same audience. If the CPP doesn't beat the default for its target audience, the CPP isn't doing its job.

A Self-Check Before Launching CPPs

Each CPP has a defined traffic source — UA channel, ad group, or partner placement.
Each CPP has 3+ unique screenshots tailored to its audience.
Promotional text is unique per CPP and addresses the audience.
CPP creative meets the same JP localization quality bar as the default page.
Per-CPP install attribution is wired up in measurement.

Where to Go Next

We design and write Custom Product Pages for Japanese listings, including the screenshot creative, promotional text, and ASA-aligned strategy. Contact us to scope a CPP engagement.