Skip to main content

​
What is a Policy Group?

A Policy Group is the top-level container for a set of related business rules. Think of it like a Git repository — it holds multiple versions of your rules and manages their lifecycle. Each policy group has:
  • A unique name (e.g., tiered-discount, fraud-detection)
  • A priority that determines execution order when multiple groups apply
  • A status that controls whether the group accepts traffic

​
Group Status

StatusDescriptionTraffic
ACTIVENormal operation. Rules are evaluated.✅ Accepted
DISABLEDEmergency stop. All executions are blocked.❌ Rejected
ARCHIVEDPermanently removed from the system.❌ Rejected
Disabling a group immediately stops all traffic to it. Use this as an emergency kill switch when you need to halt rule execution without modifying rules.

​
Creating a Group

In the Console, navigate to Policies → New Policy Group and fill in:
  • Name: A descriptive, unique identifier
  • Description: What this group of rules does
  • Priority: Lower numbers = evaluated first (0 is highest)

​
Execution Mode

When multiple rules match within a group, the Execution Mode (activationMode) controls how many of them fire:
Mode (activationMode)Console LabelBehavior
NONEAllow All (Parallel)All matching rules execute (default)
EXCLUSIVESingle ExecutionOnly one winning rule executes
MAX_NTop N ExecutionUp to executionLimit rules execute
When using EXCLUSIVE or MAX_N mode, the Priority Strategy (activationStrategy) determines which rules win:
Strategy (activationStrategy)Behavior
FIRST_MATCHFirst matching rule in priority order wins
HIGHEST_PRIORITYRule with the lowest priority number wins
MAX_BENEFITRule producing the highest output value wins
Execution Mode applies at the group level — controlling competition between groups that share the same Execution Group (activationGroup). For rule-level conflict resolution within a single version, see Mutex Groups.

​
A/B Testing

Policy groups support A/B testing to compare two versions’ performance with live traffic. To start an A/B test, you need a currently deployed (live) version, a test version (must be ACTIVE/published), and a traffic percentage to route to the test version (1–99%). The remaining traffic continues to the live version. A/B tests produce execution logs for both versions, so you can compare their performance in the History tab.

​
Next Steps

Policy Versions

Learn how versions work inside a group.

A/B Testing

Set up traffic splitting between versions.