Conditions
Route viewers through Flow Map branches based on data and date rules
Conditions send viewers to different paths based on data or time. Use them when a project needs to choose the next scene or lineup from a rule instead of sending every viewer through the same route.

Condition branches are evaluated in order. The first branch that matches determines the next path. If no branch matches, the fallback branch is used.
Common Condition Patterns
Personalize by customer type
customer_type is VIP
VIP viewers see a premium offer. Everyone else follows the fallback path.
Route by count
reorder_count is 1
First-time reorder viewers see the first-time routine scene.
Route by score or value
loyalty_points is greater than 500
High-value viewers see a reward scene.
Show date-based content
date is between June 1 and June 30
Viewers see a limited-time campaign scene during the selected date range.
Check whether data exists
first_name exists
Viewers with usable data see personalized copy; others see generic copy.
Create or Edit a Condition
To edit a condition, select the condition node, then choose Edit from the node menu.

The condition editor shows the selected node beside the editable rules, so you can keep the branch context visible while changing logic.

To add another branch rule, select + Add condition. The new rule appears as an incomplete Else if branch until a field, operator, and value are selected.

For example, to route viewers who purchased more than 30 days ago:
Select the Data condition type.
Choose
days_since_purchaseas the data key.Choose Is greater than as the operator.
Enter
30as the value.Save the condition only after the branch name and connector are ready.

Test Condition Branches
Preview every branch with representative data before publishing. Include edge cases such as missing values, unexpected values, date boundaries, and viewers who should fall through to Otherwise.
Last updated

