App Store In-App Events: a practical guide for subscription apps

In-App Events are free App Store cards that surface your app in search results, editorial tabs, and personalized recommendations — no ad spend required. This guide covers all seven event types, the App Store Connect setup workflow, and how to pair events with promotional offers to drive subscription conversions and re-engage lapsed users.

Introduced at WWDC 2021 and available from iOS 15 and iPadOS 15 onwards, App Store In-App Events are time-limited event cards that Apple displays directly on your app's product page, in search results, and across editorial tabs like Today and Games. Unlike Apple Search Ads, they require no media spend — just a submission through App Store Connect and approval from App Review.

Each event is built around a card: a dedicated image or video asset (2160×1080 pixels for landscape), a localizable event name, a short description, a badge indicating the event type, and a start/end date window of up to 31 days. Tapping the card takes users to an event detail page, which can deep-link directly into your app at any screen you choose.

For subscription app developers already investing in pricing strategy and paywall design, In-App Events are the most underused free distribution lever Apple currently offers.

The Seven Event Types — and Which Work for Subscription Apps

Apple currently supports seven distinct event types. The type you choose affects the badge displayed on your event card and, more importantly, which App Store placements Apple's algorithm will consider for your event:

For most indie subscription apps — productivity tools, health apps, learning platforms — the two most immediately actionable types are Special Events and Major Updates. Special Events can surface to users who have never installed your app, which makes them the higher-leverage option for cold acquisition. Major Updates are better suited to re-engagement campaigns targeting users who already have (or had) your app.

Why Subscription Apps Are Under-Using In-App Events

In-App Events occupy an unusual category: they are not paid ads, but they are also not purely organic metadata like keywords or screenshots. They require creative assets, localizable copy, and an App Review approval cycle that typically runs 24–48 hours. That overhead is enough to push them down the priority list for lean development teams.

The result, as ASO practitioners including those at Phiture have noted in their ongoing Mobile Growth Stack research, is that In-App Events remain underused relative to their available distribution surface. Apple surfaces approved events in multiple placements:

• Your app's product page — visible to both installed and non-installed users browsing your listing
• App Store search results — as a secondary card beneath your standard listing for relevant queries
• Today, Games, and Apps editorial tabs — for events Apple's editorial team selects, which requires no additional submission
• Personalized recommendations — surfaced to users Apple's algorithm deems likely to engage, based on usage patterns

The search result placement deserves particular attention. A “Special Event” card appearing beneath your standard listing effectively doubles your visual footprint on a search results page at no incremental cost. For keywords where you already rank organically, an active In-App Event can increase the real estate your app occupies and provide an additional, time-sensitive reason for a user to tap through.

Setting Up an In-App Event: The App Store Connect Workflow

The entire workflow lives inside App Store Connect. Here is the sequence from start to submission:

1. Open the In-App Events section. In App Store Connect, navigate to your app, select the iOS platform, and find “In-App Events” in the sidebar. This section appears once your app has at least one approved version in the store.
2. Create a new event and choose a type. The event type determines the badge on your card and influences which placements Apple considers. Choose the type that most honestly describes your event — misclassifying a promotional discount as a “Challenge” risks rejection from App Review.
3. Write the event metadata. You have three copy fields: event name (up to 30 characters), a short description (up to 50 characters), and a long description (up to 120 characters). All three are localizable. Write them in your primary language first, then localize.
4. Upload your creative assets. You need a landscape image at 2160×1080 pixels and a portrait thumbnail at 1080×1080 pixels. Both are required. Apple is strict about dimensions — off-spec files will be rejected without detailed explanation. Video is optional but supported at the same landscape resolution.
5. Set the date window. Choose your event start and end dates. You can schedule events to start up to 14 days after submission. With App Review averaging 24–48 hours, build a buffer of at least three days into your launch calendar.
6. Configure a deep link. Enter the URL scheme or Universal Link that should open when a user taps your event card. For subscription apps, this is typically your paywall, a specific content screen, or a promotional offer page. Make sure the destination handles users who are already subscribed gracefully — sending an active subscriber back to your purchase screen creates a poor experience.
7. Set event priority. If you plan to run multiple events simultaneously, priority determines which one appears most prominently on your product page. Apple recommends keeping concurrent events to three or fewer.
8. Submit for review. Events go through App Review independently of app version submissions. You do not need to ship a new build to run an event, which significantly reduces operational overhead compared to release-gated campaigns.

