Guides and playbooks
Targeting Rules Deep Dive
Use rule ordering, selector choice, and reusable audience patterns intentionally so advanced rollouts stay predictable.
Build from narrow to broad
Put the most specific rule first, then add broader fallbacks beneath it. Because evaluation is first-match-wins, this keeps special cases from being accidentally swallowed by a broad rule near the top.
Choose the right selector
Use context or segment selectors for stable known identifiers. Use attribute selectors for properties such as plan, country, role, or organization tier that can change over time and should be modeled explicitly.
Example rule stack
- Rule 1: grant access to the internal QA segment.
- Rule 2: grant access to enterprise accounts in the US.
- Rule 3: serve the fallback target to everyone else.
Inside rule 2, the country and plan clauses use AND logic. Across the three rules, Zenmanage evaluates them top to bottom and stops on the first match.
Segment versus inline rule tradeoff
Use segments when the audience has a stable identity and appears in many flags. Use inline rules when the condition is short-lived, highly local, or only relevant to one experiment. If you expect a rollout to become institutional policy, move the audience definition into a segment early.
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.