# The App Store surface should know who it is for > Why promoted purchases, segmented offer codes, win-back links, event reminders, and eligibility reports usually beat treating every App Store visitor like the same buyer. - Canonical HTML: https://growth.iangoh.com/blog/the-app-store-surface-should-know-who-it-is-for/ - Published: 2026-05-29 - Updated: 2026-05-29T01:45:00Z - Categories: mobile growth, brand trust, retention - Niches: consumer apps, SaaS, creator tools, AI products, marketplaces ## On this page - The product page can sell a specific paid object before the install - Discounts work better when they know whether the customer is new, current, or gone - Win-back gets stronger when the route is direct - Events should show demand before the event starts - The App Store is better when it stops pretending every visitor is starting from zero ## Start with these related tactics - [Promoted in-app purchases as a pre-install merch shelf](/growth-ideas/promoted-in-app-purchases-as-preinstall-merch-shelf/): Promote the exact in-app purchases you want discovered on the App Store so buyers can see paid content, offers, or add-ons before they ever install the app. - [Subscription offer codes by lifecycle state](/growth-ideas/subscription-offer-codes-by-lifecycle-state/): Issue different App Store subscription offer codes for new, active, and expired subscribers instead of blasting the same discount at every customer state. - [Win-back redemption URLs through owned channels](/growth-ideas/win-back-redemption-urls-through-owned-channels/): Send lapsed subscribers straight into the App Store win-back offer with the redemption URL instead of asking them to rediscover the discount on their own. A lot of App Store work quietly fails because the page is asked to do one job for three different people. A first-time visitor needs the cleanest possible reason to install. An active subscriber needs a reason to buy the next thing. A lapsed subscriber needs a reason to come back without feeling tricked. When the store surface treats those states as one audience, the route gets muddy fast. The interesting part is that Apple already gives teams a set of branching tools. Most teams just do not use them as route design. ## The product page can sell a specific paid object before the install The clearest acquisition move in this batch is [promoted in-app purchases as a pre-install merch shelf](/growth-ideas/promoted-in-app-purchases-as-preinstall-merch-shelf/). If the real buying trigger is a pack, membership, class, or upgrade, it helps to let the store show that object directly instead of asking every visitor to infer it from the default app story. I would keep that next to [App Store tags as clickable discovery entities](/growth-ideas/app-store-tags-as-clickable-discovery-entities/) and [keyword-triggered custom product pages in App Store search](/growth-ideas/keyword-triggered-custom-product-pages-in-app-store-search/). One sharpens what can be discovered. The others sharpen which branch of the listing the buyer reaches. ## Discounts work better when they know whether the customer is new, current, or gone [Subscription offer codes by lifecycle state](/growth-ideas/subscription-offer-codes-by-lifecycle-state/) matters because one discount usually does too many jobs badly. The team needs one route for acquisition, another for retention nudges, and another for reactivation. Apple lets you separate those states, so the offer can match the customer instead of flattening every user into one promo bucket. That belongs beside [App Store custom page selection by subscription quality](/growth-ideas/app-store-custom-page-selection-by-subscription-quality/). One decides which offer reaches which audience. The other checks whether that audience was worth bringing in. ## Win-back gets stronger when the route is direct The operational move here is [win-back redemption URLs through owned channels](/growth-ideas/win-back-redemption-urls-through-owned-channels/). If the team already knows who drifted away, it should not make those people go wander through the App Store hoping they notice the offer. I would pair it with [win-back eligibility reporting for reactivation prioritization](/growth-ideas/win-back-eligibility-report-for-reactivation-prioritization/). One gives you the direct path. The other tells you whether the person on the receiving end can actually use it. ## Events should show demand before the event starts I like [in-app event reminders as a demand signal before launch](/growth-ideas/in-app-event-reminders-as-demand-signal-before-launch/) because it gives the team an early read on whether the event pitch is doing its job. Impressions tell you distribution happened. Reminder taps tell you somebody cared enough to ask the store to bring them back. That sits naturally beside [in-app event warmup highlight loop](/growth-ideas/in-app-event-warmup-highlight-loop/) and [App Store acquisition cuts by page type, referrer, and pre-order](/growth-ideas/app-store-acquisition-cuts-by-page-type-referrer-and-preorder/). One handles the event sequence. The other helps you read which route produced the result. ## The App Store is better when it stops pretending every visitor is starting from zero This cluster is strongest for consumer apps, creator tools, AI products, marketplaces, and subscription SaaS with a meaningful mobile surface. If I were tightening one this week, I would ask five plain questions. Which paid object should the store surface before install. Which discounts are for new subscribers, active ones, and lapsed ones. Can a churned user redeem the offer from the channel where you reached them. Are reminder taps strong enough to justify an event push. Is the team contacting people who can actually claim the win-back route. If you want help turning the App Store from one generic listing into a cleaner acquisition and reactivation system, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Promoted in-app purchases as a pre-install merch shelf](/growth-ideas/promoted-in-app-purchases-as-preinstall-merch-shelf/) - App Store, Monetization, Mobile - [Subscription offer codes by lifecycle state](/growth-ideas/subscription-offer-codes-by-lifecycle-state/) - App Store, Lifecycle, Retention - [Win-back redemption URLs through owned channels](/growth-ideas/win-back-redemption-urls-through-owned-channels/) - App Store, Email, Retention - [In-app event reminders as a demand signal before launch](/growth-ideas/in-app-event-reminders-as-demand-signal-before-launch/) - App Store, Analytics, Launch - [Win-back eligibility report for reactivation prioritization](/growth-ideas/win-back-eligibility-report-for-reactivation-prioritization/) - Analytics, App Store, Lifecycle ## Essay chronology - [Newer essay: The App Store route should be judged after the install](/blog/the-app-store-route-should-be-judged-after-the-install/) - mobile growth, analytics, retention - [Older essay: The App Store route should stay intact after the tap](/blog/the-app-store-route-should-stay-intact-after-the-tap/) - mobile growth, app store, localization ## Keep reading - [The Google Play page should keep the promise after the tap](/blog/the-google-play-page-should-keep-the-promise-after-the-tap/) - mobile growth, App Store Optimization, brand trust - [The community should teach the first contribution before it asks for loyalty](/blog/the-community-should-teach-the-first-contribution-before-it-asks-for-loyalty/) - community-led growth, brand trust, retention - [The App Store route should be judged after the install](/blog/the-app-store-route-should-be-judged-after-the-install/) - mobile growth, analytics, retention ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Apple Developer: Promoting your In-App Purchases](https://developer.apple.com/app-store/promoting-in-app-purchases/) · [GrowthDex source hub](/sources/apple-developer-promoting-your-in-app-purchases-developer-apple-com/) - [App Store Connect Help: Set up subscription offer codes](https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-subscription-offer-codes/) · [GrowthDex source hub](/sources/app-store-connect-help-set-up-subscription-offer-codes-developer-apple-c/) - [App Store Connect Help: Set up win-back offers](https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-win-back-offers/) · [GrowthDex source hub](/sources/app-store-connect-help-set-up-win-back-offers-developer-apple-com/) - [App Store Connect Help: View In-App Event metrics](https://developer.apple.com/help/app-store-connect/view-app-analytics/view-in-app-event-metrics) · [GrowthDex source hub](/sources/app-store-connect-help-view-in-app-event-metrics-developer-apple-com/) - [App Store Connect Help: Win-back eligibility report](https://developer.apple.com/help/app-store-connect/reference/win-back-eligibility-report/) · [GrowthDex source hub](/sources/app-store-connect-help-win-back-eligibility-report-developer-apple-com/) ## Editing notes - Kept the essay on one claim: the App Store surface should branch by customer state instead of pretending every visitor is the same. - Used plain objects like paid items, discounts, links, reminders, and reports instead of abstract mobile-growth language. - Cut launch-theater phrasing and tied each section to a route a mobile team can actually inspect or change in App Store Connect. - Ended with an operating checklist and direct advisory CTA instead of a polished summary paragraph. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.