In-App Events as a UA Channel: iOS and Android Compared

Most teams treat in-app events as a retention play — something you set up to re-engage dormant users or reward your most loyal cohort. That framing is too narrow. Both Apple's In-App Events and Google Play's Promotional Content are surfaced to users who have never installed your app, which makes them a genuine mobile user acquisition channel. A poorly understood one, but a real one.

This post breaks down how each platform's event system works, where they differ in reach and ranking mechanics, what the setup cost actually looks like, and when it's worth running one versus the other.

What Apple's In-App Events Actually Are

Apple introduced In-App Events in iOS 15. An event is a time-bounded card — up to 30 days — that appears on your App Store product page and, more importantly, across App Store editorial surfaces: Today tab, Games tab, Apps tab, and search results.

Each event card includes a short name (max 30 characters), a subtitle (max 45 characters), a long description (max 120 characters), and a hero image or video. Apple reviews every event before it goes live, and that review typically takes one to three business days, though it can stretch longer if assets are borderline on guidelines.

What makes this a UA channel: Event cards are discoverable by users who don't have your app installed. When a non-user taps the card, they land on your product page with an install prompt. Apple can also feature events in curated editorial content — that exposure is essentially free earned media if your event concept is interesting enough.

There are five event types Apple recognizes:

Challenge — time-limited user participation goals
Competition — leaderboard-style events with winners
Live Event — real-time limited-duration experiences
Major Update — significant new feature releases
New Season — new content cycles, common in games

Choosing the right type matters because Apple's algorithm uses it as a classification signal. Miscategorizing an update as a "Live Event" won't get you featured — and it may get your submission rejected.

What Google Play's Promotional Content Is

Google Play's equivalent launched under the "Promotional Content" label and has expanded gradually. The mechanics differ meaningfully from Apple's.

On Android, you can create promotional content cards that appear on your store listing, and Google can surface them in the Games or Apps dashboards for relevant users. The card formats include in-app events (similar to Apple), major updates, and offers.

Key structural difference: Google's promotional content has less consistent editorial placement than Apple's. The Today tab equivalent on Google Play is less prominent and less frequently merchandised. That said, Google's machine learning layer is more aggressive about surfacing promotional content in personalized feeds — so the distribution is more algorithmic and less editorial-dependent.

Google also allows promotional content to be targeted by country with more granular control than Apple currently offers, which matters for apps with region-specific seasonality or localized campaigns.

Side-by-Side Comparison

Dimension	Apple In-App Events	Google Promotional Content
Availability to non-installers	Yes — full UA capability	Yes — limited surfacing
Editorial placement	Today, Games, Apps tabs, Search	Games/Apps dashboards, personalized feeds
Review time	1–3 business days (can vary)	Typically faster, often same-day
Max event duration	30 days	14 days (events), longer for offers
Asset requirements	Hero image (2160×1080px) or video, icon	Feature graphic + optional video
Country targeting	App-level (limited granularity)	Per-event country targeting
Ranking signal	Indirect (engagement likely feeds algorithm)	Indirect — no confirmed direct ranking boost
Event types	5 structured types	Events, major updates, offers
Localization	Separate submission per locale	Built into the event creation flow

