Conditional logic

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 add Conditions:

1. Open your draft maze, or create a new one. Build all the blocks that will be a part of the conditional path.
2. Navigate to the block which will conditionally route to other blocks.
3. Activate the Conditions toggle at the bottom.
   
4. Specify the criteria that you want to use to trigger your 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. Learn more in the section below: 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 the questions that are not relevant to that path are correctly skipped in the logic. Learn more in the section below: Add "Always" conditions in complex branching
5. You can optionally click Add Condition if you want to specify other criteria that will route to either the same block or a different block, allowing for complex routing.
   If you want to remove any additional Conditions you added, click the trash icon.
   
6. You also have the option with the Otherwise condition to trigger 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 are not 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:

1. Open the destination block.
2. Enable conditions on that block.
3. Delete the condition that has been automatically added.
4. This will leave an "Always" condition that will be applied no matter what.
5. 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 mission block are clear, and follow up in case they found something confusing. Here's how you could apply conditional logic:

1. After the mission block, you add an opinion scale block where you ask "Were the screens clear?" and respondents can rate from 1 (Confusing) to 10 (Super Clear).
2. If users responded with a score of 10 (Super Clear), you can route them directly to the thank you screen.
3. Users who gave a lower score can be routed to an open question block (or any other type of block). This gives you the opportunity to ask them to elaborate on what was confusing.
4. You might even route these dissatisfied users to another Mission block with an alternate workflow, 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, how Conditions will vary slightly between types of blocks. 

Mission

Your Conditions in this block can act based on any of the following tester behaviors:

• Gave up
• Succeeded directly
• Succeeded indirectly
• Took a specific path
• Misclicked

Yes/No

You can direct the tester to the next block or a specific block, depending on the specific answer they provide.

Opinion Scale

You can choose 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 tester scores between 1-3 you can set the resulting condition to route them to one particular block, while any testers between 4-6 can be routed to a different block, and so on.

Multiple Choice

You can direct the tester to the next block or a specific block, depending on the specific answer they provide.

Open Question

You can set up the condition to look for specific text within the respondent'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 cannot 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.

Context Screen, Tree Test, Card Sort, 5-Second Test, and Legal Screen

If you set up conditional logic, these blocks will only route testers 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!