With conditional splits, you can create different Automation Workflow paths based on customer behavior, profile data, or message engagement. This lets you deliver personalized experiences by sending different messages to different contact groups within the same workflow.
In this article, you'll learn how to set up conditional splits, choose the right filter type, and avoid common setup errors.
Note: Split paths do not merge back into a single branch. If you want to send identical follow-up content to both groups, add the same steps (emails, delays) to each path.
When to Use Conditional Splits
Use splits to route contacts into different paths based on:
Trigger Filters – Event data at the moment the workflow triggers (order value, product purchased, cart value).
Contact Properties – Profile data (country, segment, tags, custom properties).
Message Engagement – Opens or clicks after sending a previous message in the workflow.
Alternative approaches:
Trigger Filters (in Trigger settings) – Filter who enters the workflow.
Audience Filters – Limit the entire workflow to a specific segment.
Conditional Splits – Filter which path contacts take after entering.
Setting Up Conditional Splits
Step 1: Add a Split Block
Drag and drop the Split Block to any point in your Automation Workflow.
After adding the split, you can move messages to either the Yes or No path by dragging them.
Important: Both Yes and No paths must have at least one step (email, delay, or action). If you leave a path empty, you'll see an error: "Cannot start workflow with empty paths." Add a delay block as a placeholder if you don't want to send anything on that path, or restructure your workflow using Trigger Filters instead.
Step 2: Choose a Rule
In the Split Block settings, select the condition to check:
Trigger Filters – Properties of the event that triggered the workflow.
Contact Properties – Profile data, tags, segments, or custom properties.
Message Engagement – Opens or clicks of a previous message.
If the rule is met, the contact goes to the Yes path. Otherwise, the contact goes to the No path.
Choosing the Right Filter
To identify the correct filter, check the last word in the filter string (e.g., "Collections", "Product", "Line"). The dropdown options belong to that category.
For example:
Order → Products → Collections → Title → This filter checks the Collection Title of the purchased product.
Combining Multiple Rules
You can add up to 5 rules to a single split and combine them with AND or OR operators.
💬 Check our blog article for more ideas on split block usage.
Trigger Filters
Use Trigger Filters to split based on event data at the moment the workflow triggers.
For example, you can send different Order Confirmation messages depending on the product collection purchased.
Important: Trigger Filters check event data at the moment the workflow triggers. You cannot split based on order tags or fulfillment status added after the trigger.
Just as with the trigger rule settings, the event specified in the split condition checks the order against its initial status. Therefore, it is not possible to split your automation based on the order tag, etc., unless the order had that tag/status when the workflow was triggered.
Contact Properties
Contact Properties split lets you split based on profile data, including segments, tags, country, and custom properties.
Example: Language Localization
You can check whether the contact is from Germany. If yes, send a message in German. Otherwise, send it in English.
Omnisend splits have two paths (Yes/No). To create three outcomes, nest splits on the No path.
Example: Route contacts based on three signup forms (Form A, Form B, Form C):
First split: Check if Country is Germany → Yes path sends Email A.
On the No path, add a second split: Check if Country is France → Yes path sends Email B.
The final No path sends Email C.
Using Custom Properties in Splits
If you created a custom form field (like a dropdown), you must:
Test the form at least once to populate the property in the system.
Scroll to the Custom Properties section at the bottom of the filter dropdown.
If it doesn't appear, wait 5–10 minutes and refresh the page.
Segment-Based Splits: Timing Requirements
Always add a 1–2 minute delay before any split based on segments, tags, or contact properties that rely on event data.
When a contact triggers an event (order placed, form submitted), the system processes the event in this order:
The event is passed to the system.
The Automation Workflow triggers.
The contact is added to the segment.
If you check segment membership immediately, the contact may not yet be in the segment. Add a 1–2 minute delay block before the split to ensure accurate routing.
This applies to:
Segment-based conditions (e.g., "First Order Customers")
Tag-based conditions (e.g., "VIP Tag")
Custom properties that update based on events
Message Engagement
Use Message Engagement splits to route contacts based on opens or clicks of a previous message in the workflow.
Critical: Add a 2–24 hour delay before splits that check message engagement. Without a delay, the split checks immediately after sending – before recipients have time to open or click.
Note: Unsubscribe and Preference Center link clicks do not count toward the click count. If a recipient clicks either of these links, they won't go to the Yes path when checking if the contact clicked "any link."
💬 For more ideas, check our blog article on message engagement splits.
Opened Email Filter
After you select the Opened Email rule, the dropdown shows email messages added to your workflow prior to the split. You can send different messages to contacts who opened the email or discontinue the sequence.
⚠️ iOS 15 Impact: Conditional split by opens was impacted by the iOS 15 Mail Privacy Protection update and is ineffective with subsequent iOS updates as well. Learn more.
Clicked Email Filter
Select the email message first, then define the link type:
Link Type | When to Use | How to Set Up |
is any | Check if the contact clicked any link | No additional setup required |
is predefined | Check if the contact clicked a specific link | Select the link from the dropdown |
is generated | Check if the contact clicked a unique link (e.g., abandoned cart, product recommendation) | Use "contains" or "starts with" + the static part of the URL (e.g., |
Clicked SMS Filter
The SMS click filter works the same way as the email filter. You need to choose the message and the link type.
Important: Enter the original link you added to the SMS content, not the shortened 0snd.com/a/XXXXX link generated by Omnisend.
Example:
You add
https://basic-piece.comto your SMS.Omnisend shortens it to
0snd.com/a/XXXXX.In the Split Block, enter
https://basic-piece.com.
For automatically generated links (e.g., abandoned cart), use the "contains" operator with the static part of the URL (e.g., contains "cart").
FAQ
Can I merge split paths back together into one workflow?
No. Omnisend splits cannot merge back into a single path. To send identical follow-up content to both groups, add the same steps (emails, delays) to both the Yes and No paths.
How do I split into three or more paths (e.g., three different forms)?
Omnisend splits have two paths (Yes/No). To create three outcomes, nest splits:
First split: Check if condition = Option A → Yes path for Option A.
On the No path, add a second split: Check if condition = Option B → Yes path for Option B.
The final No path handles Option C.
Will I see my abandoned checkout link in the list of predefined links?
No. Links that carry information personalized for each contact are not added to the predefined links menu. Instead, set the condition to: URL is generated → contains → "checkout".
Will the split adjust automatically if I change the links in the message after selecting them in the Split Block settings?
No. If you change the link in the message, you must update the Split Block settings manually to match the new link.
What is the limit of split blocks?
You can use up to 20 split blocks in one workflow.
Have any additional questions? Talk to us at [email protected] or via in-app chat.