When you choose to segment users in your onboarding process by adding conditions, the first step is to select the screen where the user's input will be used. Next, you must pick an operator and specify the user input that will define the segmentation rules. This methodical approach ensures that the segmentation reflects the user's interactions and preferences throughout the onboarding journey.
Here’s a comprehensive guide on how to go about this:
Selecting the Input Screen:
If you've already added the chosen screen to your onboarding sequence and wish to segment users based on this, look for the indicator or connection point (like an 'I' dot) where user segmentation can be set. For more details on this process, you can refer to a specific article.
Choose the screen from your onboarding sequence whose user input will be crucial for segmentation. This could be any screen where users make a selection or input data.
Initiating the Condition Addition:
Click on the "+ADD" button to start adding conditions. This will present a dropdown menu for screen selection.
Upon clicking this list, you'll see a list of screens that are eligible for segmentation.
Understanding Screen Structure in the List:
Each screen in the list is displayed as 'Screen Name' + 'Screen Type'.
The 'Screen Name' is set by default but can be changed to any name that suits your needs (instructions for changing screen names can be found in a related article).
'Screen Type' describes the nature of the screen (e.g., 'Picker' for screens with pickers, 'List' for tables, 'Field' for text fields, and 'Custom' for custom screens). Note that the screen type is not changeable.
Selecting an Operator Type:
The available operators depend on the screen type you've selected.
For instance:
Tables with multiple selections have operators like "==", "!=", "in", and "contains".
Tables with single selection offer "==", "!=", and "in".
Text fields and pickers include "==", "!=", ">", "<", ">=", and "<=".
Custom screens might have a combination of these operators.
Detailed information on using conditions for each screen type can be found in specific articles.
Understanding Operators:
Equality Check (==): Checks if the input matches the specified condition value.
Non-Equality Check (!=): Verifies if the input is different from the condition value.
Including (In): Checks if the input contains a specified substring or character sequence.
Greater Than (>) / Less Than (<): Compares if the numeric value is greater or lesser than the condition value.
Greater/Less Than or Equal To (>= / <=): Similar to the above but includes equality.
Contains: Checks if a user’s choice includes a particular item from a set.
Entering List Values:
Finally, specify the values that the user input should correspond to, exclude, or compare against to determine the segmentation path. This is particularly relevant for lists where you define the criteria for segmenting the users.
For instance, for tables with single and multiple selections, you may select options from the list that contains items from the table
For pickers, text fields, and custom screens you may enter values manually:
