Google Play Pre-Registration Is a Reservation, Not a Teaser

Most teams treat pre-registration as a warm-up: put up a countdown, assume people turn up on the day. Launch day comes, the notification goes out, installs land far below the plan, and the post-mortem blames the creative.

The framing is wrong from the start. Pre-registration is not a warm-up. It is a way to hold a slot — three specific slots — and what matters is whether you put something in them.

The short version

Pre-registration does three things. It makes your store listing visible and searchable before launch. It records intent against the user's Google Play account. And it puts an install notification in front of those users at launch, with automatic installation on eligible devices.

The second is where the value sits. The third is where teams leak.

If you want a clean install path on day one, pre-registration earns its place. If you want awareness, it will not deliver that — ads or content will.

Three slots, not a campaign

The first is in the store. Once pre-registration is open your product page exists: screenshots, description, video, with the button reading pre-register instead of install. You hold a page that can be indexed, shared, and used as a landing page for paid traffic. Plenty of teams waste it, building the pre-launch page rougher than the launch page because nobody is looking yet.

The second slot is in the account. Tapping pre-register records intent against a Google Play account. It is not a push permission someone can swipe away.

The third slot is on the device. At launch, Google Play notifies every pre-registered user and installs automatically on eligible devices. That is holding a position in the most literal sense.

The five steps, and where teams lose the plot

The official flow is documented, and I will not restate menu paths — those move, so check the current official guidance before you ship. Instead, the places teams trip.

Step one is preparation. Pre-registration has its own requirements, guidelines and recommended prep activities. This step gets skipped most often, because it reads like documentation rather than work.

Step two is device targeting. You upload an app bundle and Play reads the manifest to work out which devices can pre-register. Read the parenthetical: that bundle is only used to determine device eligibility, it is not distributed to users. So do not treat it as a soft-launch channel. If the app sells one-time products, at least one bundle has to include the Play Billing Library, or the reward path will not work.

Step three is countries, which deserves its own section.

Step four is optional: a pre-registration reward. You can attach a free one-time product that users get by tapping pre-register, no promo code needed. It is a strong hook with a real cost — it pulls in people who want the free item, which dilutes launch-day conversion. Run it if you are optimising for a number, skip it if you are optimising for retention.

Step five is turning it on, then driving traffic with the pre-registration URL — the documentation is explicit that promotion should use that link.

Your pre-registration page is a store listing, not a poster

The user deciding whether to tap is looking at the icon, the title, the first two screenshots, the short description, and whether there is a video. Those assets need launch-grade treatment during pre-registration, because the page does the same job under worse conditions — no reviews, no download count, no chart position to borrow credibility from.

The starkest version: the launch page is carefully built, the pre-registration page thrown together in an afternoon. The people you spent weeks collecting land on a half-finished page and hit back.

A pre-registration user does not need your roadmap, but must recognise what kind of thing this is at a glance. If the category is unclear, every dollar of traffic after that is aimed at the wrong person.

Why the installs leak on launch day

There is always a gap between pre-registrations and day-one installs. A collapse traces to one of three breaks.

Break one: devices with a test build installed do not get the notification. Users who already have a test version installed will not receive the push. Teams running a beta walk into this every time, because the most enthusiastic early users are the ones who helped you test — so they are the ones who will not be reminded. Knowing this, message the beta group directly on launch day.

Break two: automatic installation has conditions, and "eligible" is doing real work in that sentence. Eligibility touches device, account, network and settings; check the current official guidance for the exact criteria. Practically: never paste your pre-registration count into a report as the day-one install forecast. They are different numbers.

Break three: the date slips. Pre-registration is a public promise about when the app ships. One delay costs credibility with everyone who registered; several and they have been absorbed by other apps. That cost never shows up in a dashboard, but it is paid.

The country you pick is the account's country, not the phone's

The country you select in pre-registration settings is the country registered on the user's Google Play account, not where the person physically is. A Brazilian account on a business trip in Germany still counts as Brazil.

Ad platforms target by device and location. The store targets by account. When those definitions diverge you get the classic failure: the ad reaches country A, the user taps through, and there is no pre-register button on the page. Check with a test account in each target market before scaling spend.

The flip side is an advantage: if your audience is a diaspora, this rule works in your favour.

App Store has no equivalent, so do not sync the calendars

Dual-store teams like one calendar for both platforms. Pre-registration breaks that.

Google Play pre-registration is its own pre-launch pipeline — its own page, device scope, country list, reward mechanics. The App Store has a different construct, usually translated as pre-order, with a different flow, interface and delivery at launch. Check the current official guidance on both before you plan.

So "Android is pre-registered" does not mean "iOS is ready". What genuinely aligns is the asset set: screenshots, video, copy, the order of your selling points — one production run, two stores. Launch sequence, notification path and conversion funnel are counted separately.

My default: schedule pre-registration as an Android-only workstream, and finish the iOS metadata in the same sprint.

When not to run pre-registration

Not when the launch date is uncertain. It is a public commitment and users will see your date. If the schedule is still being negotiated with engineering, wait — the value of the slot does not cover the cost of a slipped date.

Not when the app is not presentable. The page needs screenshots and video. If core screens are still moving, everything you publish gets replaced at launch.

Not when you are testing a small market with no pre-registration habit. You will collect a number too small to read anything from. Spend that effort on keywords and screenshots — that work keeps paying after launch day.

Not when the goal is demand validation. Pre-registration counts are a poor proxy for demand because they are nearly free: no payment, no contact details. A landing page with a signup form answers that question far better.

Three numbers worth watching during the window

First, source mix: store search, paid landing pages, community. This tells you where to add budget on launch day.

Second, page view to pre-registration rate. Even before launch it tells you whether the screenshots and short description explain the product. Low, and the problem is the page; high with small volume, and the problem is traffic.

Third, market coverage. Within your selected country list, which markets produce and which are empty. Fill them with localisation or switch them off — do not let them inflate the denominator in your reports.

What to do next

1. Open your pre-registration settings in Play Console and confirm the bundle used for device targeting is current, not a package from six months ago. 2. Pull the country list and compare it against your ad targeting, looking for gaps where the ad reaches a market but the button does not appear. 3. Rebuild the pre-registration listing to launch standard: icon, first two screenshots, short description, video. Nothing deferred to launch week. 4. Message your beta group directly on launch day — per the official documentation, their devices will not receive the notification.

If you are planning an overseas launch across both stores and are unsure whether pre-registration belongs in this release, there is a consultation widget on this site. Send us the app's current state and target markets. Youou would rather help you work out what the slot is actually worth than tell you to open one.