Learn how branches, filters, and decisions route contacts through a campaign.
Key concepts
- Branches route contacts according to profile data, group context, prior behavior, event data, timing, or calculated conditions.
- Ordered decisions must define what happens when multiple conditions match.
- A default route prevents records from becoming unintentionally stranded.
How it works
- Express each decision in business language before configuring it.
- Use reusable filters or rules where the same definition appears elsewhere.
- Order mutually exclusive or priority-based branches explicitly.
- Add a fallback route and define behavior for missing or invalid data.
- Test one profile for every branch and boundary condition.
Governance and considerations
- Time-relative and behavior-based conditions can change between evaluations.
- Complex nested branches are harder to operate than several clear stages.
- Record why a high-impact decision uses particular data and thresholds.
Note
Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.