That independence from app releases is the most operationally underappreciated aspect of In-App Events. Once your App Store Connect workflow is familiar, an experienced team member can draft copy, prepare assets, and submit an event in a single morning. The bottleneck is asset production, not engineering cycles.

Pairing In-App Events with Subscription Offers

In-App Events are a discovery and re-engagement mechanism, not a pricing mechanism — they do not change your subscription price or offer eligibility rules. Their power comes from pairing them with the subscription offer types Apple already supports.

Three patterns work particularly well for subscription apps:

Pattern 1: Special Event + Introductory Offer. Set up a time-limited introductory offer (discounted first billing period) through App Store Connect, then create a “Special Event” timed to match the offer window. Deep-link the event card to the screen in your app that presents the introductory pricing. This pattern targets cold users who have never subscribed — the event drives discovery, the introductory offer closes conversion.

Pattern 2: Special Event + Promotional Offer (win-back). For lapsed subscribers, introductory offers are not available — Apple restricts them to first-time subscribers. Pair a “Special Event” with an iOS promotional offer instead. Promotional offers can be configured to target only users who have previously subscribed, making them the correct offer type for a re-engagement campaign. The event provides App Store surface area; the promotional offer provides the pricing incentive.

Pattern 3: Major Update + No Offer. Not every event needs a discount. If your latest release substantially improves the subscriber experience — a new feature set, redesigned interface, meaningfully expanded content — a “Major Update” event communicates that the product has changed. For users who churned because of gaps in the previous version, product-led re-engagement can be more durable than price-led re-engagement. This pairs well with a review of your territory and pricing configuration to ensure the value proposition aligns with the updated product.

What to Measure After Running an In-App Event

App Store Connect surfaces basic event metrics in App Analytics: impressions (how many times your event card was displayed), taps (how many users tapped through to the event detail page), and downloads or re-downloads attributed to the event. For subscription apps, the most meaningful downstream metric is subscription conversions in the period following an event tap, which requires correlating App Store Analytics data with your subscription backend or a tool like RevenueCat.

A few measurement notes worth keeping in mind:

• App Store Analytics attribution for In-App Events uses a 30-day look-back window by default. Set your comparison window accordingly when evaluating conversion rates.
• Tap-through rate (taps ÷ impressions) varies significantly by event type and asset quality. A compelling image with a clear value proposition typically outperforms a generic branded graphic — treat your event creative as a marketing asset and test it accordingly.
• Re-download rate is often a more useful subscription-specific signal than gross download count, particularly for “Major Update” or win-back campaigns where the target audience is lapsed users rather than new ones.

ASO practitioners who have written about In-App Events — including researchers at Phiture and AppFollow — have suggested that the feature performs best when used on a consistent cadence (one or two events per month) rather than in infrequent bursts. Apple's placement algorithm appears to reward apps that engage with the feature regularly, though Apple has not published explicit documentation confirming that mechanism.

One practical calendar note: App Review for In-App Events is independent of, but draws from, the same review queue as app submissions. During high-volume periods — immediately before major Apple platform releases or the end-of-year holiday window — review times can extend beyond the usual 24–48 hours. If your event is tied to a time-sensitive promotion, submit at least five business days in advance and monitor the review status in App Store Connect.

Sources and Further Reading

• Apple Developer: In-App Events — official overview, event type definitions, and placement guide
• App Store Connect Help: Overview of In-App Events — step-by-step setup documentation
• Phiture Mobile Growth Stack — ongoing ASO research including In-App Events analysis and practitioner findings
• RevenueCat Blog — subscription analytics, win-back strategy research, and state-of-subscriptions benchmark reports
• AppFollow Blog — App Store metadata, ASO strategy, and event placement best practices