How to Use This Tool
Convert eligible users and rollout percentage into an exposure cohort with an exclusion allowance. A rollout percentage is ambiguous when targeting rules quietly shrink the actually eligible cohort.
Why Flag Rollout Size needs more than a raw total
Expose counts alongside percentages so support, observability and experiment power can be planned. For this page, the useful comparison is expected exposed users, not whichever input happens to be largest. The Flag Rollout Size result answers the decision in the heading and should not be reused as a score for a different workflow.
The exact Flag Rollout Size formula
Exposed users equal eligible users × rollout share × non-excluded share. The visible fields are Eligible users, Rollout percentage and Excluded or ineligible. For Flag Rollout Size, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed expected exposed users may be arithmetically valid but operationally meaningless.
Interpreting expected exposed users
Confirm the realized cohort in telemetry before advancing the flag stage. The ten-percent comparison is deliberately narrow: it tests the influence of eligible 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 Flag Rollout Size supported the choice.
What this Flag Rollout Size model leaves out
Sticky assignment, overlapping rules, bots and multi-device identity are excluded. That is where Flag Rollout Size stops being trustworthy. If an excluded factor could reverse expected exposed users, 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 Flag Rollout Size is OpenFeature — Specification. OpenFeature — Specification supports the named definition or rule but does not supply private values for expected exposed users. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.
Private, reproducible calculation
Flag Rollout Size runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Flag Rollout Size 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 OpenFeature — Specification and rerun the saved Flag Rollout Size scenario.
Sources & assumptions
Tool Spec v2 · verified 2026-08-20. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- OpenFeature — Specification (checked 2026-08-20)
Model assumptions
- Every input covers the same reporting period or cohort.
- Sticky assignment, overlapping rules, bots and multi-device identity are excluded.
- The calculator uses only the visible fields and does not fetch account data.
