Several steps decide what happens to a record based on conditions — Filter keeps or drops, and Route chooses a branch. They all use the same condition editor, covered here.
Anatomy of a condition
Each condition has three parts:
Field — what to test. Type
@to pick a field produced by an earlier step, such as@Company sizeor a score from Segment & score. See Reference earlier steps with @-mentions.Operator — how to test it — equals, doesn't equal, greater than, contains, is set, and so on.
Value — what to compare against (not needed for operators like "is set").
Combining conditions
Add several conditions and combine them:
And — the record must meet every condition.
Or — the record needs to meet just one.
Tips
Filter first, spend later. Put a filter before expensive steps so you don't enrich or research records you'll drop.
Check "and" vs "or". It's the most common reason a condition matches too many or too few records.
Only test fields that exist. A condition can only read a field an earlier step actually produced — if it's empty for a record, the condition won't match. Add the step that produces it first.