In-App Events: Your Most Under-Used ASO Lever in 2026
Apple's In-App Events surface in App Store search results and editorial tabs — but most indie developers never post one. Here's how to use them as a free discoverability lever in 2026, including what to prep for iOS 26's redesigned store.
Apple introduced In-App Events in iOS 15, and the App Store has been surfacing them more aggressively ever since. As of mid-2026, events appear on the Today tab, the Games tab, in search results, and on an app's own product page. Yet the majority of indie apps on the store have never published a single event. If that describes you, you're leaving one of the few remaining free discoverability tools on the table.
What In-App Events Actually Do for ASO
An In-App Event is a time-limited piece of content — a challenge, competition, premiere, sale, major update, or live event — published through App Store Connect. Apple gives each event its own detail page in the store, complete with a title, short description, long description, and a wide event card image.
From an ASO perspective, three things matter:
- They appear in search results independently. When a user searches for a keyword that matches your event's title or description, the event card can surface in results even if your app doesn't rank highly for that term organically. This is one of the few ways a low-ranked app can gain search real estate without paid spend.
- They signal editorial attention. Apple's App Store editorial team reviews published events. Well-crafted events for games, health apps, and productivity tools have historically triggered featuring on the Today and Games tabs — free banner placements that would otherwise cost significant Search Ads budget to replicate.
- They index fresh metadata. The event title and description fields are indexed for keyword search. Developers who treat event descriptions as additional keyword surfaces get incremental indexing they wouldn't get from the 100-character subtitle alone.
How to Publish Events That Actually Get Featured
Apple's review guidelines for IAEs are stricter than for standard app updates. Events must map to one of Apple's seven event types (Challenge, Competition, Live Event, Major Update, New Season, Premiere, Sale), and the event must accurately describe what's happening inside the app during that window. Evergreen "events" — always-on sales branded as a 31-day event — get rejected.
The card image is your hook
Apple displays the event card at roughly the same visual weight as a Today story. The card uses a wide aspect ratio (check App Store Connect for the current pixel spec — Apple has adjusted requirements across iOS versions). The image must communicate the event at a glance without relying on title text, because the card is often displayed cropped. Think of it as a mini-billboard, not a screenshot.
Time events to reinforce release cadence
A Major Update event tied to a version launch gives you a legitimate submission window every time you ship. If you release monthly, that's 12 events a year. Each one creates a fresh editorial review opportunity and a new set of indexed metadata. Pair each event with an external signal — a blog post or community announcement — to reinforce App Store activity from multiple directions.
Localize the event metadata
Most developers publish event copy in English only. Events support per-locale titles, short descriptions, and images, but almost nobody fills them in. An event published in Japanese for a fitness app with a Japanese user base is dramatically more likely to surface in Japanese search results — and potentially earn a featuring slot on Japan's App Store editorial tab, which is curated by a separate team from the US. Given the difficulty of creating quality localized copy quickly, this is one place where a streamlined localization workflow pays for itself fast.
IAEs vs. Apple Search Ads: A Quick Comparison
| Signal | In-App Event | Apple Search Ads |
|---|---|---|
| Cost | Free | CPI-based, scales with budget |
| Search placement | Organic, keyword-dependent | Paid, bid-based |
| Editorial featuring potential | Yes | No |
| Setup time per launch | A few hours | Ongoing campaign management |
| Localization effort | Copywriting + images per locale | Creative sets per territory |
What to Watch With iOS 26
With iOS 26's Liquid Glass redesign rolling out in beta, it's not yet clear exactly how event cards will render in the updated App Store UI. Apple has confirmed the store is being redesigned, and early beta observations suggest the Today tab is getting a visual refresh that could increase the surface area available to event cards. Reports suggest the redesigned store may give in-app events more prominent placement — though this is still in beta and subject to change before the autumn public release.
Developers planning a major update launch to coincide with iOS 26 general availability should factor in IAE timing. Apple typically takes one to three business days to review events, and events can be submitted up to 14 days before their start date. Submitting the same week as a major iOS launch, when Apple's review queues are heavy, risks missing the window. Build in buffer.
The Bottom Line
For indie developers and small teams, In-App Events have an outsized ROI relative to effort. They don't replace paid acquisition, but they create organic discoverability touchpoints that compound over time — each event is indexed, each well-crafted event is reviewed by Apple's editorial team, and each localized event opens a potential featuring slot in another country's store. See the territories overview for a sense of how much store-by-store editorial independence matters across Apple's 175 storefronts.
If you haven't published an event in the last 90 days, your next release is the right time to start.
Sources and further reading
- Apple Developer — In-App Events overview
- Apple Developer — App Store Connect documentation
- RevenueCat Blog — mobile subscription and growth analysis
- Appfigures — App Store analytics and event tracking
Share this