How Many Active Users Are Exposed by Ending Old-Version Support?

How to Use This Tool

Translate version share into the user cohort requiring migration or communication. A low old-version percentage can still represent thousands of people who will lose functionality after a backend or compatibility cutoff.

Why Version Sunset Impact needs more than a raw total

Applying version share to the active population converts a technical support decision into a customer migration cohort. For this page, the useful comparison is active users in sunset cohort, not whichever input happens to be largest. The Version Sunset Impact result answers the decision in the heading and should not be reused as a score for a different workflow.

The exact Version Sunset Impact formula

Affected active users equal monthly active users multiplied by the old-version share. The visible fields are Monthly active users and Share on versions to sunset. For Version Sunset Impact, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed active users in sunset cohort may be arithmetically valid but operationally meaningless.

Interpreting active users in sunset cohort

Segment by platform and critical workflow, prepare upgrade messaging and support, and monitor adoption before enforcing the cutoff. The ten-percent comparison is deliberately narrow: it tests the influence of monthly active 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 Version Sunset Impact supported the choice.

What this Version Sunset Impact model leaves out

This is a cohort count, not predicted churn; it excludes inactive installs, multi-device users, forced-update behavior and version telemetry error. That is where Version Sunset Impact stops being trustworthy. If an excluded factor could reverse active users in sunset cohort, 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 Version Sunset Impact is Apple Developer — App Analytics filters and dimensions. Apple Developer — App Analytics filters and dimensions supports the named definition or rule but does not supply private values for active users in sunset cohort. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.

Private, reproducible calculation

Version Sunset Impact runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Version Sunset Impact 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 Apple Developer — App Analytics filters and dimensions and rerun the saved Version Sunset Impact scenario.