In this article, we concentrate on directing users along varied navigation paths based on their choices from a multi-selection table. In such a table, users can select multiple items from a list, allowing for diverse user interaction scenarios.
You can find screens with multiple selections here
You can find screens with multiple selections here
Table multiple selection
2-column multiple selection
Image title subtitle selection
When implementing conditions for table multiple selections, you have the option to use operators like "==", "!=", "in" and "contains". Each of these operators serves a distinct purpose in segmenting users based on their selections.
Let's consider designing an onboarding process for a Weight Loss app, where we aim to segment users according to their goals. We'll explore how this segmentation can be implemented effectively using conditions based on table multiple selections
Segment users depending on their exact selected choices.
If a user selects 'Weight Management' as their sole goal, they will be directed to way1. This pathway is specifically for users who choose only this option, without combining it with any other goals.
If a user selects both 'Healthy Eating Habits' and 'Overcoming Food Anxiety', they will be navigated to way2. This specific path is for users who show interest in both of these areas simultaneously.
For any other combination of choices that doesn’t exclusively include just 'Weight Management' or the combination of 'Healthy Eating Habits' and 'Overcoming Food Anxiety', users will be redirected to way3. This includes users who select any one of the other goals individually, any other combinations, or even none of the options.
To configure user navigation based on these specific selections, you will need to establish three distinct connections, two of them governed by a conditional statement using the "==" operator:
On your iOs and Web2App onboarding users will be segmented accordingly:
Segment users based on their unselected choices.
If a user selects any options except 'Weight Management', they will be directed to way1. This includes selections like "Healthy Eating Habits", "Overcoming Food Anxiety", "Body Positivity", any combination of these, selecting all items, or even selecting none. Essentially, as long as 'Weight Management' is not part of their selection, they proceed to way1.
In a scenario where a user selects 'Weight Management', they will be redirected to way2.
To tailor the user journey based on these specific selection criteria, you'll need to establish two distinct connections, one of which utilizes the "!=" operator to create a conditional pathway:
On your iOs and Web2App onboarding users will be segmented accordingly:
Segment users if they choose at least one item or combination from the list that you set.
If a user selects any combination that includes at least one of the following goals - "Weight Management", "Healthy Eating Habits", "Overcoming Food Anxiety" - they are directed to a specific user journey. This includes selecting just one of these options, any pair among them, or all three together.
If a user's selection does not fit within the specified list ("Weight Management", "Healthy Eating Habits", "Overcoming Food Anxiety"), they are directed to a different journey. This applies if they select all four options (including an additional option like "Body Positivity and Self-Love"), none of the items, or any combination that includes one of the goals plus "Body Positivity and Self-Love".
To configure this user journey based on these specific selection criteria, you will need to establish two distinct connections, one of which utilizes the "in" operator to create a conditional pathway:
On your iOs and Web2App onboarding users will be segmented accordingly:
Segment users to the specific screen if they select the combination that contains a specific item.
If a user selects any combination of items that includes 'Weight Management', they will be directed to way1. This rule applies whether they select 'Weight Management' alone, or in combination with other options like "Healthy Eating Habits", "Overcoming Food Anxiety", or even all available items. The key factor here is the inclusion of 'Weight Management' in their selection.
If a user selects any combination of items that do not include 'Weight Management', they will navigate to way2. This includes any selections made from the available options, as long as 'Weight Management' is not one of them.
To configure this user journey based on your specified selection criteria, you will need to set up two distinct navigation paths, utilizing the "contains" operator and "Weight management" item as condition values for conditional routing:
On your iOs and Web2App onboarding users will be segmented accordingly:
Applying Conditions in Later Screens
Instead of segmenting users immediately based on their initial selections, you can wait to segment them a few screens later. This delayed segmentation allows for more context and user interaction before funneling users into more specialized paths.
For instance, you can store their Goals selections (such as 'Weight Management', 'Healthy Eating Habits', etc.) and use this data for later segmentation.
Conditions can be set when you add the aforementioned screens in a sequence. For any transitions between these screens, you can specify corresponding Conditions to control the flow based on user actions or choices
Utilizing Multiple Conditions for a Single Transition:
It's possible to add multiple conditions to govern a single transition. These conditions work together in a way that's akin to an AND logical operator.
Imagine you set two conditions for this transition: Condition A could be goals.list = 'Weight Management' and Condition B could be goals.list == 'Healthy Eating Habits'.
The transition to the next screen (let's say, way1) will only occur if both these conditions are met. This means the user must select both 'Weight Management' and 'Healthy Eating Habits' from the list of goals.
Managing User Pathway for Non-Matching Selections:
When a user's choice does not align with any of your predetermined conditions, you can direct them along a default pathway that doesn't have specific conditions.
For example, let's say you have set up conditions for users who select both 'Weight Management' and 'Healthy Eating Habits'. Additionally, you have a separate transition path that doesn't have any conditions attached to it. So that way:
Users who select a combination that matches 'Weight Management' and 'Healthy Eating Habits' are directed to a specific pathway (let's call it pathway1) based on the conditions you've set.
On the other hand, users who make any other selection that doesn’t match this combination are automatically redirected to the alternative pathway (pathway2), which is the transition without specific conditions.
If a user's selection doesn't meet any of your established conditional pathways, the system should have a fallback mechanism. In such cases, the user should be redirected to the pathway defined by the first programmed condition. This approach ensures that every user follows a clear, predefined path, thus avoiding any potential confusion or dead ends in the navigation flow.
Suppose you have created two specific conditional pathways in your app. The first pathway (pathway1) is for users who select both 'Weight Management' and 'Healthy Eating Habits'. The second pathway (pathway2) is for users who choose both 'Overcoming Food Anxiety' and 'Body Positivity and Self-Love'.
Now, imagine a user making a selection that doesn't align with either of these two pathways (for expanse, they select "Weight management only". In this case, instead of leaving the user without direction, our system will automatically redirect them to the first conditional pathway that was created, which in our example, is pathway1.
Here is a comprehensive guide on how to add connections and integrate conditions into your onboarding process.