App Store in-app events vs Google Play promotional content
Both stores let you show a timely event on your store page and beyond it. Apple calls them in-app events. Google calls them promotional content, and called them LiveOps until November 2022. They look alike, but the rules differ in ways that matter when you plan one event for both stores: who can use them, how long they run, what the text may say and what the images may show.
The basics
| App Store in-app events | Google Play promotional content | |
|---|---|---|
| Who can use it | Any iPhone or iPad app. Events show on iOS 15 and iPadOS 15 or later. | All games. Apps only if they meet Google's Premium growth tools thresholds. |
| Types | 7 badges: Challenge, Competition, Live Event, Major Update, New Season, Premiere, Special Event | Offers, time-limited events and major updates, each with subtypes. Pre-registration announcements fall under major updates. |
| Discounts and sales | Not an event on their own. Apple says price promotions with nothing new aren't good candidates. | A full type: discounts, extra value, free rewards and subscription trials. |
| Longest run | 31 days. At least 15 minutes. | Four weeks. Major updates run a fixed 28 days, pre-registration announcements one week. |
| Shown before it starts | Up to 14 days | Up to 14 days as a preview. Offers can't be previewed. |
| When to submit | Any time before the start, allowing for App Review | No earlier than 60 days before the start. Google recommends at least 4 days before, and requires at least 14 days if you request featuring. |
| Review | App Review, with an app version or on its own | Approval can take up to 4 days. The content quality review usually takes under 24 hours. |
| Changes after submitting | Approved events allow date, priority and availability changes. Published events, only dates. | No edits. You edit and resubmit, which cancels the original, and the new version goes live 24 hours or more later. |
| How many | 10 published at once, 15 approved, 50 drafts | No limit on events, but no identical or very similar events live at the same time. Featuring requests are limited per quarter. |
| Audience | A purpose: all users, new, active or lapsed. Every published event stays discoverable by everyone. | Everyone or people who never installed. Lapsed, churned, buyer and custom audiences for eligible titles. |
| Deep link | Part of the form. Apple recommends universal links. | Optional, for eligible titles |
| Featuring | Featuring Nominations in App Store Connect, open to every developer | Featuring requests for eligible titles. For broad audiences, 4 a quarter for games and up to 6 for apps. For specific audiences, 2. |
| Analytics | Impressions, page views, app opens, reminders, notification taps, downloads | Unique viewers, unique converters, and featuring uplift |
One note on duration: Google's create page says four weeks, while its FAQ on the same page says time-limited events must end within 30 days of the start. Plan for four weeks to be safe.
The text
| Field | App Store | Google Play |
|---|---|---|
| Internal name | Reference name, up to 64 characters | Event name, shown only in Play Console |
| Public title | Event name, up to 30 characters, title case | No separate title. The tagline does the job. |
| Short text | Short description, up to 50 characters | Tagline, up to 80 characters. For offers, the value must come in the first 40. Spotlight needs 48 or fewer. |
| Long text | Long description, up to 120 characters | Description, up to 500 characters. Google recommends at least 100. |
| Prices | Not allowed. Apple says specific prices lead to rejection. | Expected for offers. The tagline must state the value, such as "25% off TVs". A sale across many categories can name the branded sale instead. |
The price rule is the clearest example of why one text can't serve both stores. "£5 off purchases over £20" is one of Google's own examples of a good offer tagline. Specific prices like those are what Apple says lead to rejection.
The images
| App Store | Google Play | |
|---|---|---|
| Landscape | Event card, 16:9, from 1920×1080 to 3840×2160, JPG or PNG | Primary image, 16:9, 1920×1080, JPG or 24-bit PNG |
| Portrait | Event details page, 9:16, from 1080×1920 to 2160×3840 | No portrait event image |
| Video | Your own file, MOV, M4V or MP4, plays on a loop | A public or unlisted YouTube video with ads turned off, in landscape. Only the first 30 seconds autoplay. An optional Lottie animation too. |
| Text in the image | Avoid when possible, especially the event or app name | Not allowed, apart from text in a partner's logo for a collaboration or text that is part of a product |
| Borders | Don't add borders or gradients. Apple applies its own crops and gradients. | Border frames aren't allowed. |
| Safe area | Check with the preview in App Store Connect | Keep key elements out of the outer 15% at the top, 10% at the sides and 20% at the bottom |
| Other rules | Card and details art should look connected. Use only material you made or licensed. | One clear focal point. Avoid pure white or dark grey. Nothing that looks like buttons or other interface. Avoid generic screenshots and reusing the store listing image. Spotlight needs 1 MB or less. |
Both stores' landscape images are 16:9 at 1920×1080, so one artwork can be the starting point for both. In our own measurements, though, the parts each store covers differ, so a subject placed safely for one can be hidden on the other. You can check an image against both with our free safe area checker.
Planning one event for both stores
- Check Google eligibility first. If your title is an app below the thresholds, only the App Store half of the plan is possible. See who qualifies.
- Use the shorter duration. Four weeks fits both stores.
- Work back from Google's deadlines. A featuring request needs submitting 14 days before the start, and Apple's editors want a nomination at least two to three weeks ahead.
- Write the text twice. Apple wants an event name and no specific prices. Google wants a tagline that says what the event is, and for offers the value within the first 40 characters.
- Match the type. Our badge guide pairs each Apple badge with the closest Google Play type.
Sources
- In-App Events, Apple Developer
- Offer In-App Events, App Store Connect Help
- Manage events, App Store Connect Help
- In-App Event media and audio specifications, App Store Connect Help
- In-App Event statuses, App Store Connect Help
- In-App Events analytics, App Store Connect Analytics Help
- Getting featured on the App Store, Apple Developer
- Nominate your app for featuring, App Store Connect Help
- Understand promotional content, Play Console Help
- Create promotional content, Play Console Help
- Content quality guidelines, Play Console Help
- Track and fix submissions that do not meet content guidelines, Play Console Help
- Evaluate your promotional content performance, Play Console Help
- Google Play Premium growth tools, Play Console guides
- Supporting and rewarding great apps and games on Google Play, Android Developers Blog