How App Store Pre-Orders and Google Play Pre-Registration Differ for a Mobile Game Launch: Setup, Launch Day, Rewards, and a 12-Week Plan
Launching the same game on both stores does not mean your pre-launch sign-ups work the same way on both. As of October 2026, an App Store pre-order for a first-time app can carry a release date anywhere from 2 to 180 days out, and it only goes live once a build has passed App Review. Google Play pre-registration can stay open for no more than 90 days, and if you do not launch within that window, the campaign is terminated in every country and you cannot start a new one. The reward features, what happens on players' devices on launch day, and the metrics each console shows are different too.
Those differences show up in your results. Play Console counts a conversion when a pre-registered user installs within 14 days of launch, while App Store Connect shows pre-orders and cancellations and leaves it to you to measure whether people actually open and play the game. That is why the numbers rarely line up when both stores are judged against one KPI.
We covered the basics of pre-order campaigns in 4 Strategies to Maximize Pre-Order Campaigns for Games, and the role and design of Google Play pre-registration in Why Pre-Register on Google Play Matters — And What to Do Beyond and Pre-Registration Campaigns: How to Build Hype and Secure Day-One Installs. This post is a working guide for launch teams who have to run both stores at once. It walks through how the two programs differ, the setup order, launch-day behavior, reward design, a 12-week timeline and budget, and how to measure results and vet outside campaigns.
How do App Store pre-orders and Google Play pre-registration differ?
The biggest differences are the time window and what you need before you start. The App Store requires a reviewed build and an expected release date but lets you stay in pre-order for up to 180 days, while Google Play lets you start with a bundle that is never released to users but holds you to a strict 90-day deadline.
Item | App Store pre-order | Google Play pre-registration |
|---|---|---|
Where to set it up | App Store Connect > Pricing and Availability > App Availability | Play Console > Test and release > Testing > Pre-registration |
Maximum window | First-time apps: 2-180 days after the pre-order is published. Existing apps in a new country or region: 2-365 days | Up to 90 days from the first time pre-registration opens in each country |
Prerequisites | Build approved by App Review, expected release date, countries or regions | App content declarations, bundles defining supported devices (not released to users), a complete store listing |
Concurrency limit | None stated | Up to two apps or games at a time |
Account requirements | Account Holder, Admin, or App Manager role | Personal developer accounts created after November 13, 2023 must meet testing requirements first |
Store presence | Limited product page with an expected release date; appears in search results | Pre-register button shown instead of Install |
Built-in reward | None. Grant rewards in-game using the pre-order date in the app transaction | One one-time product can be set as a pre-registration reward |
Launch day | Notification plus automatic download to the device used to pre-order | Notification plus automatic install on eligible devices for users who opted in |
Console metrics | Pre-orders by date, region, and source type; cancellations | Pre-registered users; conversions (installs within 14 days of launch) |
Delays and expiry | Release date can be moved within 180 days of first publication (365 for a new region). Apple does not notify customers of changes | No launch within 90 days ends the campaign in all countries; no new campaign can be started |
Paid promotion | Apple Ads, such as search results ads (manual bidding recommended) | Google Ads App campaigns for pre-registration (target cost per pre-registration) |
Two rows in this table drive launch planning more than the rest. First, if your launch date might slip, do not open Google Play pre-registration too early. Apple lets you move the date within 180 days of first publication, but Google Play ends the campaign when 90 days run out. Second, because an iOS pre-order needs a reviewed build, it often opens later than Google Play in a real production schedule. Some guides still say Apple's pre-order window is 90 days, but as of October 2026 the App Store Connect Help allows 2 to 180 days for a first-time app.
How do you set it up on each store?
The App Store sequence is review first, then publish; the Google Play sequence is declarations, bundles, countries, and rewards, then start. On Google Play the reward must be created before pre-registration starts and cannot be edited afterward, so getting the order wrong is not reversible.
For a game's first release, the App Store pre-order setup goes like this. In App Store Connect, open Pricing and Availability, choose Set Up Availability under App Availability, select Publish as Pre-Order, then choose a release date 2 to 180 days out and the countries or regions. Nothing is public yet at this point. Next, submit the build for review, and once it is approved, click Release This Version to publish the pre-order page. The pre-order goes live immediately but may take up to 24 hours to appear for all users. In-app purchases cannot be pre-ordered themselves, though you can set them up during the pre-order period. For a paid app, customers are charged on the release date, and if the price changes in the meantime they pay the lower of the price they accepted and the price on release day.
The Google Play sequence has more steps. You need to provide app content information, including whether the app contains ads, before the pre-registration section becomes usable, and Google strongly recommends rolling out to a test track first. Then build a complete store listing with graphic assets and translations, and upload app bundles on the pre-registration track to define supported devices. These bundles are not released to users. Choose countries, keeping in mind that country means the country where the user is registered on Google Play, not their physical location. If you plan to offer a reward, set it up at this step, and finally select Start pre-registration. If the game has one-time products, the bundle on the pre-registration track must include the BILLING permission and the Google Play Billing Library.
Both stores also let you use store page optimization tools during the pre-launch phase. Google Play allows up to 50 custom store listings, one of which can target users who can pre-register, and store listing experiments can use pre-registration clicks as the target metric. Apple says existing apps taking pre-orders in a new region can use custom product pages and product page optimization. If you are deciding whether to outsource store page testing, we compared scope and cost in What Do App Store Optimization Services Actually Deliver for Games?
What happens to pre-registered players on launch day?
Both stores send a notification and download the game automatically on launch day, but the conditions for automatic installation differ. On iOS the game downloads to the device used for the pre-order by default; on Android it installs automatically only when the user has opted in to auto-install and the device and app size meet Google's conditions.
On the App Store, customers get a notification on release day and the app downloads automatically to the device they pre-ordered on. It also downloads to other eligible devices that have automatic downloads turned on. You can release early during the pre-order period, and customers still get the notification and the automatic download.
On Google Play, once you publish to production, everyone who pre-registered gets a Play Store notification, and the app installs automatically on eligible devices for users who opted in. The conditions are specific. The device needs Android M or later and Play Store version 19.2 or later, and accounts for children under 13 and managed enterprise accounts are excluded. Apps up to 200MB auto-install on Wi-Fi or mobile data, apps over 200MB and up to 2GB auto-install only on Wi-Fi, and apps over 2GB do not auto-install. Ineligible devices still get the notification, and Play retries the auto-install once conditions are met.
That leaves game teams with three practical points. First, manage the initial install size. A game over 2GB gets no auto-install on Google Play, and above 200MB the install waits until the device is on Wi-Fi. Designing large assets to download after first launch helps auto-install, but a big download right after first launch is a drop-off point of its own, so pair it with a tutorial or clear progress messaging players can use while they wait. Second, an auto-install is not a play session. A game sitting on the device does nothing until the player opens it, so you need something that pulls players into a first session after the launch notification, such as a reward claim prompt, a launch event, or a community announcement. Third, if the date changes, you have to tell people yourself. Apple does not notify pre-order customers when the release date changes or the pre-order is removed, and it advises against putting the date in marketing if it might move.
How should you design pre-registration rewards?
The principle is to give the same value on both stores, deliver it inside the game, and keep it small enough not to disturb the game economy. The delivery mechanics differ, though. Google Play provides a reward delivery structure in the store, while on the App Store the game itself must check whether a player pre-ordered and grant the reward.
Google Play's pre-registration reward lets you give one active one-time product to pre-registered users for free. The rules are strict. You can create only one reward for the lifetime of the pre-registration campaign, it cannot be edited or deleted once created, and it cannot be switched on or off while the campaign is active. You must create a product dedicated to pre-registration rather than reusing an existing one, and subscriptions are not allowed. Users must accept your terms and conditions before receiving the reward, and the game must tell them about the reward through in-game messaging within a reasonable time. Google states that failing to deliver rewards may result in the app being suspended from the Play Store, and it recommends generating a promo code for the reward product in Play Console to test the delivery flow beforehand.
The App Store has no built-in reward feature. Instead, Apple suggests identifying pre-order customers through the pre-order date in the app's receipt data (the preorder date in StoreKit's AppTransaction) and using it to show a thank-you message or unlock rewards such as bonus in-game currency. In other words, the iOS reward is work that belongs in your client and server development schedule.
Public data on reward impact is limited, but one case published by Google is useful. In a 2019 Android Developers Blog post, Nexon said it had historically seen about 50% of Google Play pre-registrations convert to installs, and that offering a pre-registration reward (in-game currency) raised the conversion rate by 20%. In the same case, pre-registered users had nearly 50% higher day-60 retention than users who did not pre-register. It is an older, single case, so read it as evidence of direction, that rewards affect conversion, rather than as a benchmark.
A few practical rules for reward design follow from this. Match the reward value across both stores so players on one platform do not feel shortchanged. Cosmetics, profile decorations, and items that help early progression are safe choices because they do not distort the economy right after launch. Milestone rewards, where every player's reward grows as total sign-ups hit targets, can combine both stores' counts and are common in cross-platform launches. Keep rewards to in-game items and experiences and avoid describing them in cash or cash-equivalent terms. Setting the expectation that the game is a way to earn money does not help retention after launch.
What does an 8-12 week timeline and budget look like when you run both stores?
The core of running both stores in parallel is to plan backward from Google Play's 90-day limit. Opening pre-registration before the launch date is firm puts you on the clock, so a realistic setup is to open Google Play pre-registration 8 to 12 weeks before launch and open the iOS pre-order as soon as a reviewed build is ready, at the same time or a little later.
In its guidance on pre-registration ad campaigns, Google recommends turning pre-registration on at least two weeks before pre-launch marketing, says 3 to 6 weeks is enough for most campaigns, and suggests 9 to 12 weeks when you expect high interest. The table below is a 12-week example built on that guidance and each store's limits.
When | Google Play | App Store | Marketing and measurement |
|---|---|---|---|
13-12 weeks before launch | Submit app content declarations, confirm testing requirements for personal accounts, finish the store listing and translations, create a dedicated reward product | Prepare the review build, choose countries | Set sign-up targets by country and decision criteria, design the tracking link structure |
12-10 weeks before | Set up the reward, then start pre-registration (the 90-day clock starts) | Submit the build for review, publish the pre-order once approved | Open pre-registration pages on the website, community, and social channels; apply store badges |
10-4 weeks before | Custom store listings, store listing experiments on pre-registration clicks | Avoid putting the date in marketing until it is firm | Google Ads pre-registration campaigns, Apple Ads search results ads (manual bidding), partner and influencer campaigns, milestone reveals |
4-1 weeks before | Test reward delivery with a promo code, check the build against auto-install size limits | Test reward delivery based on the pre-order date | Prepare launch-day communication (notification copy, events, coupons) |
Launch week | Add production countries and publish; pre-registration ads stop automatically in launched countries | Release date arrives, or release early | Switch pre-registration campaigns to install and re-engagement campaigns |
Two weeks after launch | Check 14-day install conversions | Check pre-order cancellations and first opens | Compare D1 and D7 retention by channel cohort |
It is easier to manage the budget in five buckets. The first is store page and creative production: key art, trailers, localization by country, and the number of custom pages you run. The second is store advertising. Google Ads pre-registration campaigns bid on a target cost per pre-registration and serve on Google Play, YouTube in-stream, and the Display Network. Apple Ads recommends manual bidding for apps in pre-order and says Maximize Conversions is designed for post-launch campaigns only. In one Apple Ads success story, an open-world action RPG ran Today tab, Search tab, and search results ads together during the six weeks before release, and Apple Ads drove 30% of the game's total iOS new-user downloads during the pre-order phase (Apple's own case study). The third is partner and community campaigns, which covers media with dedicated pre-registration products, influencers, and gaming communities. The fourth is development time for rewards and launch-day events. The fifth is measurement tools and analytics staff. We covered the wider pre-launch marketing sequence in Mobile Game Marketing Strategy Before Launch, and what to validate before pre-registration in Soft Launch Strategy: What to Validate, and When to Go Global.
How many sign-ups become installs, and how do you measure each channel's contribution?
Judge pre-registration by how many people actually install and play after launch and how well they retain, not by the number of sign-ups. Conversion varies widely by game and channel, so a system for comparing your own channel cohorts matters more than any industry average.
Published conversion benchmarks are rare. The Nexon case above, about 50% historically and a 20% lift with a reward, is one of the few figures Google has published, and it is a single case from 2019. The reasons conversion varies so much are structural. Auto-install opt-in and device and size conditions shape Android conversion, interest fades the longer the gap between sign-up and launch, and delays increase drop-off. Motivation matters too. Players who signed up only for the reward behave differently after install from players who signed up because they like the genre.
Scale does not guarantee quality, even in the biggest launches. According to a 2024 Deconstructor of Fun analysis, Supercell's Squad Busters collected 40 million pre-registrations with rewards offered across Supercell's other games, and first-month cumulative downloads were also about 40 million by Sensor Tower's estimate. But downloads fell quickly after peaking in the first five days, and more than 60% of download volume came from Tier 3 countries. Where pre-registrants come from shapes the curve after launch.
Measurement has to be set up differently on each store. On Google Play, the console's pre-registration metrics are the baseline: pre-registered users and conversions, meaning installs within 14 days of launch, are available on the Statistics page. Note that ad-side numbers use different rules. Google Ads can count a pre-registration even if the user later unregisters, and can count repeat pre-registrations from the same user, while Google Play counts only users who are still pre-registered. On the App Store, App Analytics shows pre-orders by date, region, and source type, and Sales and Trends shows pre-orders and cancellations. Apple Ads pre-order metrics are counted within 30 days of an ad tap or 24 hours of an ad view, and pre-orders canceled later are not subtracted.
The simplest way to separate each channel's contribution is to send each traffic source to its own store page. Apple recommends creating a unique URL for each custom product page and using it only in the matching campaign, and Google Play custom store listings can also be targeted through a unique URL. Add an in-game record of pre-registration status after launch (the pre-order date on iOS, reward redemption on Android), and you can see which channel's pre-registrants were still playing on D1 and D7.
If you are evaluating an outside pre-registration campaign vendor or media partner, ask these questions before signing.
Question | What you are checking |
|---|---|
Does the sign-up happen in the store, or in a form inside the partner's platform? | Whether it becomes a real store pre-registration or pre-order that gets the launch notification and auto-install |
Which OS and countries do you cover? | Android only or iOS too, and overlap with your launch countries |
Do you report installs, first opens, and D1 and D7 by cohort after launch? | Whether you can judge quality after launch rather than sign-up volume |
Why do your users sign up? | Genre interest versus a high share of reward-only participants |
How do you bring users back on launch day? | Push, coupon delivery, in-platform announcements, or other first-session triggers |
How do you charge? | Price per sign-up, a fixed package, or pricing tied to post-launch installs and actions |
Do you avoid promoting rewards as cash or cash-equivalent value? | Brand safety and store policy risk |
A first engagement is safest as a pilot. Use one or two countries and a four-to-six-week pre-registration window, separate channels with unique store page URLs, and write the decision rules down in advance. For example: "If the partner channel's 14-day install conversion and D7 retention are not far below those of organic pre-registrants, expand into post-launch UA," or "If sign-ups are high but first opens after install are low, strengthen launch-day re-engagement or switch channels."
Where does Playio's pre-registration product fit in a launch plan?
Playio is an advertising platform built on a gamer community of 5 million players, and its global user base is Android-centric, so in the terms of this post it is a partner channel that supports the Google Play pre-registration side. iOS pre-orders are better planned around Apple Ads, custom product pages, and your own channels.
Playio's pre-registration product comes in three tiers, Step-Up, Premium, and Premium PLUS, which are provided at no cost depending on campaign spend. The base tier includes placement in the pre-registration list, post-launch coupon delivery, tracking links, and dashboard access, and higher tiers add placements such as a push message, a full-screen popup banner, a Playio mailbox message, and a Today banner. You can choose direct participation, where players go on to pre-register in the store themselves, or automatic participation, which prioritizes sign-up volume; if post-launch install conversion and engagement are the goal, direct participation is the better fit. AI analyzes the genre preferences, play history, and in-game behavior of 5 million gamers to show the campaign first to players whose tastes match the game, which is aimed squarely at the question raised above: who you bring in. After launch, the same channel can continue on CPI as the default model, with CPE also available, so you can follow pre-registrants through to actual play in one place.
If your launch date is set, we suggest designing a pilot inside Google Play's 90-day window first. Send your planned launch date, target countries, genre, planned Google Play pre-registration start date, and the pre-registration reward you are preparing to [email protected], and we will send back a pre-registration pilot plan covering countries, duration, participation type, post-launch coupon delivery, and decision rules based on 14-day install conversion and D7 retention.
You can find more details here. (https://playioadsen.oopy.io/bizdeck)
Key takeaways
As of October 2026, an App Store pre-order requires a build approved by App Review and can run for up to 180 days for a first-time app, while Google Play pre-registration can start with bundles alone but ends in every country if you do not launch within 90 days. On launch day both stores send a notification and download or install the game automatically, but Android auto-install depends on user opt-in and device and size conditions (the 200MB and 2GB thresholds), and Apple does not tell customers when the release date changes. Match reward value across Google Play's pre-registration reward (set once, not editable) and iOS in-game rewards based on the pre-order date, and avoid cash-like framing. Plan backward from Google Play's 90-day limit to run an 8-12 week campaign, and judge results on 14-day install conversion and D1 and D7 by channel cohort rather than sign-up counts. For outside campaigns, confirm that sign-ups are real store pre-registrations, that the partner reports post-launch cohorts, and why its users sign up, then start with a small pilot. That is the approach you are least likely to regret.
For inquiries about Playio's advertising solutions, reach out at: [[email protected]](mailto:[email protected]?subject=Playio%20inquiry%20from%20blog%20-%20pre-registration%20pilot)
Sources
App Store Connect Help, Publish for pre-order (2-180 days for first-time apps, 2-365 days for new regions, limits on editing the release date, required roles, Release This Version after review, up to 24 hours to appear, charged on release at the lower price, release-day notification and automatic download, early release, in-app purchases and bundles not eligible): https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/publish-for-pre-order/
Apple Developer, Offering your apps for pre-order (limited product page and search visibility; Apple does not notify customers of date changes or removal; avoid dates in marketing if they may change; preorder_date to unlock rewards; App Analytics pre-orders by date, region, and source type; Sales and Trends pre-orders and cancellations; Apple Ads; custom product pages): https://developer.apple.com/app-store/pre-orders/
App Store Connect Help, Pre-order report (Ordered and Canceled metrics): https://developer.apple.com/help/app-store-connect/reference/pre-order-report/
Apple Ads, Maximize Conversions best practices (designed for post-launch campaigns only, not pre-order campaigns): https://ads.apple.com/app-store/best-practices/maximize-conversions
Apple Ads Help, Search Results (Manual Bid strategy recommended for apps in pre-order): https://ads.apple.com/app-store/help/ad-placements/0082-search-results
Apple Ads Success Stories, Wuthering Waves (six-week pre-order campaign across Today tab, Search tab, and search results; 30% of total iOS new-user downloads driven by Apple Ads during the pre-order phase. Apple's own case study): https://ads.apple.com/app-store/success-stories/wuthering-waves
Apple Ads Help, Reporting options and definitions (pre-order metrics: 30 days from tap, 24 hours from view; later cancellations not subtracted): https://ads.apple.com/app-store/help/reporting/0023-reporting-options-and-definitions
Google Play Console Help, Build awareness for your apps with pre-registration (90-day limit, per-country clock, two apps at a time, testing requirements for personal accounts, app content declarations, supported-device bundles, country definition, reward rules, possible suspension for undelivered rewards, promo code testing, auto-install conditions including Android M+, Play Store 19.2+, under-13 and managed accounts excluded, 200MB and 2GB thresholds, 14-day install conversion metric, campaign terminated in all countries if not launched within 90 days): https://support.google.com/googleplay/android-developer/answer/9859047?hl=en
Google Ads Help, About App campaigns for pre-registration (target cost per pre-registration, networks, counting differences between Google Ads and Google Play, ads stop in launched countries, turn on at least two weeks before marketing, 3-6 weeks typical, 9-12 weeks for high interest): https://support.google.com/google-ads/answer/9441344?hl=en
Google Play Console Help, Create custom store listings (up to 50; targeting users who can pre-register; targeting via a unique URL): https://support.google.com/googleplay/android-developer/answer/9867158?hl=en
Google Play Console Help, Run A/B tests on your store listing (unique user pre-registration clicks as a target metric): https://support.google.com/googleplay/android-developer/answer/6227309?hl=en
Android Developers Blog, Nexon increases day 60 retention and conversion with pre-registration rewards, August 13, 2019 (about 50% historical pre-registration-to-install conversion, 20% higher conversion with a reward, nearly 50% higher day-60 retention for pre-registrants): https://android-developers.googleblog.com/2019/08/nexon-increases-day-60-retention-and.html
Deconstructor of Fun, Squad Busters One Month Later: Down, But Not Out, July 8, 2024 (40M pre-registrations, about 40M first-month downloads per Sensor Tower estimates, pre-registration rewards across Supercell games, more than 60% of downloads from Tier 3 countries): https://www.deconstructoroffun.com/blog/2024/7/8/squad-busters-one-month-later-down-like-a-lot-but-not-out