Conditional Logic & Branching

Conditional logic allows your survey to adapt based on user input. You can show or hide entire pages, or control the flow within a single page. Instead of every respondent seeing the same questions in the same order, you create paths that respond to their answers.

When to Use

Use conditional logic when different respondents need different questions:

  • Segmented feedback - Ask product-specific questions only to users who’ve used that product
  • Eligibility screening - End the survey early if the respondent doesn’t match your criteria
  • Progressive detail - Ask follow-up questions only when the initial answer warrants deeper exploration
  • Role-based surveys - Show manager questions to managers, individual contributor questions to ICs
  • Skip irrelevant sections - If someone rates satisfaction as 10/10, skip the “what could we improve?” page

Show or Skip Pages

Control whether a page appears based on previous answers. When the condition is not met, the entire page is skipped and respondents continue to the next page.

P2
Page 2

Elements on this page are only shown if the condition is met

Page-level conditions are evaluated before the page loads. The respondent never sees a flash of content that gets hidden - the page simply doesn’t appear in the flow.

Example: A customer satisfaction survey has three pages: General Feedback, Product Issues, and Thank You. Set a condition on the Product Issues page: only show it if the satisfaction rating is below 7. Respondents who rate 7 or above skip straight to Thank You.

Flow Control

Use Flow Control to manage logic within a page. You can skip the rest of the page or end the survey immediately.

P2
Page 2
Yes
No

Flow control is useful when a single answer on a page determines whether the remaining questions are relevant. Instead of splitting content across multiple pages, keep related questions together and let the logic handle the rest.

Example: On an event feedback page, the first question asks “Did you attend the networking session?” If the answer is No, flow control skips the remaining networking questions on that page and moves to the next page.

Building Conditions

Both Page Logic and Flow Control use the same condition builder. A condition defines a rule that the engine evaluates against the current survey data.

Basic Condition

A basic condition compares a “fact” (the answer to a question) against a value or another fact.

  • Fact: The question to check (e.g., “What is your favorite color?”).
  • Operator: The operation to perform (e.g., is equal to).
  • Value: The value to compare against.

Combined Conditions

You can combine multiple conditions using AND / OR logic directly in the editor. Click the + Add condition button to create complex rules.

Supported Operations

The available operators depend on the type of the element being evaluated.

Text (String)

eq
is equal to
contains
contains
exists
has a value

Number

eq
is equal to
gt
greater than
gte
greater than or equal to
lt
less than
lte
less than or equal to
exists
has a value

Boolean (Yes/No)

true
is true
exists
has a value

Select One (Single Choice)

eq
is equal to
in
is one of
exists
has a value

Select Many (Multiple Choice)

eq
is equal to
in
contains any of
all
contains all of
exists
has a value