Conditional logic lets your form respond to what a contact is typing or selecting in real time. You can show or hide fields based on earlier answers, redirect contacts to different pages depending on their responses, and even disqualify submissions that don’t meet your criteria — all without writing code.
Accessing conditional logic
- Open the form or survey in the builder.
- Click the Conditional Logic tab in the right-side panel.
- Click Add Rule to create a new condition.
Each rule follows a three-part structure: when [field] [operator] [value], then [action].
How rules work
Rules are evaluated from top to bottom. For submission-level actions (redirect, display message, disqualify), only the first matching rule executes. For show/hide actions, later matching rules override earlier ones — this allows a sequence of rules to progressively narrow down what’s visible.
This top-down evaluation model makes the order of your rules important. Place your most specific conditions first and your broadest fallback conditions last.
Available conditions
The operators available depend on the field type being evaluated:
Text fields
- Equal to
- Not equal to
- Contains
- Does not contain
- Starts with
- Ends with
- Is empty
- Is not empty
Number and date fields
- Equal to
- Greater than
- Less than
- Between (requires a minimum and maximum value)
Dropdown, radio, and checkbox fields
- Is selected (checks whether a specific option is chosen)
- Is not selected
Checkbox and terms fields
- Is checked
- Is not checked
Submission actions
These actions fire when the contact submits the form. Only the first matching rule executes.
Redirect to URL
Sends the contact to a different page based on their answers. For example: if the contact selects “Yes, I have a budget over $1,000,” redirect them to a booking calendar page. If they select “No,” redirect them to a resource page.
Enter the full URL including the protocol: https://yourdomain.com/next-step
Display custom message
Shows a personalized message inside the form space instead of the default thank-you message. Use this when the appropriate response depends on what was submitted — for example, showing different instructions to clients who chose different service tiers.
Disqualify lead
Prevents the submission from being saved to the CRM and shows a customizable message. Use this when you want to filter out contacts who don’t meet minimum criteria — for example, contacts outside your service area or below a minimum budget threshold.
Disqualified submissions are not saved to your CRM. The contact will not receive any automated follow-up unless you explicitly configure one. Make sure the disqualification message sets appropriate expectations.
Show / hide field actions
These actions change what fields are visible in real time as the contact interacts with the form. They fire whenever the triggering field changes, not just at submission.
Show field
Reveals a hidden field when the condition is met. By default, any field can be set to hidden (it starts invisible) and then shown by a conditional rule.
Hide field
Hides a visible field when the condition is met. Use this to simplify the form for contacts who don’t need to see certain fields. For example: hide the “Business name” field unless the contact selects “Business owner” from an occupation dropdown.
To mark a field as initially hidden (so it only appears when a rule reveals it), open the field settings and toggle Hidden by default to on.
Survey-specific: jump to logic
In surveys, each slide can redirect the respondent to a different slide based on their answer using Jump To logic. This is configured per answer option rather than in the conditional logic tab.
- Click on a multiple-choice or radio answer option in the survey builder.
- A Jump To selector appears showing all available slides.
- Choose which slide the respondent should go to after selecting that option.
Jump To logic lets you create branching survey paths that feel personalized — a respondent who says they are a beginner sees different follow-up questions than one who says they are experienced. The system prevents infinite loops automatically.
Example: progressive disclosure
A form collects contact details and asks if the person has a dog. If “Yes” is selected, additional fields appear asking for the dog’s name, breed, and age. If “No” is selected, those fields remain hidden.
Rule 1: When “Do you have a dog?” equals “Yes,” show the field “Dog’s name.”
Rule 2: When “Do you have a dog?” equals “Yes,” show the field “Dog’s breed.”
Rule 3: When “Do you have a dog?” equals “Yes,” show the field “Dog’s age.”
These three rules keep the form short for contacts without dogs while collecting the extra data from those who do.
Test your conditional logic before publishing by using the form preview. Work through every possible answer path to make sure the correct fields appear, the correct submission actions fire, and no fields are accidentally shown or hidden at the wrong time.