Survey Logic & Branching
Survey logic lets you control what respondents see and where they go next.
You can use logic to:
- Show or hide a question based on earlier answers
- Show or hide an entire section
- Show or hide individual options (or Rank Order / Group Ranking / Matrix items, Carousel items and options, or Swipe Cards) with the branch icon on that item — see Option Properties
- Send a respondent to a different question (Skip to question)
- Send a respondent to a different section (Skip to section)
- End the survey early (End survey)
How logic works in Quali-Fi
Logic is built from two parts:
- When conditions are met (rules based on earlier answers)
- Do this (show, hide, skip, or end)
In the builder, you’ll typically see logic written like:
"Result: Show this question when …"
or
"Result: Skip to question when …"
Add logic to a question (show / hide / skip / end)
Select the question
Click the question in the Survey Builder.
Open Display Logic
In the right-side properties panel, open Display Logic.
Turn it on
Enable Enable conditional display.
Choose what happens when conditions are met
Choose one of these actions:
- Show this question
- Hide this question
- Skip to question
- Skip to section
- End survey
Build your conditions
Use the condition builder to choose:
- A source (what you are checking)
- An operator (how to compare)
- A value (what it should match)
Save
Click Save (or Update) to activate the rule.
Condition sources (what you can base logic on)
When you add a condition, you can usually pick from:
- Earlier questions (the most common)
- Embedded data (fields defined in Tools → Embedded Data, with values passed through the survey link or defaults)
- Access ID data (on restricted surveys after you import Access ID metadata fields)
- Reference data (when a Reference Data binding is configured)
- Quotas (when quota cells are available)
Embedded data conditions
Choose Embedded data as the source, then pick the field key. Operators depend on the field type—numbers support greater/less than; strings support contains; Choice List fields use their configured choice values.
Embedded data is available in question logic, section logic, quota conditions, saved response filters, and conditional redirect rules on end screens.
See Embedded Data for how to define fields, pass values in links, and control reporting.
Access ID data conditions
On surveys set to Restricted (requires access ID) with imported metadata fields, choose Access ID data as the source, then pick the field (shown as aid. plus the key, for example aid.city). Operators follow the field type, same idea as embedded data.
Values come from the Access ID snapshot stored when the response started — not from later edits to the Access ID list, and not from URL query parameters. This is separate from embedded data (ed. / ED.). Generated codes with no metadata fields do not show this source.
Access ID data is available wherever other condition sources are (question and section logic, quotas, filters, end-screen redirects, and similar). For piping those same fields into question text, see Piping and Recall. For import and field flags, see Restricted Survey Access.
Yes/No conditions
Yes/No questions are first-class choice sources. The condition builder offers Yes and No — not option IDs.
Pick the Yes/No question, then equals / not equals with Yes or No. That is the value you should store and the value you will see when you reopen the rule.
The evaluator is forgiving on the response side (yes / true / 1 / y count as Yes; no / false / 0 / n count as No). You still write the rule as Yes or No.
If you built Yes/No logic before this update and a path looks wrong, open the rule and re-select Yes or No. Stale values that pointed at option IDs will not match.
Tip
If you’re trying to use a question in a condition but can’t find it, it usually means it comes after the question you’re editing. For show/hide display logic, your conditions must come from earlier questions.
Common actions explained
Show this question / Hide this question
This controls whether a question is visible.
Important behavior:
- If a question has one or more Show this question rules, it stays hidden unless at least one show rule is true.
- If a question has Hide this question rules, any matching hide rule will hide it.
Skip to question
Use this when you want to jump respondents to a specific later (or earlier) question.
In the logic action area you’ll choose:
- Jump to: the destination question
Note
Skip rules are evaluated as the respondent moves through the survey. You can use conditions based on earlier answers (and in some cases the current question).
Skip to section
Use this when the destination is a whole block, not one question. Same Display Logic card — pick Skip to section, then Jump to: the section title.
Respondents land on the first question in that section. The current section is not in the picker (you cannot skip a section to itself).
This is the cleaner path when you used to skip to “the first question of Demographics” and then someone reordered that section. Point at the section. The first question can move; the skip still holds.
End survey
Use this to stop the survey early (terminate / screen out, hit quota full, or mark a complete).
You’ll also choose what to Mark as:
- Screened Out — termination / DQ / disqualification
- Quota Full — over quota
- Complete — survey complete (including early complete)
Tip
If you want a custom thank-you or termination message at the end, configure your end screens in the Survey Builder (the logic rule controls when the survey ends; the end screen controls what respondents see). See End Survey Screens for titles, messages, icons, redirects, and preview.
Add logic to a section (show / hide a whole section)
Section logic lets you show/hide an entire section based on conditions.
Open the Sections sidebar.
Open Section Logic for the section you want to control.
Enable section logic, choose Show this section or Hide this section, then build conditions.
Click Save.
Using ALL vs ANY (AND vs OR)
When you add more than one condition, you’ll choose how they combine:
- ALL means every condition must be true
- ANY means at least one condition must be true
If you need parentheses-style logic, you can use Add group (parentheses) to build a nested group.
Number selected (Multiple Choice and multi-select Autosuggest)
When the source question is Multiple Choice, or Autosuggest with Selection mode → Multiple, the condition builder also offers number selected operators. Use these when the count of picks matters more than which labels were chosen.
| Operator | Meaning |
|---|---|
| number selected equals | Exactly N options selected |
| number selected does not equal | Not exactly N |
| number selected is greater than | More than N |
| number selected is less than | Fewer than N |
| number selected is at least | N or more |
| number selected is at most | N or fewer |
| number selected is between | Inclusive range (min and max) |
Unanswered counts as 0. Example: show a follow-up when someone picks at least three brands, or skip ahead when they pick none.
For the same idea in Script Mode (Q1 count < 3, Q1 count between 1..3), see Survey Script Mode.
Rank Order and Group Ranking conditions
You can base display logic, skip logic, end-survey rules, and custom trigger conditions on how respondents ranked items in a Rank Order or Group Ranking question.
When the source question is a ranking question, the condition builder shows ranking operators and lets you pick an item plus a position (or top/bottom N):
| Operator | Meaning |
|---|---|
| is ranked | The item is in that exact rank position (1 = top) |
| is not ranked | The item is not in that position (also true if the item was never ranked) |
| is ranked in top | The item's position is at or above N (for example, top 3) |
| is ranked in bottom | The item is among the last N ranked items |
Example: show a follow-up question when "Price" is ranked 1st on your Rank Order question.
For Group Ranking, Quali-Fi flattens groups in group priority order (the same overall order used for piping), and items left unassigned are not part of the ranking.
If you used Max items to rank on Rank Order, only the ranked subset has positions; an item the respondent never ranked will not match is ranked / is ranked in top / is ranked in bottom.
Open-end exclusive options
Short Text and Long Text can include up to 10 exclusive options. You add them on the canvas with Add exclusive option and you write each label. A typical one is “None of the above” or “Not applicable.” Selecting one clears the text fields.
In the condition builder, pick the text question and use equals or does not equal. The value list shows those labels. Custom text… is there when you want to match what someone typed instead. The same equals / does not equal match works in quotas, triggers, end screens, and saved filters.
Selecting an exclusive option also unlocks navigation when AI probing would otherwise hold Next on a Long Text question.
Carousel item and option visibility
On a Carousel question, the branch icon works on items (each statement in the sequence) and on options (the scale or choices shown for each item). Hover the item or option and set show-when logic.
If the Carousel is required, only visible items must be answered, and only with currently visible options.
Common logic patterns (examples)
Screen out non-qualified respondents
- Action: End survey
- Mark as: Screened Out
Example:
If Do you live in the United States? (Yes/No) equals No then end the survey.
Show a follow-up question
- Action: Show this question
Example:
If How satisfied are you? is less than or equal to 2 then show What disappointed you?
Skip over a section of questions
- Action: Skip to section (or Skip to question if you truly need a specific item)
Example:
If Have you used this product? equals No then skip to the Reasons section.
Branch on a top ranking
- Action: Show this question
Example:
If Rank these features is ranked in top 3 for "Same-day delivery" then show Tell us more about delivery expectations.
Survey health checks
Logic rules feed directly into Survey health in the builder top bar. Broken skips, stale targets, circular paths, and incomplete conditions appear under the Logic group alongside completion-time and design suggestions.
For the full guide — where to find the control, what each group checks, severity levels, dismiss behavior, and package access — see Survey Health.
Testing Your Logic
Warning
Always test complex logic thoroughly before launching. Logic errors can corrupt your data or frustrate respondents.
Preview
Use Preview to test your logic before launching:
- Go through the survey as a respondent
- Test every path (different answers)
- Confirm that questions/sections show or hide when expected
- Confirm skip destinations land on the right question — or the first question of the right section
Tip
When testing logic with a team, use Survey Team Collaboration to flag logic issues on specific questions during test mode and track them in the Feedback Inbox.
Best Practices
Keep It Simple
- Start with essential logic only
- Add complexity gradually
- Document why each condition exists
Plan Before Building
- Map out logic paths on paper first
- Identify all segments and their paths
- List all conditional questions
Test Every Path
- Create a test plan covering all paths
- Record expected behavior
- Test edge cases
Use Clear Naming
Name your variables and logic descriptively:
Good: Show_FollowUp_NPS_Detractor
Bad: Logic_1 or Condition_A
Troubleshooting
Question Not Appearing
- Check display logic conditions
- Verify source question has a response
- Look for conflicting conditions
Skipping to Wrong Place
- Verify skip logic destination
- Check for multiple skip conditions
- Ensure page breaks aren't interfering
Next Steps
Now that you understand logic:
- End Survey Screens - Customize what respondents see when the survey ends
- Embedded Data - Pass metadata through links and use it in conditions
- Yes/No - Binary questions with Yes / No condition values
- Restricted Survey Access - Import Access ID fields and use Access ID data in conditions
- Option Properties - Per-option hide and visibility logic
- Rank Order / Group Ranking - Rank items, then use ranking operators in conditions
- Quota Management - Limit completes by segment (including
aid.bulk syntax) - Carousel - Item and option show-when logic
- Creating Surveys - Apply logic to your surveys
- Distributing Surveys - Share your dynamic survey
- Survey Analytics - Analyze responses by segment