Key points:
- Play Console’s own help pages describe a change to how pre-registration is counted. Only active devices count now, each one counted once.
- The old count included devices gone quiet since signup. It also counted the same device twice if someone signed up more than once. That inflated the real number.
- A smaller number after this change means a more honest count. Not an actual loss of real interest.
- New metrics were added at the same time. They track how many people actually open or install from the store listing.
You check your Google Play pre-registration count. It’s noticeably smaller than last week. Nothing about your campaign changed. The counting method did.
What actually changed
Play Console’s own help pages spell this out plainly. Pre-registration counts now only include active devices, each one counted once. Before this, the number included devices that had gone quiet since signing up. It also counted the same device twice if someone signed up more than once. Neither of those was a real, engaged person. The new count strips both out.
| Before the change | After the change |
|---|---|
| Included devices gone quiet | Only active devices count |
| Same device could count twice | Each device counts once |
| Number often too high | Number reflects real interest |
Why a smaller number is actually the better one
A count full of stale, quiet devices tells you less than it looks like it does. It inflates the headline number. It doesn’t say how many people are still genuinely interested by launch day. The new count, smaller as it looks, is a more honest read on real interest.
Find this number under Release, then Reach and devices, then Devices, in the Pre-registration section. New metrics sit right there too, tracking opens and installs tied to the store listing itself. That gives you a fuller picture, not just one raw count.
Real-world scenario: A team prepping a game launch had reported a pre-registration count of 40,000 to stakeholders for weeks. After the counting method updated, the same campaign showed roughly 28,000 instead. Their first instinct was to assume a tracking bug or a mass unsubscribe. Checking Play Console’s own documentation cleared it up. The new number excluded inactive devices and duplicate registrations that had inflated the old count. They updated their internal reporting to explain the change. They used the new acquisition metrics alongside it to get a clearer picture of real launch-day interest.
What to actually do about it
- Don’t panic over a smaller number right after this change. It’s very likely a counting method shift. Not a real loss of interest.
- Explain the methodology change to stakeholders before they ask. A sudden drop without context reads as bad news even when it isn’t.
- Use the new acquisition and open metrics alongside the count. They give a fuller picture than the pre-registration number alone.
- Treat the new number as your real baseline going forward. Comparing future campaigns against the old, inflated count will make every new one look artificially weak.
AppRankr’s Rank Tracker tracks your keyword visibility from the day your app goes live. You get a real, independent read on launch momentum beyond any single pre-registration metric.