How to Use This Tool
Apply device availability and expected conversion to the active pre-registration audience. A pre-registration headline overstates launch load when territory, device availability and actual install behavior reduce the reachable cohort.
Why Play Pre-Reg Installs needs more than a raw total
Play Console reports active pre-registered users, but conversion remains an assumption until the launch cohort matures. For this page, the useful comparison is estimated launch installs, not whichever input happens to be largest. The Play Pre-Reg Installs result answers the decision in the heading and should not be reused as a score for a different workflow.
The exact Play Pre-Reg Installs formula
Estimated installs equal active pre-registrations × launch-available share × registration-to-install rate. The visible fields are Active pre-registered users, Compatible and available at launch and Registration-to-install rate. For Play Pre-Reg Installs, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed estimated launch installs may be arithmetically valid but operationally meaningless.
Interpreting estimated launch installs
Capacity-plan from a conservative install case and compare realized installs with the same eligibility definition after launch. The ten-percent comparison is deliberately narrow: it tests the influence of active pre-registered users and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Play Pre-Reg Installs supported the choice.
What this Play Pre-Reg Installs model leaves out
Automatic installs, notifications, country rollout, device compatibility changes, duplicate accounts and organic installs are excluded. That is where Play Pre-Reg Installs stops being trustworthy. If an excluded factor could reverse estimated launch installs, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.
Evidence and independent verification
The reference reviewed for Play Pre-Reg Installs is Google Play Console Help — App quality and reach. Google Play Console Help — App quality and reach supports the named definition or rule but does not supply private values for estimated launch installs. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.
Private, reproducible calculation
Play Pre-Reg Installs runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Play Pre-Reg Installs inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen Google Play Console Help — App quality and reach and rerun the saved Play Pre-Reg Installs scenario.
Sources & assumptions
Tool Spec v2 · verified 2026-08-22. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- Google Play Console Help — App quality and reach (checked 2026-08-22)
Model assumptions
- Every input covers the same reporting period or cohort.
- Automatic installs, notifications, country rollout, device compatibility changes, duplicate accounts and organic installs are excluded.
- The calculator uses only the visible fields and does not fetch account data.
