Concepts
Rules and Evaluation Order
Build predictable targeting by understanding selectors, operators, rule priority, and how Zenmanage resolves the first match.
Selector types
Attribute
Matches context attributes such as plan, country, role, or device type.
Context
Matches the current context identifier and, when present, the context type.
Segment
Uses the same matching model as context selectors but represents a reusable audience definition.
| Operator | Meaning | Example |
|---|---|---|
| equals / not_equals | Exact string or identifier match. | plan equals enterprise |
| contains / not_contains | Substring check. | email contains @acme.com |
| in / not_in | Match against a list of values. | country in [US, CA, UK] |
| starts_with / ends_with | Prefix or suffix match. | user_id starts_with user- |
| gt / gte / lt / lte | Numeric comparison. | age gte 18 |
| regex | Regular-expression match for string values. | email regex /^.+@example\.com$/ |
| isnull | Match missing or null-like values where supported by the SDK. | middle_name isnull |
Evaluation precedence
Rules are evaluated in order. The first rule that matches wins. If no rules match, Zenmanage returns the target value for the flag or rollout branch being evaluated.
That means multiple rules behave like ordered alternatives: top-to-bottom priority with first-match semantics.
AND and OR composition
Within a single rule, all clauses must match. That is AND logic. Across multiple rules, each rule is a separate candidate and the first successful one wins. That is the practical equivalent of ordered OR logic.
Segments versus inline rules
Use segments when the same audience appears across many flags. Use inline rules when the logic is specific to one rollout. The tradeoff is reuse versus local clarity.
Next step
Take the next integration step in your own stack.
Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.