Logic & jumps
Not every respondent needs to see every question. With jumps you can branch your survey: send someone from one question to a later one based on how they answered, so you can skip irrelevant sections or route different people down different paths — for example, sending detractors somewhere other than promoters.
This page explains how jumps work, the conditions you can build them from, and the visual flow view that shows it all at a glance.
How a jump works
A jump starts at a question and sends the respondent to a later question once they answer it. A jump carries a target (where the respondent lands) and a set of conditions that decide whether it fires. A few rules keep things predictable:
- A jump always goes forward to a later question — you can't jump backwards. The list of possible targets only includes questions that come after the starting one.
- A jump can have one or more conditions, and all of them must be true for the jump to fire. Conditions always combine with AND.
- To express "OR", create separate jumps from the same question — whichever one's conditions are met will fire.
- A jump with no conditions is a direct jump: it's always taken once the question is answered. This is the way to unconditionally route everyone past a section.
Which questions can start a jump
Any enabled question except Open text can start a jump. Open-text answers have no comparable value to test against, so they can't originate a jump (they can still be a target). Questions that come from a shared template are locked and can't have jumps added to them. See Question types.
Condition comparisons
Each condition compares the respondent's answer against a value you choose. There are thirteen comparisons available:
- Equals / Does not equal — the answer matches (or doesn't match) the value exactly.
- Is empty / Is not empty — there is no answer / there is some answer. These two take no value.
- Greater than / Greater than or equal — for numeric scale answers above (or at-and-above) a threshold.
- Less than / Less than or equal — for numeric scale answers below (or at-and-below) a threshold.
- Contains / Does not contain — the answer includes (or doesn't include) the text you enter.
- Matches a pattern — the answer matches a pattern you supply (a regular expression), for advanced text matching.
- List contains / List does not contain — for multi-answer questions where the answer is a list, test whether a particular value is among the chosen options.
The Is empty and Is not empty comparisons need no value. Every other comparison takes a value you enter. For selection questions, the value you compare against is the option's underlying value, shown alongside its label so you can pick the right one.
Adding a jump
Pick the starting question
Open the question where the branch should begin — any enabled type except Open text.
Choose the destination
Set a later question as the target the respondent jumps to. Only questions that come after the starting one are offered.
Add conditions
Add one or more conditions using the comparisons above. Each condition needs a comparison, and most need a value (the two "empty" comparisons don't). Remember every condition must be true for the jump to fire.
Repeat for other paths
Need an "OR", or a different route for a different answer? Add another jump from the same question with its own conditions.
Leave no conditions for a direct jump
A jump with zero conditions always fires once the question is answered. If you meant the jump to be conditional, make sure you've added at least one condition — otherwise everyone takes it.
The flow view
A visual flow view lays your questions out top to bottom and draws the jump connections between them as curved arrows, so you can see at a glance how respondents move through the survey and where each branch leads. Selecting a jump highlights its connection.
A toggle lets you show or hide disabled questions while you review the paths. Even when you hide them, a disabled question that is a jump target still appears, so the picture of where each branch lands stays complete and accurate.
Route detractors and promoters
A common pattern is one jump for low scores and another for high scores from the same question — for example sending unhappy respondents to a follow-up about what went wrong, and happy ones to a referral ask. The results still flow into Insights so you can analyze each path separately.