Conditions are built with the same interface everywhere in Exoid: on blocks, in the results filters and in quotas. Once you’ve learned it in one place, you know it in all three.
Visibility condition
The button on the block is labelled Skip condition, but the modal it opens is titled Visibility condition — “Show this question when the condition is met”. At the top there is a Show / Skip selector, and it changes what the condition does:- Show — the question appears only if the condition is true. Everyone else never sees it.
- Skip — the question is skipped when the condition is true, and shown to everyone else.
The elements of a condition
Every condition is made of three parts.required
The question whose answer the condition evaluates. You pick it by question code.
required
The type of comparison to apply to that answer.
required
The value to check for the condition to be true.
Stacking conditions and groups
One condition is often not enough. You can add more of them, joined by an operator.
You can also nest groups: a group is a set of conditions evaluated together, which then counts as a single condition inside the level above it. That’s how you write things like “(region is North OR region is Centre) AND age is over 35” without splitting the question in two.
Navigation rules
Navigation rules are the branching feature. They open from the block into a modal titled Edit logic for <question code>, and they say where the respondent goes once they’ve answered this block. The modal offers two shapes.1
Always go to
A single row: whatever the respondent answers, they go to the destination you pick. Use it to jump over a section or to send everyone to a specific ending screen.
2
A list of rules
Rows in the form
if <question> is <value> → <destination>. Each row sends a different answer to a different place.3
All other cases go to
The last row closes the list: it catches everyone that no rule above matched. Set it deliberately — it’s the default path of the block.
The order of the rules matters
Rules are evaluated from top to bottom and the first one that matches wins. The rules below it are never considered, even if they would also match. You reorder the rules by dragging them. Put the most specific rule at the top and the broadest at the bottom: a wide rule sitting first will swallow all the traffic that should have gone to the ones after it.Which one do you need
The question shouldn't be asked
Use a visibility condition. The respondent skips over the block and carries on in the normal flow.
The path has to change
Use a navigation rule. The respondent answers, and the answer decides which block comes next.
Next steps
Context variables
Store values from the URL or from an answer and reuse them across the interview.
Scripts
Run JavaScript on a block to set a variable from the answers already collected.
Block options
The question code every condition and rule refers to, plus the settings shared by all blocks.
Quotas
The same condition builder, used to cap how many people of a given profile can complete.