Conditional Logic

Conditional logic makes your forms dynamic — show or hide fields, skip sections, and route respondents down different paths based on their answers.

Field Visibility Rules

Control whether a field is visible based on the value of another field.

Adding a Visibility Rule

1. Select a field in the builder.
2. Open the Logic tab in the settings panel.
3. Click Add Condition.
4. Configure the rule:
5. When — select the field to watch
6. Operator — choose the comparison
7. Value — the value to compare against

Available Operators

Operator	Description	Example
equals	Exact match	"Country equals United Kingdom"
not_equals	Does not match	"Role not equals Student"
contains	Text includes value	"Comments contains urgent"
not_contains	Text does not include	"Email not contains test"
greater_than	Numeric comparison	"Age greater than 18"
less_than	Numeric comparison	"Budget less than 1000"
is_empty	Field has no value	"Phone is empty"
is_not_empty	Field has a value	"Email is not empty"
is_one_of	Matches any in a list	"Country is one of UK, US, CA"
is_not_one_of	Does not match any in list	"Status is not one of Closed, Archived"

Combining Conditions

Use AND / OR combinators to build complex rules:

• AND — all conditions must be true
• OR — at least one condition must be true

Example: Show a "Dietary Requirements" field when: - "Attending dinner" equals "Yes" AND "Meal preference" is not empty

Section Routing

For multi-section forms, route respondents to different sections based on their answers.

How Section Routing Works

1. Select a section in the builder.
2. Open the Routing tab.
3. Add routing rules that determine which section comes next.

Example: A survey with three sections — General, Technical, and Non-Technical: - After the General section: - If "Role" equals "Developer" → go to Technical - If "Role" equals "Designer" → go to Non-Technical - Default → go to Technical

Default Routes

Every section has a default "next section" that applies when no routing conditions match. By default, sections flow in order (Section 1 → Section 2 → Section 3).

End Screens

Create custom end screens for different paths through your form.

• Title — custom heading (e.g., "Application Received!")
• Message — custom body text
• Redirect URL — optional redirect after submission

This lets you show different thank-you messages depending on which path a respondent took.

Conditional Logic in the Flow View

Switch to Flow View in the builder to see a visual diagram of your form's logic:

• Sections appear as nodes
• Routing rules appear as connecting arrows
• Conditions are labelled on each arrow

This view is especially helpful for complex forms with many branches.

Tips for Conditional Logic

• Keep it simple — deep nesting makes forms hard to maintain
• Test thoroughly — use Preview mode to walk through every possible path
• Consider the default — always set a sensible default route for unmatched conditions
• Required fields — be careful with required fields inside conditional sections; they're only required when visible
• Pacing mode matters — conditional logic works with all three pacing modes, but is most impactful with Considered and Guided modes where respondents see one section at a time