In-App Events: a discovery surface most apps ignore
Most ASO advice stops at the static metadata: name, subtitle, keywords. In-App Events are a separate, underused discovery surface: timely event cards you set in App Store Connect that can appear in search results, on the Today tab, in category pages, and on your own product page. The catch is that they are time-boxed and owner-set, with their own metadata rules, and unlike your hidden keyword field, the event's user-facing name is shown to real people, so it works differently from an indexed field you optimize in private. That distinction shapes everything about how you use them. An In-App Event is not a permanent listing change and not a substitute for keyword work; it is a parallel, time-based layer that earns the store reasons to feature you when something is genuinely happening in your app. Think of your App Store presence as two layers stacked together: the always-on indexed metadata (app name, subtitle, and 100-byte keyword field) that wins searches around the clock, and the timely event layer that earns editorial featuring, surfaces in search alongside your listing, and gives existing visitors a reason to act now. The apps that win discovery treat both layers deliberately. This guide covers what events are, every place they can surface, the metadata fields that matter, cadence and review timing, and how to measure them so they earn their place in your calendar.
What is an In-App Event?
An In-App Event is a timely happening inside your app (a competition, a premiere, a seasonal challenge, a major update, a live event) that you publish through App Store Connect as an event card with art, a name, and a short description. It is not a permanent listing change; it has a start and end date and is meant to surface things happening now. Each card deep-links into the relevant part of your app, so a tap can drop a user straight into the tournament lobby, the premiere, or the new season rather than the generic home screen. Apple allows a limited number of published and approved events at a time, so they are a curated surface, not an endless feed, which means each event should be worth a slot. Events also carry their own lifecycle states in App Store Connect (draft, submitted, approved, published, past), and you can schedule them in advance so the card appears at the right moment. The deep link is more than a convenience: it is the mechanism that turns a discovery card into an in-app action, and getting it pointed at the precise moment of value is what separates an event that converts from one that merely decorates your product page.
Where can an event surface?
An approved event can appear in several places beyond your product page: it can show up in App Store search results, be featured on the Today tab and within category and Games pages, and surface in editorially curated selections. That makes it a discovery channel that reaches users who have not found your app yet, distinct from your indexed metadata, which only helps once someone searches a matching term. It also appears as an event card on your product page itself, giving existing visitors a timely reason to act. The surfaces split into two kinds of reach. The first is owned and rules-based: the event card on your own product page and to people who already follow or have downloaded your app, which you can count on once the event is approved and live. The second is earned and editorial: placement on the Today tab, in curated category collections, and in search beyond your own listing, which Apple's editors and algorithms grant to events that are genuine, well-crafted, and timely. You cannot buy the editorial reach, but you can make your event a strong candidate for it with sharp art, a specific name, an accurate badge, and a real, time-bound hook. The product-page card is the floor; editorial featuring is the upside.
Reference name vs. the user-facing name and badge
Event metadata separates an internal reference name (for your own organization in App Store Connect, never shown to users) from the user-facing event name and short description that people actually see on the card. There is also an event badge, Apple's label like Challenge, Competition, Live Event, Major Update, New Season, Premiere, or Special Event, that you choose to classify the event; the badge is shown on the card and helps users grasp the event type at a glance. Write the user-facing name to be specific and inviting, since unlike the hidden keyword field it is read by humans. The card also carries a deep-link target, event art and short video, and start/end dates with an optional 'event time' for live moments, each part of the metadata Apple reviews and users judge. Choose the badge honestly: labeling a routine update as a 'Premiere' or a minor sale as a 'Special Event' invites rejection and erodes trust when users tap through to nothing special. The user-facing name and description carry localization, so you can and should localize them per storefront the same way you localize your indexed metadata, since the card text is what converts the impression into a tap in each market.
How often should I run events, and who sets them?
Events are owner-set: you create, schedule, and submit them through App Store Connect, and each goes through App Review before it can publish, so plan lead time rather than expecting instant go-live. A steady cadence works better than a one-off: recurring seasonal or content events give the store fresh cards to surface and give users repeat reasons to return. Keep events genuinely timely and tied to something real in the app; padding the calendar with hollow 'events' risks rejection and trains users to ignore your cards. Practical scheduling discipline matters: because review can take time and you want the card live at a precise moment (a holiday, a launch, a tournament start) submit well ahead and use the scheduled publish date rather than racing the approval clock. Build an events calendar that maps to your app's real rhythm: seasonal tentpoles, content drops, recurring competitions, major version launches. A predictable cadence also compounds, because the more reliably you ship real events, the more the store has to surface and the more your audience learns to check back. Reserve your limited active-event slots for the events that genuinely merit them, and retire or let expire the ones that have run their course so a stronger card can take the slot.
What makes an event eligible and likely to be featured?
Approval and featuring are different bars, and clearing both takes care. For approval, the event must describe a real, time-bound happening inside the app, not an evergreen feature dressed up as an event, not a pure discount with nothing behind it, and not a misleading badge. The art and short video must meet Apple's specs and avoid prices, ranking claims, or App Store UI in the imagery; the name and description must match what the user actually experiences after the deep link. For featuring (the earned editorial reach) Apple's editors favor events that are genuinely novel or seasonal, visually distinctive, accurately badged, and tied to a moment users care about. A competition with a clear start, a premiere of new content, or a major new season tends to read as featurable; a recurring 'weekly sale' rarely does. Localize the card so it is eligible to feature in multiple storefronts. And make the deep link land on the exact in-app moment, because a card that over-promises and under-delivers not only fails to convert but can draw rejections on resubmission. Treat each event as an editorial pitch: the cleaner and more honest the package, the better its odds at the surfaces you cannot buy.
How do events fit alongside your keyword strategy?
In-App Events complement, not replace, your indexed metadata. Your app name, subtitle, and keyword field still do the heavy lifting for search ranking; promotional text and description remain non-indexed. Events add a parallel, time-based path to visibility (including appearing in search) that static metadata can't provide. Think of your ASO as two layers: the always-on indexed metadata that wins searches, and the timely event layer that earns featuring and gives the store reasons to surface you when something is actually happening. The interaction is worth being precise about. Do not try to stuff keywords into the event name expecting search-ranking lift the way the keyword field gives. The event surfaces in search as a card tied to your listing, but the heavy text-relevance weighting still comes from name, subtitle, and the 100-byte keyword field, in that order. Instead, write the event name for humans and for clarity, and let it ride alongside the rankings your indexed metadata already earns. The event card can also reinforce a campaign theme (a seasonal push, a new feature) that your screenshots and Custom Product Pages support, so coordinate the messaging across layers. The mental model: indexed metadata is the durable foundation, events are the timed amplifier, and neither substitutes for the other.
How do you measure whether an event worked?
Because events cost real production effort and a scarce active slot, measure them rather than running them on faith. App Store Connect and App Analytics surface event-level metrics (impressions across the surfaces it appeared on, the notifications and follows it drove, and the deep-link taps and resulting opens or downloads) so you can compare an event's reach and conversion to the work it took. Watch the split between owned reach (your product-page card, followers) and earned reach (Today tab, category, search beyond your listing); a sharp rise in the earned portion signals the event won editorial featuring, which is the outcome worth chasing again. Tie the in-app side to your own analytics: did the deep-link taps convert into the action the event promised (entries into the competition, views of the premiere, sessions in the new season), and did that lift retention or revenue in the window? Use sanctioned data only: App Store Connect's own reporting and your in-app instrumentation, not scraped store pages. Over several events you will learn which badges, themes, and cadences earn featuring and conversion for your specific app, and you can retire the formats that draw impressions but no action. That feedback loop is what turns In-App Events from a checkbox into a repeatable discovery channel.
FAQ
Do In-App Events appear in App Store search?
Yes. An approved event can surface in search results, in addition to the Today tab, category and Games pages, editorial selections, and as a card on your own product page. That makes it a discovery channel that can reach users who have not found your app yet. The reach splits into owned placement (your product-page card and your followers) which you can count on once the event is live, and earned editorial placement on Today and in curated collections, which Apple grants to events that are genuine, distinctive, and timely.
What's the difference between the reference name and the event name?
The reference name is internal to App Store Connect for your own organization and is never shown to users. The user-facing event name and short description are what people see on the card, alongside the badge, the art, and the deep link. Write the reference name for your own clarity in the dashboard, and write the user-facing name to be specific and inviting: it is read by humans, unlike your hidden keyword field. Localize the user-facing name and description per storefront, since that text is what converts an impression into a tap in each market.
Who creates In-App Events and do they go live instantly?
You set them up in App Store Connect as the app owner, and each event goes through App Review before publishing. Plan lead time; they do not go live the moment you submit. Because review takes time and you usually want the card live at a precise moment (a holiday, a launch, a tournament start), submit well ahead and use the scheduled publish date rather than racing the approval clock. Events have a start and end date and a lifecycle of states, so you can prepare and schedule them in advance.
Are In-App Events a replacement for keyword optimization?
No. They are a separate, time-based discovery surface. Your app name, subtitle, and 100-byte keyword field still drive search ranking, in that weight order, and promotional text and description stay non-indexed. Events add featuring and timely visibility on top (including surfacing in search as a card tied to your listing) but you should not stuff keywords into the event name expecting the same ranking lift the keyword field gives. Treat indexed metadata as the durable foundation and events as the timed amplifier.
What gets an event rejected or featured?
Rejections come from events that are not genuinely timely (an evergreen feature or a bare discount dressed as an event), from misleading badges, from art that includes prices, rankings, or App Store UI, or from a card that over-promises what the deep link delivers. Featuring, the earned editorial reach, favors events that are novel or seasonal, visually distinctive, accurately badged, and tied to a moment users care about, like a competition with a clear start or a premiere of new content. You cannot buy the editorial placement, but an honest, well-crafted, localized card improves its odds.
How do I measure whether an event paid off?
Use App Store Connect and App Analytics for event-level metrics (impressions, notifications, follows, deep-link taps, and resulting opens or downloads) and tie those to your own in-app instrumentation to see if taps converted into the promised action and lifted retention or revenue. Watch the split between owned reach (your product-page card, followers) and earned reach (Today, category, search beyond your listing); a jump in earned reach signals editorial featuring. Rely on sanctioned data only: Connect's reporting and your own analytics, never scraped pages. Over several events you learn which formats earn featuring for your app.
appusula puts these checks in one self-hosted dashboard: keyword ranks, metadata validation, competitor tracking, and AI visibility.
Get started