Google Play pre-registration feature changes operators must track
Analysis
By UA Ledger staff — 1 min read

Pre-reg rewards and listing rules keep changing. Operator card from the current Play Console pre-registration help article.
Operators should track Play pre-registration as a dated rule card, not a remembered blog rumour.
Current rules (body-read 20 September 2026)
From Build awareness with pre-registration:
- Pre-registration can last 90 days, after which the app must launch to production; missing the window can terminate campaigns across countries.
- The 90-day clock for a country starts when pre-registration is first enabled there.
- Upload app bundles on the pre-registration track to declare supported devices; those bundles are not user releases.
- Optional pre-registration rewards (one-time products) must be deliverable — Play states failure may suspend the app.
- Google strongly recommends a test track before enabling pre-registration.
- Promote the listing URL across channels; eligible devices may auto-install on launch when opted in.
About App campaigns for pre-registration requires Console pre-reg first and notes count discrepancies between Ads and Play Console.
Facts vs limits
| Fact | Limit |
|---|---|
| 90-day, rewards, device AABs, Ads prerequisite documented on help pages | This card is not a full historical diff of every 2023–2026 UI tweak |
| Re-check the help article before each campaign | Android Developers Blog posts may announce future changes earlier |
CSV.
Draft prepared 20 September 2026. Local expansion-500 file; human editorial review pending. No CMS write.
Featured
Related posts
More from the Platforms desk
platforms
·Archive date: 4 min read
Roblox Everywhere: when a platform ships standalone apps, it competes for your installs
measurement
platforms
·2 min read
AppLovin Ad Review drops user-level journeys for aggregate-only reporting
measurement
platforms
·2 min read
Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets
platforms
·1 min read