The True/False branch is the decision-making block in a workflow. It evaluates one or more conditions and splits the contact’s path into True or False based on whether the condition(s) are satisfied.
Conditions
You can set conditions on any contact field, variable, or event property.
- Equals / Not equals → check exact matches (e.g.
Plan = Enterprise).
- Contains / Does not contain → check for partial matches in text fields.
- Greater than / Less than → numerical comparisons (e.g.
Days since signup > 30).
- Is empty / Is not empty → catch missing or filled values (e.g.
Phone is empty).
- Date comparisons → before/after operators for timestamps.
Certain comparison operators only work with certain data types. For example, greater than / less than will only work with a # Number data type. Date comparisons only work with the Date data type.
Multiple conditions
- AND logic: all conditions must be true for the branch to resolve as True.
- OR logic: only one condition must be true for the branch to resolve as True.
- Nested logic: combine ANDs and ORs for more complex rules (e.g.
Plan = Enterprise AND (Region = US OR Region = UK)).
Flow behavior
- Contacts enter the block and are evaluated immediately.
- If conditions resolve True → the contact follows the True path.
- If conditions resolve False → the contact follows the False path.
- Conditions are evaluated based on the latest available contact data at that exact moment.
Data dependency: If a variable or field used in the condition does not exist for a contact, it is treated as empty. This often resolves to False unless the condition explicitly checks for empty values.Timing effects: If the branch comes immediately after a variable update or enrichment, ensure enough wait time if data may not be written yet.No fallback merge: A contact can only follow one path (True or False). If you want multi-branching with more than two outcomes, use multiple branches chained together.
Common Use Cases
- Personalization split: Enterprise customers get one sequence, SMBs another.
- Lifecycle gating: Only send the upsell email if
Last purchase date > 90 days.
- Deliverability control: Branch based on
Email engagement score > threshold.
- Regional compliance: Different sequences for EU vs. non-EU contacts.
Decision Logic Table
| Example condition(s) | Evaluation result | Path taken |
|---|
Plan = Enterprise | True | True branch |
Plan = SMB | False | False branch |
Region = US OR Region = UK | True | True branch |
Plan = Enterprise AND Region = EU (Plan = Enterprise, Region = EU) | False | False branch |
Phone is empty (Contact has no phone value) | True | True branch |
Phone is not empty (Contact has no phone value) | False | False branch |
