This feature allows you to direct users down different paths based on how they answer previous questions, ensuring a tailored and relevant experience every time. Imagine guiding a user through a tailored pathway based on their favorite color and shoe size, while also excluding those interested in basketball shoes. You’ll be crafting rules using responses collected across three different screens within the same user session, ensuring a seamless and intuitive experience for your users.
Before you begin
Confirm your experience includes multiple screens to branch from.
Ensure you've planned the logic for each path based on user responses.
Understand how branching logic works across different question types.
Add rules based branching
You can insert a traffic split from either the builder map or the screen cards within the editor.
Insert from builder map:
Select the three-dot dropdown on a screen.
Choose to insert a Traffic Split in front of all your branches.
Insert within a branch:
Click into a specific screen branch.
Open the Traffic Split modal.
Select Rule Based as your split type. Within the Traffic Split modal, you will notice "Rules Based" as the top choice.
Refer to the Traffic split overview article here for more information.
Set up a rule
After selecting Rule Based, choose the screen(s) to build your rule from.
Only screens within the current path that support branching will be available.Choose your criteria:
Any: The rule is met if any of the selected responses are chosen (logical OR).
None: The rule is met if none of the selected responses are chosen (exclusion logic).
(Optional) Name each branch to clearly identify the logic it uses.
If a user doesn’t meet any rules, they’ll default to the fallback path.
Tip: You can name your branches at the top of each branch for better recognition of what rule is behind each branch. If the rule is met by the end user, they will be routed down the pathway you set up. If a rule is not met, they will branch to the ‘default’ path.
Advanced rules across screens
You can:
Combine rules across multiple screens using AND or OR
Add multiple conditions within a single screen
Prioritize rules using drag-and-drop if multiple branches could apply
Note: If there is a tie between branches, you can stack rank which one gets priority by dragging and dropping the order.
Create Rules with Select All That Apply (SATA)
If you are using a Select All That Apply question type, there are some additional rule options available using the operators.
Any will be used if one or more of the items is selected by the user
All will be used if all the items are selected. This selection will provide an exact match.
Create rules with the Stack Rank element
The Stack Rank question type has some similarities with Select All That Apply. Here’s how the 3 operators work:
Any: If you select ‘Any’, you will set the ranking for the branch. If the end user selects any of the items you ranked the same way you did, they will meet that condition and go down that route.
All: Similar to ‘All’ for Select All That Apply, you will set up your ranking for a branch, and if the end users selects all of them right, they will go down that route.
Order: The ‘Order’ operator is used to apply logic to ensure that certain selections are ranked above others. For example, if a certain pathway always needs ‘Apples’ ranked higher than ‘oranges’ and ‘pairs’ you can set the Order for Apples to be ranked 1 and set oranges and pairs to 2 and 3.
Tip: Stack Rank is a screen type where you may want to consider setting up numerous rules for a pathway to get the proper granularity.
Create a rule with a Slider element
If your screen has a Slider, there are 3 operators you can use to set up your rule.
Above: If the end user selects a value above a certain number
Equal: if the end user selects a specific number
Below: If the end user selects a value below a certain number
Next steps
Finalize your rules and test each path using the preview feature
Consider using Dynamic Product Feed if your experience involves many product-specific outcomes
FAQ
Is there a limit on the number of rules you can create?
There is no limit. However, if your builder map has too many branches, the building experience can get a bit unwieldy. Ultimately Rules based branching should cut down on how many screens you need to personalize your content, not increase the number of screens.
Can you use rules based branching to create segment based outcomes?
Segment Based Outcomes is what is described to create an exact set of rules to achieve an outcome at the end of your experience. While you can technically achieve this with Rules Based branching, it is not a super scalable way to accomplish it if you have many outcomes. The Dynamic product Feed may be a better choice if you have many product or outcome, and you’d like to achieve this use case.