Conditions

What this step does

A Condition step splits the flow into paths based on a rule, so contacts only see what applies to them.

How to use it (recommended)

Common condition types

• Tags (has/does not have)
• Lists (belongs to/does not belong to)
• Subscriber data (field values)
• Custom fields
• Email activity from flow or campaign sends
• Email preference by message category
• Quiz result from the completion that started the current flow

Tips

• Use all/any matching carefully when checking multiple tags or lists.
• For email activity, choose whether the condition should reference a campaign email or a flow email before selecting the message.
• Date-based custom fields compare by calendar date even when the saved value and condition value use different display formats, such as May 24, 2026 and 2026-05-24.
• Test both the Yes and No paths with known contacts before publishing.
• The plus buttons inside a path add a branch-specific step. The centered Add step after all branches button adds a shared continuation. An empty Yes or No path can still join that shared sequence.
• For quiz conditions, select the quiz first so the builder can show its saved results and questions. The condition reads the current flow run's completion, so a previous result or tag does not reroute a retake.
• Keep conditions simple and test each branch with one contact.
• When deleting a condition, choose whether to remove both branches or keep the Yes or No path. Keeping one branch preserves the selected branch steps and the following steps that sit after the condition.

If you want to compare two full paths, consider A/B Testing instead.