Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

Deviating from the Main Path with Splits

Objective

After completing this lesson, you will be able to add Splits steps to provide alternative paths for Smart Walk-Thru.

Deviating from the Main Path with Splits

Split Steps allow for variation in our guidance.

Watch the video to learn about deviating from the main path with Splits.

Key Takeaways
A Split will create a branch off the Main Path where we can create dedicated steps that will only show under certain circumstances. Using Splits allows us to make flexible guidance that can accommodate users to take different paths through a process.

Deviate from the Main Path using Splits

The Importance of Splits

Splits are a kind of Flow Step in Smart Walk-Thrus that allow us to build variations in your guidance. While the majority of users will follow the process laid out in the Main Path, some users will need to deviate. Anticipate these variations by adding Splits to allow the guidance to continue even if the user needs to take a different route.

The figure shows an example of a Split in a Smart Walk-Thru.

The image shows a flowchart with a decision point labeled Split? and paths for Yes leading to a Popup Step and No looping back.

Split From the Main Path

Splits can be added anywhere in a Smart Walk-Thru. Within the Main Path, in a branch, in a branch off a branch, etc. Splits are created with a condition in the Condition Builder. When the Smart Walk-Thru gets to the Split in the flow, it will check the condition.

If the condition is True, the guidance will branch off the Main Path. The branch can include any number of steps and then reconnect to the Main Path at any step (or not!). If False, the guidance will continue playing along the Main Path.

The figure shows Split from the Main Path.

The image shows the shopping cart page displaying a CatNip Fish Pouch, . The page includes sections to enter a promo code and add special instructions or requests.

Note

Additional fields appear on the Checkout page when users click on Enter a promo code or Add a note that require additional guidance.

Next, we'll go through a scenario on our Eddie's Depot platform. In this scenario, users are having confusion when asked to provide a note for their purchasing order. They don't know what they should write in this field and if it is even necessary for their order.

To resolve this confusion, we'll add a Split Step to a Smart Walk-Thru to provide specialized guidance for these confused users.

Exercise: Add Splits to your Smart Walk-Thru

Below is a software simulation that will guide you through how to add Splits to your Smart Walk-Thru. The simulation will replicate what you will experience when you build in your own Editor.

ExerciseStart Exercise

Best Practices for Split Steps

Splits can be built with any of the available Rule Types in the Condition Builder. A common Rule Types for creating Split conditions is Element On Screen. This may be used if we are checking to see if a certain checkbox is selected or if a certain tab is visible to the user in the navigation bar.

We want our conditions to be simple, as adding additional logic can be cumbersome to the building experience.

The figure shows the best practices for Split Steps.

The image shows a conditional interface showing the evaluation of whether a user opened notes, with a criteria that an on-screen element is visible.

Name the Split Step!

Make sure to change the name of the Split to a straightforward Yes or No question so that it is easy to tell what is happening in the Smart Walk-Thru flow.

The image shows a decision box in a flow-chart with an info symbol and text below asking, Did user open Notes?

Great job! Now that we've become more familiar with the Split Flow Step, let's look at our next Flow Step: Wait For Conditions

Log in to track your progress & complete quizzes