Visibility rules

A visibility rule decides whether a respondent ever sees a field. Use it for follow-up questions, branch-specific sections and pages that only some respondents need.

Build a rule

Select a field and open Visibility in the inspector.

1. Choose whether the rule requires all or any of its condition rows to match.
2. Each numbered row picks a Field, an Operator, and a Value.
3. Add or remove rows as needed. The field stays hidden from respondents until its rule is satisfied.

Operators: equals, does not equal, contains, greater than, at least, less than, at most, is blank, is not blank.

Values offer real choices rather than free text wherever the product knows them. Checkbox fields offer Checked and Unchecked; Picklist and Radio fields offer that field’s own options.

Under the conditions, the rule reads back in plain English: Shown when Multi-Select 1 contains “sports”. An Advanced toggle reveals the raw expression when you want it.

The same condition builder is available on a Section marker, which hides everything inside it, and on a page, which makes the respondent skip the page entirely. See Pages.

Three behaviours worth knowing

• “Is blank” means blank. An input typed into and then cleared, a whitespace-only answer, and an empty multi-select all count as blank.
• Rules that depend on each other settle correctly. A hidden question’s answer reads as blank to any rule that references it, so a follow-up question hides the moment the answer above it changes. What you see is what is reviewed, validated, and saved.
• Answers a respondent could not see never reach your records. They are stripped in the browser and again on the server, including per-row fields inside repeating groups. Hidden fields you set up deliberately, such as a Hidden Field carrying a campaign ID, still submit.

Before publishing, check the whole form’s logic at once in the Logic Map.