Appearance
Conditional visibility
Show or hide fields based on the visitor's answers to other fields on the same form. Hidden fields are also excluded from server-side validation, so a visitor never gets blocked by a required field they couldn't see.
Add a visibility rule
- Open the form in the builder.
- Click the field whose visibility you want to control.
- In the field editor, open the Logic section and toggle Enable conditional logic.
- Pick an action (Show / Hide), a match mode (All / Any), and add one or more rules.
Each rule has three parts:
- Field — the field whose value is being compared.
- Operator — see Operators below.
- Value — the value to compare against.
Operators
| Operator | Meaning |
|---|---|
equals | Value matches exactly |
not_equals | Value does not match |
contains | Value contains the substring |
not_contains | Value does not contain the substring |
greater_than | Numeric: greater than |
less_than | Numeric: less than |
is_empty | Field has no value |
is_not_empty | Field has any value |
Match modes
- All — every rule must be true for the action to apply.
- Any — any single rule being true is enough.
Example: show "Other" text field when "Other" is selected
- On a Select field, add an option labelled "Other".
- Add a Text field below it called "Please specify".
- On the Text field, enable conditional logic with: action = Show, match = All, rule =
your_select_fieldequalsOther.
Now the "Please specify" field only appears when the visitor selects "Other".
How fields are referenced
Rules reference fields by a stable internal field key (e.g. fld_01J9K2P3QX…), not the field's name. That means renaming a field's HTML name will not break existing rules. Duplicating a field always produces a fresh key.
Behaviour on the frontend and server
- Frontend — visibility is evaluated live as the visitor types or selects. Hidden fields are not submitted.
- Server — submission validation skips hidden fields entirely. A required field that is hidden by a rule does not produce a validation error.