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.

Add a Condition step where you need branching.

Choose the data you want to evaluate (tags, fields, activity, etc.).

Use two test contacts so you can see each branch run.

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.
Keep conditions simple and test each branch with one contact.

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