OOmnistu

Blog / Mobile App Development

Mobile App Development

In-App Events and Promotional Content: Store Surfaces for Live Moments, Explained

How Apple In-App Events and Google Play promotional content put time-bound app moments onto store pages, search and editorial surfaces - and the eligibility bars and lead times that decide your start date.

OOmnistu
Reviewed 2026-11-19 · 4 min read

A finished feature nobody notices is a marketing problem, not an engineering one. Both stores now let you put time-bound moments - a tournament, a season premiere, a flash sale - directly onto store surfaces: Apple calls them In-App Events, Google Play calls them promotional content. The mechanics rhyme, the eligibility bars do not, and the lead times are longer than most teams plan for.

Apple In-App Events: an event card with store-wide reach

An In-App Event gets an event card and a richer event details page, which notes if an Apple In-App Purchase or subscription is required to participate. From either surface people can share the event, opt in to an App Store notification when it starts, and - if they do not have your app - download it directly from the card and land in the right place when they tap Open. Where it appears is the point: your product page lists all currently published events; in search results the event card shows alongside your app for users who already have it (screenshots show for those who do not), and users can search for events directly; and events can be picked for curated selections and personalized recommendations on the Today, Games and Apps tabs. Setup happens in App Store Connect: a reference name (visible only there), event metadata, an event badge and regional availability, then submission for review. Apple also runs an editorial door - you can share an In-App Event with its worldwide team of editors for promotional consideration, the same channel that highlights significant updates and cultural or seasonal moments.

Google Play promotional content: same idea, gated eligibility

Play's promotional content covers in-app and in-game events and featured products, created under Grow users > Store presence > Promotional content. The first difference from Apple is the gate: promotional content is available for all games, but apps need to meet the eligibility criteria for Premium growth tools - and access to featuring, deep links and audience targeting rides on that same eligibility. The second difference is the clock: an event can be created any time but submitted no earlier than 60 days before its start date, approval can take up to four days, and Google recommends building that in. The third is the preview mechanic: you can show your event on Google Play before it starts, up to 14 days ahead, so users can choose to be notified when it begins - preview is selected by default, so change it if a surprise launch is the plan. Play's separate content quality guidelines still apply to everything you submit.

The operational rhythm both stores impose

Neither surface is a same-day lever. Apple's events go through App Store review; Play's take up to four days and cannot even be submitted inside the 60-day window's last moments. Work backwards: lock the in-app experience first (deep links or event routing ready, purchase requirements accurate), then the store metadata, then submit with approval slack, then market externally - Apple's own guidance is to promote events via email, ads and social with a link to the event details page. The common failure mode is treating the store event as an afterthought on launch day: by then the review window has already decided your start date for you.

A short checklist

The honest summary

Apple gives every developer the surface and asks for a good event; Play gives the surface to every game and to apps that clear an eligibility bar. Both make the store itself a marketing channel for what's happening inside your app this week - and both punish teams that start the paperwork on launch day.

Sources

Prepared with AI assistance and reviewed before publication. Eligibility rules, timing windows and review behavior are drawn from the source pages above, checked on 19 November 2026.