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
When to use a targeted rollout
Want the full picture? Read the concept guide: Rollout strategies →
Related terms
Percentage rollout
A percentage rollout serves a feature to a defined share of users — chosen by a deterministic hash — so the same users stay in the cohort as you ramp the percentage up.
Segment targeting
Segment targeting serves a flag variation to a named, reusable group of users defined by shared attributes — like "beta users" or "EU customers" — instead of listing individuals one by one.
Canary release
A canary release exposes a new version to a small group of users first and watches its metrics before rolling it out to everyone — so problems surface on a fraction of traffic instead of the whole fleet.
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.