Targeted rollout

Also called: targeted release

Last updated:

A targeted rollout exposes a feature to a chosen audience selected by who users are — their plan, region, role, or membership of a segment — instead of to a random slice of the whole user base. Where a percentage rollout asks "what fraction of everyone?", a targeted rollout asks "which users?".

Targeted rollout vs percentage rollout

The two answer different questions and compose cleanly. A percentage rollout is random sampling across all traffic; a targeted rollout is deliberate selection by attribute. You combine them by targeting an audience and then rolling out to a percentage within it — "enable for 10% of EU enterprise accounts" — which is how most real releases are shaped: a canary aimed at internal staff first, then widened. The rollout strategies guide shows how the serving is configured.

When to use a targeted rollout

Reach for it when exposure should follow the user, not chance: shipping to beta opt-ins, enabling a feature only for the plan tier that paid for it (flag-based entitlement gating), dogfooding with internal accounts, or honouring data residency by region. Because membership is recomputed at each evaluation, users move in and out of the target automatically as their attributes change — no redeploy and no manual list-keeping.

Want the full picture? Read the concept guide: Rollout strategies →

Try it in your own app

Free Solo plan covers 10 flags and 2 environments. No credit card, no demo call — sign up and ship.