Currently only "Contact Field Is Not __" is possible for enrollment criteria. I'm surprised there is only one option. I can't use this feature without the other option.
Â
Ideally, "Contact Field Contains __" would be useful in many cases too, but at the bare minimum an exact match shouldn't be hard to add.
Hi everyone,
Thank you for your ongoing, detailed feedback! We completely agree that robust branching logic is what turns a basic email sequence into a powerful, personalized customer journey.
We have some great news! Since this thread was originally posted, we launched our modern Automation Path Builder, which officially delivers the vast majority of the branching conditions requested in the comments!
When building an active path, you can drag a Conditional Split step into your workflow to automatically send contacts down a "Yes" or "No" path based on their real-time data. You can now split based on:
List Membership: (e.g., If a prospect makes a purchase, you can use a split to check if they are on the "Customer" list. If Yes, they are routed away from the sales pitch emails!)
Custom Fields: (e.g., If Custom Field "VIP" is exactly "YES")
Email Engagement: (e.g., Did they open or click the previous email?)
Tags and E-commerce Activity
You no longer have to manually download and cross-reference spreadsheets to move contacts between lists—the Conditional Split step handles that routing for you automatically!
Join us to learn about successful email lists, from onboarding to database maintenance. May 28, 2026 - 2:00 pm ET
