App Store Product Page Optimization in Simplified Chinese — zh-Hans PPO Treatments for China
You launched a Product Page Optimization test in App Store Connect — Treatment B has a sharper en-US subtitle, fresh promotional text, and new screenshot caption lines.
Organic traffic on the US and UK storefronts sees the experiment. On the China storefront, buyers still land on the English control — or you never added a zh-Hans treatment row at all.
PPO is not Custom Product Pages. Each treatment variant has its own per-locale copy matrix. AppLocale writes paste-ready zh-Hans subtitle, promotional text, and screenshot caption lines for your treatment fields — not machine-dumped, not test management, not screenshot design.
Operator guidance only — no conversion guarantee, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
PPO treatments vs Custom Product Pages — two different tools
Teams conflate Apple's two product-page experiment surfaces. They share some field names but serve different traffic and live at different URLs.
Product Page Optimization (PPO)
Built into the default product page in App Store Connect. You define a control and up to three treatment variants with alternate subtitle, promotional text, and screenshot sets. Apple splits organic App Store traffic between variants and reports impression and conversion metrics. The URL stays your standard product page — no campaign deep link.
Traffic source: organic browse and Search on each storefront where the test runs
Per-locale: each treatment needs its own zh-Hans subtitle, promotional text, and screenshot captions if you want localized variants on the China storefront
You configure the test; Apple assigns visitors — we do not run or analyze it
Custom Product Pages (CPP)
Separate page variants with unique URLs for paid user acquisition, influencer codes, email campaigns, or Apple Search Ads deep links. Up to 35 per app. Localizing PPO treatment copy does not localize CPPs, and vice versa. See CPP localization guide.
This page covers zh-Hans copy for PPO treatment fields only — not CPP campaign pages, not default listing fields outside an active test, and not Apple Search Ads bid management. For ASA landing-page mismatch, see Apple Search Ads in China.
Why China storefront PPO often stays on the English control
Connect treats PPO localization the same way as the default listing matrix: each treatment variant has independent rows per language. Common failure modes:
Treatments built en-US only — Treatment B subtitle and promo text exist in English; zh-Hans row is empty, so China traffic falls back to control copy
Assuming default zh-Hans listing propagates into treatments — your main listing row is localized, but PPO treatment B carries its own fields that do not inherit from default or from other treatments
Localized screenshot art, English caption strings — design exported Chinese overlay frames but Connect caption metadata for treatment B is still Latin script
One treatment localized, siblings forgotten — Treatment B has zh-Hans; Treatments C and D do not, yet all run on the China storefront
Attributing low China conversion to audience fit — the experiment never showed a Chinese variant; the control was the only option zh-Hans visitors could see
Filling zh-Hans treatment fields gives China-assigned traffic a fair comparison against your English control — it does not guarantee win rates, impression share, or ranking movement.
Which PPO fields AppLocale rewrites for zh-Hans
For one PPO treatment variant, we deliver paste-ready Simplified Chinese strings for the copy slots Apple exposes in the treatment editor:
Subtitle — treatment-specific hook under the app name (~30 characters for zh-Hans); can differ from both control and default listing subtitle when the test angle targets a segment
Promotional text — 170-character updatable slot above the description; often carries the test's time-limited hook. See also promotional text guide
Screenshot overlay / caption lines — short text strings tied to gallery frames in this treatment's screenshot set; not the image files themselves. See screenshot captions guide
App name, keyword field, description body, What's New, IAP metadata, and in-app UI strings sit outside this PPO-treatment-focused deliverable unless you bundle a default listing rewrite via the AppLocale product page. We do not redesign screenshot PNGs or edit App Preview videos.
Connect workflow — where zh-Hans treatment copy goes
App Store Connect → your app → Product Page Optimization — open the active or draft test
Select the treatment variant — Control, Treatment B, C, or D (not all treatments need zh-Hans if you only test one angle in China)
Open localization — language dropdown under the treatment's subtitle, promotional text, and screenshot set
Add or edit Chinese (Simplified) — paste zh-Hans subtitle, promotional text, and caption strings; verify character counts against Apple caps
Confirm screenshot set assignment — this treatment's gallery may differ from control; captions must match the frames uploaded for this variant
Save and let the test run — Apple assigns storefront traffic; you read results in Connect analytics
We deliver copy files. You paste, save, and manage test lifecycle — start, pause, end — in Connect.
Common PPO + zh-Hans mistakes
Running a multivariate test in en-US and expecting zh-Hans storefront visitors to see Treatment B's English subtitle
Copy-pasting the default listing's zh-Hans subtitle into every treatment — losing the angle that justified a separate variant
Machine-translating treatment promotional text word-for-word — 170 characters of formal 翻译腔 that mismatches your listing voice
Localizing control only and leaving all treatments English — China traffic never enters the experiment you think you are running
Confusing PPO with CPP — optimizing campaign landing URLs while the organic PPO test on the default page is still English-only on zh-Hans
Expecting AppLocale to pick winners — we supply copy; you interpret Connect conversion metrics
What AppLocale delivers
Simplified Chinese (zh-Hans) — PPO treatment subtitle, promotional text, and screenshot caption lines, paste-ready for one treatment variant
English alignment notes — when your en-US treatment copy also needs tightening, we flag mismatches in the deliverable
Field map — which Connect slots each block belongs to on the treatment's zh-Hans localization row
Character verification — subtitle ~30, promotional text 170, captions within frame limits before delivery
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite from your treatment brief — not a machine translation dump. We preserve test intent (segment hook, offer language, feature emphasis) in native Simplified Chinese.
What AppLocale does not do
Does not create, launch, pause, or analyze Product Page Optimization tests in App Store Connect
Does not configure traffic allocation, storefront scope, or test duration
Does not localize Custom Product Pages, In-App Events, or default listing fields outside the scoped treatment (unless bundled separately)
Does not manage Apple Search Ads campaigns, bids, or creative — see ASA guide for landing-page context only
Does not design screenshot images, produce overlay artwork, or edit App Preview videos
Does not translate in-app UI, StoreKit strings, or app binary resources
Does not guarantee PPO conversion lift, impression share, keyword rank, or download growth
Is not QuantRadar, not investment advice, and not legal review
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — one PPO treatment variant, zh-Hans subtitle + promotional text + screenshot captions
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, which treatment variant (Control, B, C, or D), current English treatment copy and caption lines, target locale (zh-Hans), and deadline if your test window is fixed
Receive files — within 24 hours, paste-ready zh-Hans treatment strings arrive at your Stripe receipt email
Paste in Connect — Product Page Optimization → your treatment → Chinese (Simplified) → save
FAQ
What is Product Page Optimization (PPO) vs Custom Product Pages (CPP)?
Product Page Optimization is Apple's built-in A/B testing on your default product page — you create treatment variants with alternate subtitle, promotional text, and screenshots, and Apple splits organic traffic between control and treatments. Custom Product Pages are separate campaign URLs with their own deep links for paid ads or influencer codes. PPO treatments live on the default page URL; CPPs are distinct URLs. Localizing one does not localize the other.
Why does my zh-Hans PPO test still show English copy?
PPO treatment fields are localized per locale in App Store Connect. If you built treatments in en-US only, zh-Hans storefront visitors see the English control or empty fallback — not your US treatment copy. Each treatment variant needs its own zh-Hans subtitle, promotional text, and screenshot caption strings if you want Chinese buyers to see a localized variant.
What do I send after AppLocale payment?
Your live App Store listing URL, which PPO treatment variant you want localized (Control, Treatment B, C, or D), current English treatment subtitle, promotional text, and screenshot caption lines, target locale (zh-Hans), and any deadline. Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Does AppLocale run my Product Page Optimization test?
No. You create treatments, set traffic allocation, and read results in App Store Connect. We deliver copy files only — we do not log into your account, start experiments, or interpret conversion data.
Can you localize all three treatments in one order?
The base $79 deliverable covers one treatment variant's zh-Hans copy fields. If you need multiple treatments localized, note that in intake — we can scope additional variants separately.
Will zh-Hans treatment copy improve my PPO win rate in China?
We do not guarantee conversion lift or statistical significance. Complete zh-Hans treatment copy lets China-assigned traffic see a localized variant instead of English-only control — it is not a placement or algorithm hack.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not PPO test setup or analysis, not Custom Product Page localization, not Apple Search Ads management, not screenshot image design, not in-app or binary localization, not ranking guarantees, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans PPO treatment copy for the China storefront
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English PPO treatment copy. No conversion or ranking guarantees. Sold by Fortune Insight, LLC.