Shop Storefront Brief · Issue 6

In-App Event pages are your time-boxed campaign surface. Ship one event whose card copy matches the CPP you built last week.

2026-08-27 · Fortune Insight, LLC · Operator intel for indie iOS teams. This page covers In-App Events in App Store Connect — event cards, event details pages, localization, and deep links — not a commission or IAP rate change. If you only track fee worksheets, Connect rules did not change because of this note.

What happened / why this follows Issue 5

Issue 5 treated Custom Product Pages (CPP) as the always-on landing surface: keyword-specific screenshot sets, unique ?ppid= URLs, and ASA ad-group assignments. CPP is the baseline storefront variant you control for paid traffic.

In-App Events have been a Connect feature since 2022 and add a different layer: a time-boxed campaign surface with its own event card, event details page, and App Review gate. An event can sit on top of your default listing or be promoted independently — on your product page, in App Store search, and in editorially curated selections on the Today, Games, and Apps tabs.

This issue is the next step in the storefront-surface thread: if you already shipped one CPP from Issue 5, do not build a second CPP yet. Ship one In-App Event whose card copy matches that same keyword intent, deep-links into the matching in-app surface, and runs in a window where you are not also A/B testing conflicting PPO screenshots.

Default listing vs CPP vs PPO vs In-App Event — operator map

Four different Connect tools. Mixing them up is the most common indie mistake after enabling 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 — always-on landing for paid traffic (Issue 5)
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
In-App Event page	Time-boxed event card + event details page with localized name, short/long description, and event media	Product page visitors, search (event card or direct event search), Today/Games/Apps editorial surfaces	Limited-time campaign — challenge, premiere, major update — with deep link into the matching in-app moment

Rule of thumb: CPP = always-on paid landing. In-App Event = time-boxed campaign layer on the default page and discovery surfaces. PPO = organic experiment on the default page. Do not run a PPO screenshot test and an In-App Event promoting conflicting copy in the same window — you will not know which surface moved conversion.

How an event page is localized in Connect

In-App Event metadata is per locale, separate from your default listing row. Each localization includes:

• Event name — up to 30 characters, title case, distinctive event title (not a call-to-action tagline).
• Short description — up to 50 characters, sentence case; displays on the event card in search and on the product page.
• Long description — up to 120 characters, sentence case; displays on the event details page after the user taps the card.
• Event card media — 16:9 image or video (1920×1080 minimum). Event details page media is 9:16 portrait (1080×1920 minimum).

Operator checklist for one event + one locale:

• Fill every locale you will serve. Adding a zh-Hans row does not auto-translate event copy. Empty localizations fall back to your primary locale — often English.
• Event image copy is part of the image. Same lesson as Issue 5 screenshot overlays: text baked into PNGs does not auto-translate. Re-export event card art for each locale if overlays carry the keyword intent.
• Apple discourages text and logos in event media. Prefer visual continuity between card and details page. If you must use overlay copy, keep it inside the 4+ Creative Assets ceiling from Issue 4 — no price callouts, no unverifiable badges.
• Character limits are hard caps. Name 30, short 50, long 120 — counted per locale. Machine translation often overflows; trim before upload.
• App Review reviews the event separately. You can submit without a new app binary. Budget 24–48 hours; events with incomplete localizations or price claims in metadata get rejected.

Packing one event to the same intent as your first CPP

If Issue 5 left you with one CPP aimed at a specific keyword intent — e.g. "budget tracker" overlays on a CPP screenshot set — your In-App Event should reinforce that same intent, not introduce a second message.

Step	Connect action
1 · Reuse the keyword intent	Pull the keyword you built CPP #1 for (Issue 5). Event name and short description should echo the same value prop — not a generic "check out our app" promo.
2 · Match card copy to CPP screenshot overlays	If CPP screenshots say "Track expenses in one tap," the event short description should say the same thing in 50 characters — not a different feature angle.
3 · Deep link into the matching in-app surface	Connect → In-App Events → your event → Event Deep Link. Use a universal link (recommended) to the screen that delivers the CPP promise — budget view, challenge lobby, new content tab. Test by pasting the URL into Notes and tapping.
4 · Set a real time window	Events last up to 31 days and can appear on the App Store up to 14 days before start. Pick start/end dates that cover your campaign — not an evergreen placeholder.
5 · Do not conflict with PPO	If a PPO screenshot test is live on the default page, pause it or wait until the event ends. Running both in the same window splits traffic across competing creative.
6 · Submit for review	Connect → In-App Events → Add for Review. Approved apps can submit events without a new binary. Up to 10 events published at once; up to 15 approved in Connect.

Operator catches: event badges (Challenge, Competition, Live Event, Major Update, New Season, Premiere, Special Event) display above the title — do not repeat the badge type in the event name. App Review rejects price claims in event metadata. Editorial featuring on the Today tab is discretionary — submitting an event does not guarantee placement.

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 of Today-tab featuring. You can share events with Apple's editorial team for consideration; placement is discretionary.
• Not a substitute for CPP on ASA traffic. Event cards appear on the default product page and discovery surfaces; ASA ad groups still need CPP assignments for keyword-specific landing pages.
• Not a price-promotion tool. Apple explicitly lists standalone price discounts without new content as a poor In-App Event candidate.
• If you only sell US IAP inside the App Store and do not run campaigns: no need to ship an In-App Event this week unless you have a real time-boxed feature launch.

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. In-App Event and CPP 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.

• Custom Product Pages + ASA packing: keyword-specific landing pages — Issue 5
• 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

• If you shipped CPP #1 from Issue 5: open Connect → In-App Events → Create. Pick a badge that matches your launch (Major Update, New Season, Challenge, etc.).
• Write event name, short description, and long description in every locale your CPP serves — card copy must match CPP screenshot overlay intent.
• Upload 16:9 event card media and 9:16 details-page media. Keep visuals inside the 4+ ceiling; avoid price text in metadata or images.
• Set a universal-link deep link to the in-app surface that delivers the CPP promise. Test on device before submitting.
• Do not start a second CPP or a conflicting PPO screenshot test in the same window. Submit the event for App Review and track impressions in Connect App Analytics after publish.

Sources: Apple · In-App Events · Apple · Offer In-App Events (Connect Help) · Apple · Submit an In-App Event · Apple · In-App Event media specifications · Apple · App Store asset best practices