Conditions are a way to apply logical routes to blocks based on actions taken during the test.
Based on the outcome of a mission, or on the answer a tester gives you, you can direct them to different blocks. This lets you ask clarifying questions or get targeted feedback only when necessary to help reduce the length of your test.
In this article:
- Who can use conditions?
- Apply conditional logic to your mazes
- Add "Always" conditions in complex branching
- Example
- What are the options for each block?
Who can use this feature?
The ability to add conditions is exclusive to paid plans.
Apply conditional logic to your mazes
To enable conditions:
- Open Build mode and set up all the blocks that’ll be a part of the conditional path.
- Select the block that’ll conditionally route to other blocks. Enable the Conditions toggle at the bottom.
- Specify the criteria to trigger conditional routing, and what to do if the condition has been met. Only some block types support custom conditions; others allow only for skipping to the next block or a specific one further down the maze. What are the options for each block?
Be sure to add an Always condition to the subsequent blocks that you’re using as a follow-up to your conditions. This ensures that questions that aren’t relevant to that path are correctly skipped in the logic. Learn more in the section below: Add “Always” conditions in complex branching
- If needed, you can click Add Condition to specify additional conditional criteria, allowing for complex routing.
- The Otherwise condition triggers a fallback action, should the tester not trigger any of the conditions you’ve set.
Add “Always” conditions in complex branching
When working with branching paths, use an “Always” condition to make sure that users are always routed to a specific block (while skipping the blocks that aren’t relevant for that path).
You can use this method to ensure that someone who sees that block is taken to the next block in the flow that you want them to see, rather than the next block consecutively. This will ensure testers won’t see blocks that belong to other paths in the logic.
Here’s how you do it:
- Open the destination block.
- Enable conditions on that block.
- Delete any conditions that have been automatically added.
- This will leave an Always condition that’ll be applied no matter what.
- Select Jump to a specific block to choose which block those users should be routed to.
Example
Suppose you want to find out if users think the screens in a prototype are clear, and follow up in case they find something confusing.
Here’s how you could apply conditional logic:
- After the prototype block, you add an Opinion Scale block where you ask “Were the screens clear?” which respondents can rate from 1 (Very confusing) to 10 (Very clear).
- If participants respond with a score of 10 (Very clear), you can route them directly to the end screen.
- Participants who gave a lower score can be routed to an Open Question block (or any other type of block). This is a chance to ask them to elaborate on their feedback.
- You might even route these dissatisfied users to a different prototype block, if you want to get their feedback about a different approach.
What are the options for each block?
Conditions are available for all block types with the same core option to route testers either to the next block, or to a specific block later in the maze.
That said, depending on the type of block, there are different options for conditional logic.
Prototype test
You can set IF conditions based on any of the following behaviors:
- Didn’t succeed: The participant didn’t reach the last screen of any of the paths you’ve set.
- Succeeded directly: The participant completed the task via an expected path.
- Succeeded indirectly: The participant completed the task via an unexpected path, but still reached the final screen.
- Took a specific path
- Misclicked: During the test, the participant clicked/tapped outside a clickable area (i.e. hotspot). In a live product, a misclick would have taken the user to an “incorrect” page.
You can also set an ALWAYS condition to direct participants to the next block or a specific block, depending on the specific answer they provide.
Learn more about setting up prototype tests
Website test
Because paths are optional in website tests, it's not possible to define conditions based on mission outcomes.
In website tests, it's only possible to use ALWAYS conditions to direct participants to the next block or a specific block.
Learn more about setting up live website tests
Yes/No
You can set IF conditions to direct participants to the next block or a specific block, depending on the specific answer they provide.
You can also set an ALWAYS condition to direct participants to the next block or a specific block.
Opinion Scale
You can set IF conditions for any range of your choosing within the scale.
For example, for a scale with 10 steps, you can choose a condition for any range between 1-10. If a participant scores between 1-3, you can send them to a specific block. Any participants who chose between 4-6 can be sent to another block, and so on.
You can also set an ALWAYS condition to direct participants to the next block or a specific block.
Multiple Choice
You can direct the tester to the next block or a specific block, depending on the specific answer they provide.
You can also set an ALWAYS condition to direct participants to the next block or a specific block.
Open Question
You can set IF conditions to look for specific text within the participant’s answer:
- Contains: This condition will be satisfied if the specific text is found anywhere in the answer.
- Is exactly: This condition will only be satisfied if the entire answer matches exactly what’s specified.
- Does not contain: This condition will only be satisfied if the specific text can’t be found anywhere in the answer.
If the condition is met, then you can direct the tester to the next block or a specific block.
You can also set an ALWAYS condition to direct participants to the next block or a specific block.
Context Screen, Tree Test, Card Sort, 5-Second Test, and Legal Screen
These blocks only support ALWAYS conditions to route participants to the next block or to a specific block.
Still need help?
If you have any questions or concerns, please let our Support team know — we'll be happy to help!