Feature
Targeting rules
Ordered rules on context attributes. The first enabled rule that matches decides the value.
A rule is a list of conditions combined with all (AND) or any (OR), and what to serve when they match: a fixed variation or a weighted rollout. Rules are evaluated in order and the first match wins.
Conditions compare a context attribute (user key, email, organization id, plan, country, app version, or any custom attribute, including dot paths such as custom.tier) using one of fourteen operators, segment membership included.
A missing attribute never matches, not even a negated condition, so an unknown user cannot slip through “does not equal”. A rule with no conditions never matches.
More features
All features →- 01
Organizations, projects and environments
Tenants, the products inside them, and the stages each product ships through, each configured on its own.
- 02
Flag types and variations
Boolean, string, number and JSON flags, each with a list of variations to serve.
- 03
Individual overrides
Pin a specific user or a whole organization to a variation, ahead of every targeting rule.