iOS In-App Events: What They Are, When They Work, and How to Write One
An iOS In-App Event is a timely, time-boxed event happening inside your app — a competition, a premiere, a major update, a seasonal challenge — that Apple gives its own discoverable card on the App Store. The card carries an image or video, an event name of up to 30 characters, and a short description of up to 50, and it can appear on your product page, in search results, and in editorially curated selections on the Today, Games and Apps tabs.
That makes In-App Events the only ASO surface where you can publish new, indexable, promotable content on your own schedule without shipping an app version. Your title, subtitle and keyword field are locked until your next release. An event is not. This article covers what Apple actually permits — the seven event badges with Apple's own definitions, the character limits, the timing rules, and the review requirement — and then how to write the three fields inside limits that are much tighter than they look.
Every limit below is quoted from Apple's App Store Connect documentation rather than from ASO convention.
The Short Answer
- Three visible fields: event name 30 characters, short description 50, long description 120. Plus an internal reference name of up to 64 characters that users never see.
- Seven badges. Live Event, Premiere, Challenge, Competition, New Season, Major Update, Special Event. You must pick one and the event must genuinely fit it.
- Timing is bounded. An event runs at least 15 minutes and at most 31 days, and can be published up to 14 days before it starts.
- Volume is capped. Up to 10 events published on the App Store at a time, up to 15 approved in App Store Connect, and up to 10 with overlapping start times in approved or draft status.
- Events go through App Review. "In-app events must be approved before they are visible to users."
- The search behaviour is the part people miss. For users who have already downloaded your app, the event card appears in search results instead of your screenshots.
What Apple Says an In-App Event Is
Apple's definition, from App Store Connect Help:
"In-App Events, such as game competitions, movie premieres, and live-streamed experiences, are timely events within apps and games. Customers can discover these events on the App Store and Apple Games for iOS and iPadOS, providing a new way to showcase and expand their reach."
And on how they render:
"On iOS 15 and iPadOS 15 and later, In-App Events appear across the App Store as event cards that include images or video, the event name, and a short description."
The word doing the work is timely. An In-App Event is not a feature description or a permanent marketing surface — it is something that starts and ends. App Review enforces that: Guideline 2.3.13 requires that "all event metadata must be accurate and pertain to the event itself, rather than the app more generally" and that "events must happen at the times and dates you select in App Store Connect."
Where the Cards Actually Appear
Apple names three surfaces:
"On your App Store and Apple Games product page, which displays all of your currently published events."
"In App Store and Apple Games search results. When users search for an app, the event card appears along with your app for users who have downloaded your app, while screenshots show for those who haven't downloaded your app. Users can also search for In-App Events directly. When users search for an event, the event card appears along with your app."
"In editorially curated selections and personalized recommendations on the Today, Games, and Apps tabs in the App Store and Apple Games."
The middle one is the most consequential and the least discussed. In search results, Apple shows the event card instead of your screenshots to people who already have your app, and your screenshots to people who do not. That splits the surface cleanly:
| Audience | What they see in search | What the event is for |
|---|---|---|
| Has your app installed | Event card | Re-engagement — bringing a lapsed user back |
| Does not have your app | Screenshots | Acquisition — unchanged by the event |
So an In-App Event is primarily a re-engagement and retention instrument in search, and an acquisition instrument only through the third surface — editorial curation — which you do not control. Anyone selling In-App Events as a download-acquisition tactic is describing the Today-tab feature slot, which is discretionary and rare.
The re-engagement framing is not a downgrade. Reactivating a user who already installed you is cheaper than acquiring a new one, and it feeds two of the behavioural inputs Apple names for search ranking — downloads and ratings — described in what is App Store Optimization.
The Seven Badges, in Apple's Own Words
You must choose a badge, and it displays above the title on both the event card and the event details page. Apple's badge definitions:
| Badge | Apple's definition |
|---|---|
| Live Event | "Activities that occur in real-time that all users can experience simultaneously — for example, a sports match or live-streamed concert. These events should provide users with new content, features, or goods." |
| Premiere | "First-time availability of content or media — for example, newly released movies or audio." |
| Challenge | "Activities encouraging the user to achieve a goal before the event ends — for example, a fitness challenge in a workout app or beating a certain number of levels in a game." |
| Competition | "Activities in which users compete against one another for the highest ranking or to win rewards — for example, a tournament where players battle to win the most matches." |
| New Season | "Introducing new content, storylines, or media libraries — for example, a new season of a television show or a new battle pass in a game." |
| Major Update | "Introducing significant new features, content, or experiences – for example, the launch of new game modes or levels. These events go beyond minor enhancements like UI adjustments or bug fixes." |
| Special Event | "Limited-time events that aren't captured by another event badge, possibly spanning multiple activities or experiences — for example, an event featuring a collaboration." |
Two notes for non-game apps, which is most indie iOS developers. Challenge and Major Update are the two badges that fit a typical utility, health or productivity app without contortion — a 30-day streak challenge, or a genuinely significant feature launch. And Apple's qualifier on Major Update is explicit: these "go beyond minor enhancements like UI adjustments or bug fixes." A bug-fix release dressed as a Major Update is a rejection, not a clever ASO trick.
Special Event is the catch-all, but read Apple's condition: it "should provide users with new content, features, or goods." It is not a slot for a discount announcement with nothing behind it.
The Rules That Constrain Your Plan
| Rule | Apple's wording |
|---|---|
| Maximum duration | "The end date can be a maximum of 31 days from the start date." |
| Minimum duration | "Events must be at least 15 minutes long." |
| Promotion window | "The publish date is when your event will become discoverable ... and can be a maximum of 14 days in advance of the start date." |
| Published at once | "You can publish up to 10 In-App Events on the App Store and Apple Games at a time." |
| Approved at once | "You can have up to 15 approved In-App Events per app in App Store Connect at a time." |
| Overlapping | "You can have up to 10 events with overlapping start dates and times, either approved or in draft status, at the same time." |
| Review | "In-app events must be approved before they are visible to users." |
Source: Apple, Offer In-App Events.
The operationally important line is the last one. Events go through App Review, so the publish date you choose is a target, not a guarantee — build slack into any event pegged to an external date such as a holiday or a launch. The 14-day promotion window is the outer bound on how early you can start building anticipation, and it is generous enough that submitting well ahead of the start costs you nothing.
Guideline 2.3.13 adds one more requirement that is easy to overlook in the copywriting rush: "your event deep link must direct users to the proper destination within your app." An event card that opens your home screen instead of the event is a rejection.
The Three Fields You Have to Write
Apple's field definitions and limits, quoted from Offer In-App Events:
| Field | Limit | Apple's wording | Where it shows |
|---|---|---|---|
| Reference name | 64 characters | "This name identifies your event in App Store Connect and is not visible on the App Store" | Internal only |
| Event name | 30 characters | "Enter an event name to appear on the App Store and Apple Games. It can be up to 30 characters." | Card and details page |
| Short description | 50 characters | "Enter a short description to appear on your event card in places like the Today tab and Search" | Card |
| Long description | 120 characters | "Enter a long description that will appear on your event details page when users tap your event card" | Details page only |
Each of the three visible fields is localisable — Apple's instruction is to "add localizations for your event by choosing the primary language to display the language pop-up menu" — which means the writing problem multiplies by every locale you support.
Note how small the long description is. One hundred and twenty characters is roughly one sentence. The instinct to draft a paragraph and trim is a trap: at these limits, trimming produces mangled copy rather than tight copy. Write to the limit from the first draft.
How to Write Each Field
Event name — 30 characters
The name is the headline and it sits under a badge that already states the category. Do not spend characters repeating the badge.
- Bad:
Special Event: Summer Sale— the badge already says Special Event. - Bad:
Our Biggest Summer Challenge Yet— 32 characters, and "biggest" is an unverifiable claim. - Good:
30-Day Summer Streak— 20 characters, concrete, and clearly time-boxed.
Name the thing that happens, with the specific number or period in it if there is one. Numerals are cheaper than words and read faster.
Short description — 50 characters
This is the line that appears with the card in search and on the Today tab. It has one job: give a reason to tap, right now.
- Weak:
Join our summer event and have fun— no stake, no deadline. - Better:
Log 30 workouts by Aug 31. Earn the badge.— 42 characters, one action, one date, one reward.
Fifty characters is about eight words. A verb, an object, and a deadline is usually the whole budget.
Long description — 120 characters
The long description appears only after someone has already tapped, so its job is not to sell the event again — it is to remove the last ambiguity about what participating involves.
- Redundant:
Our summer challenge is here! Join thousands of users in our biggest summer event.— repeats the card and says nothing new. - Useful:
Complete 30 workouts of any length between Aug 1–31. Progress syncs automatically. Badge unlocks at workout 30.— 111 characters, answers what counts, how tracking works, and what you get.
Guideline 2.3.13 requires that metadata "pertain to the event itself, rather than the app more generally." A long description that describes your app rather than the event is both a rejection risk and a wasted 120 characters.
When In-App Events Are Worth It
Worth it when:
- You have a genuine, dated thing happening — a challenge, a season, a real feature launch, a live session.
- You have an installed base large enough that re-engagement matters, since that is where the search surface actually lands.
- You can run them repeatedly. The cap of 10 published at a time implies a cadence, not a one-off.
- Your event has a deep link to a real destination in the app.
Not worth it when:
- Nothing is actually happening and you are manufacturing an event to get a card. Guideline 2.3.13 is specific, and review is the enforcement.
- You have almost no installed base, and therefore almost nobody in the audience that sees event cards in search.
- The "event" is a bug-fix release. Apple excludes minor enhancements from Major Update by name.
The honest framing: In-App Events are a retention and re-engagement lever with an outside chance of editorial pickup. Treated that way they are one of the few ASO surfaces you can move between releases. Treated as a growth hack they produce rejections.
Generate the Copy Inside the Limits
The hardest part of an In-App Event is not the concept. It is producing three fields at 30, 50 and 120 characters, in every locale you ship, without the result reading like something that has been cut down twice.
App Store Operator is a free, open-source MCP server for Claude, and prepare_iae is the tool built for exactly this. It returns three complete variations per run, with all three App Store Connect character limits enforced rather than checked afterwards, across 14 locales — en-us, en-gb, de, fr, es, es-mx, it, ja, ko, pt-br, nl, zh-hans, zh-hant and tr. Getting three finished options lets you pick an angle instead of editing one draft down to fit.
Register the server with one command:
claude mcp add --transport stdio app-store-operator -- npx -y app-store-operator@latest
Then describe the event in plain language:
Prepare an In-App Event for my fitness app: a 30-day summer streak challenge running Aug 1–31, where users log any workout each day. Give me options in English and German.
prepare_iae needs no account of any kind — it makes no external API calls, so there is nothing to sign in to. That is also true of search_app_store. The two analytics tools, research_rivals and get_app_details, are the ones that open a browser window once for a one-time sign-in to a free SensorTower account. Full detail on which tool needs what is on the pricing page, and the use cases page shows the prompts for all four.
The character limits prepare_iae enforces — 30, 50 and 120 — match Apple's documented limits exactly, which is worth confirming rather than assuming, because tool-enforced limits and platform limits do drift apart over time.
Frequently Asked Questions
What is an iOS In-App Event?
An In-App Event is a timely, time-boxed event inside your app — such as a competition, premiere, challenge or major update — that gets its own discoverable card on the App Store. Apple describes them as "timely events within apps and games" that customers can discover on the App Store for iOS and iPadOS. Each event carries a badge, an image or video, an event name, and a short description.
What are the In-App Event character limits?
The event name can be up to 30 characters, the short description up to 50, and the long description up to 120. There is also an internal reference name of up to 64 characters that identifies the event in App Store Connect and is never visible on the App Store. All three visible fields can be localised.
What are the In-App Event types?
Apple provides seven badges: Live Event, Premiere, Challenge, Competition, New Season, Major Update and Special Event. You must choose the one that genuinely fits — App Review Guideline 2.3.13 requires the event to fall within an event type provided in App Store Connect and requires all event metadata to be accurate and specific to the event rather than the app generally.
How long can an In-App Event run?
At least 15 minutes and at most 31 days from the start date. You can publish an event up to 14 days before it starts, which is the window in which it becomes discoverable on the App Store ahead of the event itself.
How many In-App Events can I have at once?
Up to 10 published on the App Store at a time, up to 15 approved per app in App Store Connect, and up to 10 events with overlapping start dates and times in either approved or draft status.
Do In-App Events go through App Review?
Yes. Apple states that in-app events must be approved before they are visible to users. Build review time into any event pegged to an external date, and make sure your event deep link opens the correct destination inside your app — Guideline 2.3.13 requires it.
Do In-App Events bring in new users?
Mostly not directly. In search results, Apple shows the event card to people who have already downloaded your app and shows screenshots to people who have not, so the search surface is a re-engagement channel rather than an acquisition one. New-user exposure comes through editorial curation on the Today, Games and Apps tabs, which is discretionary and not something you can plan around.
Can I change In-App Event copy without shipping an app update?
Events are configured in App Store Connect rather than in your binary, so you can create and schedule them between releases — unlike your app name, subtitle and keyword field, which are version-locked. Events still require App Review approval before they become visible.
Run Them as a Cadence, Not a Stunt
The cap of 10 published events at a time tells you how Apple expects this surface to be used: repeatedly, by apps that genuinely have things happening. One event is an experiment. A quarterly rhythm of real, dated events is a re-engagement channel that costs no release cycle.
The three fields are the constraint, and they are tighter than they look. Get the copy generated to spec in one step:
claude mcp add --transport stdio app-store-operator -- npx -y app-store-operator@latest
For the metadata that does ship with a version — and is therefore worth even more care — see App Store title, subtitle, and keyword field. For the wider picture of what actually moves App Store rankings, start with what is App Store Optimization.
Run your first competitive research in 60 seconds.
App Store Operator connects Claude to App Store and SensorTower data — no browser, no API keys, no manual copy-paste.
View setup guide →