Where the Ranking Impact Is (and Isn't)

Neither Apple nor Google publicly confirms that running an event directly boosts your keyword rankings. Be skeptical of any agency that claims otherwise with certainty.

What is reasonable to believe, based on observable patterns:

On iOS: Events that drive a spike in installs, engagement, or downloads will likely improve your app's performance signals, which Apple's algorithm does factor into rankings. The event itself isn't a ranking lever — the installs it generates are. A well-trafficked In-App Event can therefore produce an indirect ranking benefit, but it's mediated by conversion volume, not event creation alone.

On Android: Similar logic applies. Google Play's ranking algorithm weighs engagement metrics. Promotional content that drives re-engagement or new installs can shift your standing, but the event card isn't a magic ranking button.

The honest framing: in-app events are a conversion surface, not an SEO shortcut. If your creative is weak, your event page won't convert, and you won't see ranking movement.

For a broader look at how this fits into a full 2026 acquisition strategy, see our post on 2026 Mobile User Acquisition Strategy.

Setup Cost and Resource Reality

Teams underestimate what a good event submission actually requires.

For Apple:

Hero creative (static or video) — budget for real design work. Apple rejects assets that look low-effort, and a rejection resets your timeline.
Copy in every locale you're targeting — Apple reviews localized versions separately.
Internal QA pass to confirm deeplink behavior works correctly on iOS 15+ devices.
Calendar buffer for the review window — don't submit two days before your event starts.

For Google:

Feature graphic and promotional copy — lighter asset lift than Apple in most cases.
Country/region targeting decisions — if you're running a localized event, you need translated copy ready.
Testing on the actual Play Store listing to confirm the card renders correctly.

In our engagements, teams that try to run events as a side task without dedicated creative bandwidth consistently produce underperforming cards. The event mechanic is free — the production quality is where budget needs to go.

Want help building an event strategy that actually converts? Our mobile app marketing team handles event planning, asset production, and submission management across both platforms.

When to Prioritize iOS Events vs. Android Events

This isn't an either/or decision for most teams, but when resources are constrained, here's how to think about it.

Prioritize Apple In-App Events when:

Your app skews toward iOS users (common in US fitness, finance, and premium consumer verticals)
You have a genuinely time-sensitive moment — a product launch, a seasonal hook, a partnership activation — where editorial placement could amplify your reach
Your design team can produce App Store-quality hero assets without a long lead time

Prioritize Google Promotional Content when:

Your user base is globally distributed or Android-dominant
You need country-level targeting precision for regional campaigns
You're running a promotional offer (discounts, trials) — Google's offer card type is more flexible here

Run both when:

You have the creative bandwidth and you're within 30 days of a meaningful product milestone
You're trying to generate a measurable install spike to support a paid acquisition campaign — organic event traffic compounds with paid

For context on how event strategy connects to broader app growth levers, our post on 5 App Marketing Strategies to Skyrocket User Retention in 2026 covers retention mechanics that in-app events feed directly into.

Common Mistakes That Kill Event Performance

Treating it like a press release. Event copy written in corporate announcement language ("We are thrilled to introduce…") converts poorly. Write for someone who has never heard of your app. What do they get? Why does it expire?

Missing the deeplink. An event card that drops users into the app home screen instead of the specific event experience is a wasted opportunity. This is a technical requirement, not a nice-to-have.

Submitting too late. Apple's review window means you cannot submit an event the day before launch. Build at least a five-business-day buffer. Google is faster, but don't push it.

Running an event with no paid amplification. Events are an organic surface, but they compound well with paid. Running a Meta or Apple Search Ads campaign pointing to your product page during an active event period means your event card is visible to everyone who lands on that page, including paid traffic.

Not measuring separately. If you can't isolate event-driven installs from baseline installs, you can't evaluate the channel. Use App Store Connect's event analytics on iOS and Play Console's reporting on Android. Tag deeplinks properly.

FAQ

Do Apple In-App Events directly improve App Store keyword rankings?

Not directly. Apple hasn't confirmed any direct ranking signal from event creation. What events can do is drive installs and engagement, both of which are factors Apple's algorithm uses. The ranking benefit, if any, is downstream of the traffic the event generates.

How long does Apple's In-App Event review take?

Apple typically reviews events within one to three business days, but complex submissions or borderline assets can take longer. Build a minimum five-business-day buffer before your event start date. Don't plan a launch-day event submission.

Can non-installers see In-App Events on both platforms?

Yes, on both iOS and Android. This is what makes them a legitimate mobile user acquisition tool rather than a pure retention feature. On iOS the editorial placement is more prominent; on Android the distribution leans more algorithmic.

Is there a cost to submit In-App Events or Promotional Content?

The submission itself is free on both platforms. The real cost is production — quality creative, localized copy, QA, and the internal time to manage submissions and track performance.

What's the maximum duration for each event type?

Apple allows up to 30 days per In-App Event. Google's promotional content events run up to 14 days; offer cards can run longer. Both platforms let you run multiple events sequentially, but Apple requires at least some gap between overlapping events on the same app.

Should I run an In-App Event if my app has few existing users?

Yes — but calibrate expectations. Events surface to non-installers, so thin engagement from your existing user base doesn't block the UA benefit. What matters is your product page conversion rate and the quality of the event creative. A new app with a compelling event concept can still generate meaningful installs.

If you're building out a serious mobile user acquisition program and want to incorporate in-app events as part of a broader paid + organic strategy, book a 30-minute call or explore what our mobile app marketing team builds for apps across iOS and Android.