In-App Events: Free App Store Visibility Most Apps Skip

Most app teams treat the App Store listing as something you set once and tweak quarterly. Meanwhile, one of the few free ways to get extra visual space in App Store search results sits unused in App Store Connect: In-App Events. If your app has anything time-bound happening inside it — a challenge, a new content drop, a seasonal feature, a live session — you can turn that into an event card that shows up where people are already browsing.

This guide covers what In-App Events actually do for ASO, which apps benefit most, how to write event metadata that converts, and a simple cadence you can run without a dedicated LiveOps team.

What In-App Events are (and where they show up)

In-App Events are timed happenings inside your app that you submit through App Store Connect, each with its own name, short and long description, artwork or video, badge type and deep link. Once approved, an event can appear in several places:

• Your product page, as a card above the fold that existing visitors see before your screenshots.
• Search results, where an event card can display alongside or instead of your standard result for people who already have the app, and as additional discovery surface for those who don't.
• Personalized recommendations and editorial tabs (Today, Games, Apps), if Apple's editors or algorithms choose to feature it.

Two details matter most for marketers. First, event metadata is indexed for search, so a well-named event can help you appear for queries your main metadata doesn't cover. Second, events have their own deep link, so a tap can drop an existing user straight into the relevant screen instead of your home tab. That makes them a re-engagement tool as much as an acquisition one. Apple's full requirements and character limits live on developer.apple.com; check them before you write, because they're tight.

Why most apps skip them — and why that's an opportunity

The usual objection is "we're not a game, we don't have events." That's too narrow. Apple's badge types include things like Challenge, Major Update, New Season, Premiere, Live Event and Special Event. A meditation app can run a 7-day calm challenge. A budgeting app can run a "January reset" with a guided setup flow. A language app can premiere a new course. A productivity app can frame a big feature release as a Major Update event.

Because many non-game categories rarely use events, the ones that do stand out visually in search. You're competing for attention with plain icon-and-screenshot results, and a large, colorful event card is simply harder to scroll past.

Picking events worth submitting

Not every feature deserves an event. A good candidate passes three tests:

1. It's genuinely time-bound. Apple reviews events and rejects ones that are just evergreen features dressed up. "New dark mode" is not an event; "30-Day Focus Challenge starting Monday" is.
2. It has a clear destination. The deep link should open a screen built for the event, not a generic dashboard. If a new user taps through after installing, they should land somewhere that makes sense.
3. It maps to a search intent. Think about what someone might type that week. Seasonal moments (new year, back to school, exam season, holiday travel, summer fitness) are the obvious ones, because demand for related keywords spikes on its own.

A practical rule: brainstorm ten possible events for the next quarter, then keep only the three or four that pass all three tests. Fewer strong events beat a calendar full of filler.

Writing event metadata that converts

Event copy is short, so every word has to work. Treat it like ad copy, not a changelog.

Event name

Lead with the outcome or the hook, and include one keyword you want to rank for that isn't already doing heavy lifting in your title or subtitle. "21-Day Sleep Reset" beats "Sleep Feature Update." Avoid your app name here — it's already on the card.

Short description

This is the line most people will actually read. State who it's for and what they get, in plain language: "Fall asleep faster with one 10-minute routine a night." Concrete beats clever.

Long description

Use this to remove friction: what happens, how long it takes, whether it's free, and what someone needs to do to join. If the event is part of a subscription, say so honestly — surprises here turn into bad reviews.

Artwork and video

The card image is the real hook. Show the event, not your logo. A person mid-workout, a progress streak, a new map or level — something that communicates "this is happening now." Keep text on the image minimal; it gets small fast on a phone.

A lightweight event cadence

You don't need a LiveOps department. Here's a worked example of a four-week rhythm a two-person team could run:

• Week 1: Pick the event, confirm the in-app destination exists, and draft three variations of name and short description.
• Week 2: Produce the card artwork, submit for review, and schedule the event to start promoting before it goes live, so it's visible during the run-up.
• Week 3–4: Event runs. Push a notification and an email to existing users that point to the same deep link, and post a short-form video teasing it so all channels tell one story.
• After: Review results, log what worked, and plan the next event.

Running roughly one strong event a month keeps your listing looking alive without burning out the team.

Measuring whether events pay off

App Store Connect reports event-specific metrics such as impressions, event page views, opens and downloads attributed to the event. Look at three things:

• Incremental downloads: compare first-time downloads during the event window to the same window the previous month. If you see a lift of, say, 8–12% in a quiet period, that's meaningful free volume.
• Reactivations: how many lapsed users opened the app via the event card. For many apps this is the bigger win.
• Search coverage: did you start appearing for the keyword you placed in the event name? Track it in whatever keyword tool you already use.

If an event underperforms, the culprit is usually the card artwork or a vague name. Change one variable for the next event so you actually learn something.

Don't forget Google Play

Google Play has its own equivalent, Promotional content (sometimes called LiveOps), managed in the Play Console. The principles are the same: time-bound, deep-linked, outcome-led copy and strong visuals. If you write your App Store event well, adapting it for Play is mostly a formatting job — so plan both at once.

Make events part of your campaign, not an afterthought

The teams that get the most from In-App Events treat each one as a mini campaign: one idea, expressed consistently across the store card, push notifications, email and short-form video. That consistency is what turns a free listing slot into installs and reactivations.

If you want help drafting event names, descriptions, matching push copy and a video script around the same hook, you can generate a campaign with Skilmark in a few minutes and adapt it for your next event.