# In-app event reminders as a demand signal before launch

> Track how many people tap Reminder on an App Store in-app event before it starts, and use that as the first read on whether the event pitch is strong enough.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/in-app-event-reminders-as-demand-signal-before-launch/
- Source: [developer.apple.com](https://developer.apple.com/help/app-store-connect/view-app-analytics/view-in-app-event-metrics)
- GrowthDex source hub: [App Store Connect Help](/sources/app-store-connect-help-developer-apple-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: App Store, Analytics, Launch
- Stages: event launch, mobile analytics, demand validation, creative testing
- Key metric: Apple exposes Reminders as a first-class in-app event metric alongside impressions and event detail page views.

## Why this can grow

Event launches usually get judged too late, after the live slot has already been spent. Apple's in-app event analytics give an earlier clue. Reminder taps show whether the event card and detail page are convincing enough for someone to ask the App Store to bring them back later. That makes reminders a useful pre-launch demand signal. If impressions are high and reminders stay flat, the event story probably needs work before more traffic gets pushed into it.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where in-app event reminders as a demand signal before launch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the App Store and Analytics channel.
3. Use the evidence from developer.apple.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Apple's in-app event metrics count event impressions, event detail page views, and reminders, defined as the number of times users tap the reminder button to request a notification when the event begins.

## Adjacent tactics in the same lane

- [Offer code reference names as a redemption ledger](/growth-ideas/offer-code-reference-names-as-redemption-ledger/) - same source, 2 shared channels
- [Win-back eligibility report for reactivation prioritization](/growth-ideas/win-back-eligibility-report-for-reactivation-prioritization/) - same source, 2 shared channels
- [Keyword-triggered custom product pages in App Store search](/growth-ideas/keyword-triggered-custom-product-pages-in-app-store-search/) - same source, 1 shared channel
- [App Store tags as clickable discovery entities](/growth-ideas/app-store-tags-as-clickable-discovery-entities/) - same source, 1 shared channel

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The App Store surface should know who it is for](/blog/the-app-store-surface-should-know-who-it-is-for/) - mobile growth, brand trust, retention

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.