You can use Filter and Condition Actions in your Automations to further tailor your workflows and customize your customer experience. This article will show you how you can use the Yes/No Split Conditioning Action in a workflow, as well as illustrate which scenarios would be best to use this feature.
How to Configure a Yes/No Split Conditioning Action
A Yes/No Split Condition is considered an Action; therefore this conditioning will take place at a given point in a workflow, when the customer passes through the Yes/No Split node in their defined Automator journey.
Once your Automation has been created, configuring a Yes/No Split into the workflow can be quite simple:
1. The Yes/No Split can be found in the Automator Actions menu on the lefthand side of the page, under the Filters and Flow section.
Drag this node onto your canvas, and define your Transition type, as you would with any other Action:
2. Once the node has been connected to existing workflow, click the Yes/No Split to prompt the configuration panel to slide out from the righthand side.
3. The Configuration panel is where you will be able to configure a number of conditions for this Yes/No Split. Any customers who reach this point in the workflow who DO meet all of these conditions, will be sent down the YES path. Any customers who reach this point in the workflow who DO NOT meet all of these conditions, will be sent down the NO path.
Select Action Type: This will determine which Action Type in your workflow this Condition Rule will apply to. In this use case, we have selected the Send Email Action Type.
Action Condition: This will determine what outcome from the selected Action your customers must meet in order to be sent down the YES path. In this use case, we have selected “Is Sent”.
Status: This will determine whether or not the above-defined rules must be met or not in order for the customer to be sent down the YES path. In this use case we have selected True.
In summary, the condition configured reads that:
If Email Send is Successful = TRUE,
then this customer must be sent down the YES path. Any failure to meet all of these criteria will result in the customer being sent down the NO path.
4. You can create more complex Conditioning Filters by adding additional condition rules to this action. This is done by selecting the + button.
This will create fields for you to add an additional rule. Only customers who meet all of the criteria, of all conditioning rules will be sent down the YES path. Customers who default on any of the criteria across any of the rules configured for this node, will be sent down the NO path.
Operator: The Operator selection allows you to select between an And/Or relationship between your existing conditions and this new, additional condition.
Remember to SAVE your Yes/No Split configuration before closing the Configuration panel.
What Happens After a Yes/No Split?
The Yes/No Split node essentially creates two paths in your workflow, and sends customers down either path based on whether or not they meet the criteria defined in the Yes/No Split Conditions. You can continue to attach Actions to each path of this node, to further build out your customer journey.
The customers who DO meet the criteria outlined in your Yes/No Split Conditions will be sent down the YES path, and will experience the Actions attached to the YES endpoint of this node. The customers who do NOT meet the criteria outlined in your Yes/No Split Conditions, will be sent down the NO path, and will experience the Actions attached to the NO endpoint of this node.