Google Play Pre-Registration Campaigns: A Developer's Setup Guide
Launch day is your app's first impression at scale. A well-run Google Play pre-registration campaign means you launch to users who already asked to be notified — many of whom install automatically the moment your app goes live. This guide covers exactly how pre-registration works, how to set it up step by step in Play Console, and how to avoid the mistakes that waste the opportunity.
In short: Pre-registration puts your store listing live before launch so users can sign up to be notified — and on eligible devices the app installs automatically on launch day. Campaigns last at most 90 days per country, so set up your declarations and listing, pick your launch markets, and start 3–6 weeks before release.
A pre-registration campaign builds an audience before launch day.
What does pre-registration actually do?
When you enable pre-registration, your app's store listing becomes visible on Google Play with a "Pre-register" button instead of an install button. Users who tap it are expressing interest in your app before it launches. When you release the app, Google notifies every pre-registered user — and users who opted into auto-install get the app installed on their device without lifting a finger.
Three things make this worth doing:
- Launch-day spike. Pre-registered users convert at very high rates, often within the first 24–48 hours. That concentrated burst of installs feeds the trending and top-chart algorithms exactly when they matter most.
- Early feedback loop. Pre-registration numbers by country tell you where demand is before you spend a dollar on launch marketing, so you can allocate budget to markets that already want the app.
- Compounding visibility. Google surfaces pre-registering apps in dedicated discovery surfaces (the "Pre-registration" games/apps sections), giving you a second storefront while you finalize the build.
Google's pre-registration guide covers the full process, including the requirements below and the 90-day limit per country.
What do I need before I start?
Pre-registration only works for apps that have not yet launched in the countries you want to target. You also need the app in a publishable state, which means:
- App created in Play Console with the package name finalized. This can't change later, so get it right.
- All required declarations completed: App access, Ads declaration, Content rating (complete the IARC questionnaire), Target audience and content, News apps declaration if applicable, and the Data safety section. Incomplete declarations are the most common reason pre-registration gets stuck.
- A complete store listing: 512×512 app icon, 1024×500 feature graphic, at least two screenshots per supported form factor, a short description (80 characters) and a full description (up to 4,000 characters). Your pre-registration page is your store listing — there is no separate page.
- A build on a test track. Google strongly recommends rolling out a release to a test track and testing your app before starting pre-registration. Upload an AAB to a testing track and let it pass review — the first review can take several days, so do this early.
Two hard limits to plan around: a campaign can last at most 90 days per country, counted from the day pre-registration first becomes available there — if the app hasn't launched within 90 days in a country, the campaign ends there. And you can make up to two apps or games available for pre-registration at a time. Personal developer accounts created after 13 November 2023 must also meet Google's testing requirements before they can use pre-registration.
Plan for a 3–6 week active campaign. Less than two weeks gives you no time to build momentum; more than three months and you hit the 90-day cap, with users forgetting they ever pre-registered.
How do I set up pre-registration in Play Console?
With the prerequisites done, the setup itself is straightforward:
Selecting core launch markets gives cleaner pre-registration data.
- Select your app in Play Console and open Release in the left menu, then choose Pre-registration.
- Select the countries or regions where you want to offer pre-registration. Start with your core launch markets rather than the entire world — you'll get cleaner data and can manage localization properly. Each country runs its own 90-day clock from the day you first make pre-registration available there.
- If you want to offer incentives, configure pre-registration rewards. Rewards (in-game items, exclusive content, premium unlocks) are delivered automatically to pre-registered users when they install at launch. Make them genuinely exclusive — a cosmetic item nobody else can get converts far better than a small currency bundle. Note that you get one reward product for the campaign, and it can't be edited or deleted once created.
- Double-check your store listing as it will appear to pre-registering users, then enable pre-registration. Google will confirm once it's live.
One critical timing note: submit your production build for review at least a week before your planned launch date. Pre-registration ends the moment you release to production, and if your production build sits in review for five days, you lose five days of your campaign and the momentum that comes with a coordinated launch.
How do I maximize sign-ups?
Pre-registration is a funnel, and every step leaks. Work through this checklist:
Six practical steps to maximize pre-registration sign-ups.
- Treat the listing as a launch page. The feature graphic, screenshots, and first two lines of the description do the selling. A gameplay trailer or product demo video dramatically outperforms static graphics.
- Localize for target countries. At minimum, translate the short description and key screenshots into the languages of your top three target markets. Pre-registration conversion varies hugely by region, and unlocalized listings leak sign-ups in exactly the markets you're targeting.
- Make the reward tangible and visible. Announce the reward prominently in the description and in external marketing. "Pre-register to unlock the exclusive Founder skin" beats a vague promise of "launch bonuses."
- Drive external traffic. A landing page with the Play badge, social campaigns, influencer seeding, community posts (Discord, Reddit, forums), and your existing email list all feed the pre-registration count. Google tracks where pre-registrations come from, so you can see which channels work.
- Keep the drumbeat going. Post development updates, behind-the-scenes content, and countdown posts during the campaign. Silence between pre-registration and launch is how you lose half your audience.
- Watch metrics weekly. Play Console shows pre-registrations by country. If one country is overperforming, shift marketing spend there; if a channel is dead, cut it.
What happens on launch day?
When you're ready, create your production release. The moment it goes live, pre-registration ends and notifications go out. What happens next in the first 72 hours sets the tone for your launch:
- Monitor crash rates and ANRs obsessively during the first three days. A spike in pre-registered users hitting a day-one crash is the fastest way to convert a great campaign into a 3.2-star rating.
- Respond to the first wave of reviews within hours, not days. Early reviews carry disproportionate weight in the rating average while the count is low.
- Stagger your marketing. Let the pre-registration notification wave hit first (day 1), then layer in paid acquisition (days 2–3). This stacks install velocity instead of spreading it thin.
If coordinating release tracks, review timing, and the production cutover is eating more of your schedule than actual development, it can be worth getting an experienced hand on the publishing side. Play Console Store, for example, offers hands-on help with Google Play release management and launch coordination at their publishing services page, so your team can stay focused on the app itself.
What mistakes should I avoid?
- Submitting for review too late and missing your own launch date.
- Targeting every country with an English-only listing and wondering why conversion is poor in non-English markets.
- Going silent between pre-registration and launch.
- Launching with a known crash in the build that pre-registered users will hit first.
Run the campaign deliberately, treat the pre-registration page as a real launch asset, and you'll start day one with an installed user base most apps take months to build.
FAQ
How long can a pre-registration campaign run?
At most 90 days per country, counted from the day pre-registration first becomes available there. If the app has not launched within 90 days in a country, the campaign ends there. Aim for 3–6 weeks of active promotion — long enough to build momentum, short enough that sign-ups still remember you.
What do I need before I can switch on pre-registration?
Your app created in Play Console with all declarations complete — app access, ads, content rating, target audience and data safety — plus a complete store listing and a build uploaded to a test track. Personal accounts created after 13 November 2023 must also meet Google's testing requirements first.
What happens when the app launches?
Pre-registration ends the moment you release to production. Every pre-registered user gets a push notification from Google Play, and on eligible devices the app installs automatically. Users who already have a test version installed do not get the notification, so check your tester lists before launch.
Can I offer a reward for pre-registering?
Yes — one optional reward, a free one-time in-app product such as an exclusive cosmetic or premium unlock, delivered automatically when pre-registered users install at launch. Set it up before the campaign starts: the reward product cannot be edited or deleted once created, so choose something genuinely exclusive.
How many apps can I pre-register at once?
Two. Google lets you make up to two apps or games available for pre-registration at a time, and each country runs its own 90-day clock from the day pre-registration first becomes available there. If you are launching several apps, stagger them so each gets a proper campaign window.
About the author
This guide was prepared by the publishing team at Play Console Store — an independent marketplace for Google Play publishing services (release management, closed testing coordination, policy compliance, and app publishing assistance), not affiliated with or endorsed by Google LLC.
Top comments (0)