App Store In-App Events in Simplified Chinese — zh-Hans Event Cards for China
You localized the default listing, maybe even the Custom Product Page — then published an In-App Event whose event name, short description, and long description are still English on the China storefront.
IAE cards in Today, Search, and on your product page pull from a separate per-event localization matrix in App Store Connect. Empty or English-only zh-Hans event fields mean China buyers see fallback copy while your main listing reads native.
AppLocale writes paste-ready zh-Hans event metadata aligned with your listing voice — not machine-dumped, not artwork design, not event scheduling.
Operator guidance only — no impression guarantee, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS developers — US, UK, EU, Canada, Australia — who:
Already ship or plan to ship In-App Events (seasonal challenges, livestreams, major updates, limited-time modes)
Target the China App Store or zh-Hans device language with those events
Have a zh-Hans default listing (or are finishing one) but left event metadata in English or machine translation
Need paste-ready Connect text — not a designer to rebuild event card artwork from scratch
If your main product page is still English on the China storefront, start with China App Store still shows English or the AppLocale product page for default listing fields first. In-App Events sit on top of a localized listing — they do not replace it.
In-App Events are not your listing — three layers
Teams conflate three different copy surfaces when planning a China launch. Each has its own Connect editor and localization dropdown.
1 — Default listing (product page)
Name, subtitle, keywords, description, promotional text, What's New, screenshots, and App Preview on the zh-Hans localization row. Organic Search and browse traffic see this page. AppLocale's core $79 deliverable covers these fields. See localize an iOS listing for China.
Up to 35 per-app variants with their own subtitle, promotional text, description, and screenshot sets — linked from paid ads or Product Page Optimization. Localizing the default listing does not localize CPPs. See Custom Product Page in Simplified Chinese.
3 — In-App Events (time-boxed cards)
Each event is a separate record under In-App Events in Connect. Apple publishes up to 10 events on the App Store at a time (15 approved in Connect). Every event carries its own localized event name, short description, long description, badge, media uploads, storefront availability, and schedule. Filling zh-Hans on the default listing does not propagate to events you create afterward.
Where zh-Hans In-App Events appear
When Apple surfaces your event, buyers on the China storefront see an event card — image or video, event name, short description, and badge — in places like the Today tab and Search. Tapping opens an event details page with the long description and larger portrait media.
Event card — landscape media (16:9), event name (up to 30 characters), short description (up to 50 characters)
Event details page — portrait media (9:16), long description (up to 120 characters), deep link to in-app content
Product page — upcoming and live events listed chronologically; high-priority events can sort ahead of normal priority
Apple chooses whether and where to feature any given event. Complete zh-Hans metadata improves locale fit when your event is shown — it does not force placement or impressions.
Apple Connect field limits (In-App Event text)
Per Apple's In-App Events documentation, localized text fields are capped as follows. CJK characters count toward the same limits as Latin letters — plan shorter Chinese phrasing than English drafts.
Reference name — up to 64 characters; internal to Connect only, not visible on the App Store
Event name — up to 30 characters; appears on the event card and details page. Apple recommends a distinctive event title in title case (e.g. a named season or challenge), not a generic call to action
Short description — up to 50 characters; summarizes the event on the card. Apple recommends sentence case
Long description — up to 120 characters; extra context on the details page (rewards, participation notes). Apple recommends sentence case
Event card media and event details page media are separate image or video uploads with fixed aspect ratios — not text fields. If your English event artwork has embedded headline text, translating that requires redesigning the asset; AppLocale delivers Connect text only.
Common mistakes on China-targeted In-App Events
English event copy on a zh-Hans listing — the product page reads native; the event card still shows Latin script fallback
Machine-translated event names — 30 characters of formal 翻译腔 that does not match your listing tone or game genre vocabulary
Generic English titles reused verbatim — "Live Stream Event" or "Limited Time Offer" instead of a named event Apple can distinguish on the card
Long description stuffed with keywords — the 120-character slot is for participation context, not ASO keyword packing from your main description
Assuming one zh-Hans paste covers all events — each event needs its own localization row; copying event A's text into event B reads wrong when rewards or dates differ
Mismatched listing promise — event short description advertises a feature your zh-Hans description never mentions, or uses payment vocabulary inconsistent with your IAP copy
Untranslated text in event artwork — Connect text is Chinese but the 16:9 card image still shows English headlines (a design fix, not a metadata paste)
Better zh-Hans event metadata reduces friction when users tap Open — it does not replace in-app localization, deep link testing, or Apple's editorial choices about featuring.
What good zh-Hans In-App Event copy looks like
Apple's guidance favors specific event names and accurate summaries. For China storefront events, align tone with your existing zh-Hans listing:
Event name (30 chars) — name the season, challenge, or collab: "夏日排行榜挑战" not "精彩活动等你来"
Short description (50 chars) — one crisp outcome: who can join, what happens, any time window — within the character cap
Long description (120 chars) — rewards, eligibility, or subscription note if participation costs extra — mirror vocabulary from your IAP localization when relevant
Voice match — casual game vs professional tool; same 你/您 and punctuation habits as your description field
Schedule honesty — dates and times are set in Connect, not in copy; do not promise "starts tomorrow" in text if publish dates differ by storefront
Connect checklist before you order copy
Open In-App Events — Connect left sidebar → select the event (or create one with a unique reference name up to 64 characters)
Select Chinese (Simplified) — language dropdown under Event Information; adding zh-Hans here is separate from the App Store tab listing row
Audit the three text fields — event name, short description, long description saved in zh-Hans, not placeholder English
Confirm China in event availability — Country or Region Availability must include China if the event should appear on that storefront (subject to app availability)
Review media separately — card and details assets may still carry English embedded text; plan a design pass if needed
Test the deep link — Open on the event details page should land in the right in-app screen; copy cannot fix a broken URL
Submit for review — events are reviewed independently of app binary versions
What AppLocale delivers
For one In-App Event, paste-ready Simplified Chinese metadata rewritten from your English event copy:
Event name — up to 30 characters, title-case style appropriate for zh-Hans storefront display
Short description — up to 50 characters for the event card
Long description — up to 120 characters for the event details page
Listing alignment — phrasing consistent with your existing zh-Hans product page (send listing URL with intake)
English source alignment — when your en-US event copy also needs tightening, we note both sides in the deliverable
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite from your event brief — not a machine translation dump. Character counts verified before delivery so fields fit Connect caps.
What AppLocale does not do
Does not design event card (16:9) or event details (9:16) artwork or edit event videos
Does not translate text burned into existing image or video assets — only Connect metadata fields
Does not create events, set schedules, choose badges, or configure country availability in Connect
Does not submit events for App Review or manage deep links on your behalf
Does not guarantee In-App Event impressions, Today tab featuring, Search placement, or download lift
Does not rewrite your default listing, CPP, What's New, or IAP rows in the base $79 event-focused deliverable — ask if you need those bundled; see related guides below
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — one event, zh-Hans text fields; listing already localized or in progress
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, English event name / short / long descriptions (or Connect export), target locale (zh-Hans), and event dates if copy should reference timing
Receive files — within 24 hours, paste-ready zh-Hans event fields arrive at your Stripe receipt email
Paste in Connect — In-App Events → your event → Chinese (Simplified) → save → submit for review
Do In-App Events use the same copy as my default App Store listing?
No. Each In-App Event has its own localized metadata in App Store Connect — event name, short description, and long description — separate from your default listing's title, subtitle, description, and keywords. A complete zh-Hans listing row does not auto-fill In-App Event fields.
What are Apple's character limits for In-App Event text fields?
Per Apple's App Store Connect documentation: event name up to 30 characters, short description up to 50 characters (shown on the event card), and long description up to 120 characters (shown on the event details page). Reference name (internal only) is up to 64 characters. Limits apply per localization.
What do I send after AppLocale payment?
Your live App Store listing URL, your current English (or partial zh-Hans) event name, short description, and long description, which event in Connect (reference name or screenshot), 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.
Can you localize event card images?
No. Event card and details page media are uploads you provide. We rewrite Connect text fields. If your artwork embeds English headlines, you need a designer or video editor to produce zh-Hans visual assets separately.
Will localized events get more impressions in China?
We do not guarantee impressions, featuring, or download growth. Apple controls event surfacing. Complete zh-Hans metadata helps users who do see your event understand it in their language — it is not a placement hack.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not event artwork design, not video editing, not event scheduling or campaign management, not ranking or impression guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans In-App Event copy aligned with your listing
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English event copy. No impression or ranking guarantees. Sold by Fortune Insight, LLC.