Conditional visibility
Blocks can be shown or hidden depending on the values of other fields. This turns a static page into a form that reacts to input.
Included in the top plan
Conditional visibility is part of the top plan. The notice in the interface reads:
Upgrade to Pro to show or hide blocks based on form field values.
Creating a condition
- Select the block that should appear conditionally.
- In the block settings, open the Visibility section.
- Choose Field, Condition, and Value.
Use Remove to delete the condition again.
Available conditions
| Condition | Useful for |
|---|---|
| is empty / is not empty | any field type |
| is true / is false | checkmark, decision |
| equals / does not equal | select, text, numbers |
| is greater than / is less than | numbers, date |
Feedback in the editor
The editor shows what currently applies:
- Visible when {condition} — the configured rule
- Currently visible or Currently hidden — the state given the values entered right now
Test it live in the editor
Enter test values in the editor and watch the display switch between Currently visible and Currently hidden. That way you can verify the condition without publishing the page.
Advanced: ApptiveScript
For cases the simple selection doesn't cover, there's Advanced (ApptiveScript). The placeholder shows the syntax:
formValues.get('age').greaterThan(18)Access happens via the field's Key — not its label.
Set keys in advance
If you change an input block's key, existing conditions stop matching — without any error message. Choose descriptive keys before you start using them.
Use Manage keys to see all keys on a page. → Input blocks
For most everyday cases, the simple field/condition/value selection is enough. Beyond that: Syntax, Referencing values, and the function reference. The condition must ultimately evaluate to a boolean value.
Two failure patterns, two causes
A block that never appears usually points to a wrong key — the condition is then always false. A block that always appears usually points to a typo in the expression: on a broken expression, the block stays visible.
Typical uses
| Goal | Condition |
|---|---|
| Follow-up question only on rejection | Decision is false |
| Extra fields only for "Other" | Category equals Other |
| Adults-only section | Age is greater than 17 |
| Follow-up on a poor rating | Rating is less than 3 |
| Details only when provided | Order number is not empty |
Shorter forms through conditional fields
Instead of presenting everything to everyone, show few fields up front and reveal more only when needed. This noticeably lowers the abandonment rate — especially on mobile.
This is also the main reason to build a Page instead of a form: forms have no conditional display.
Showing and hiding entire sections
Visibility applies to one block. Set it on a layout, and its entire contents disappear along with it.
Use a layout as a container
If five fields should appear together, put them inside a vertical layout and set the condition once on that — instead of five times individually. That's clearer and easier to change.
Limits
What visibility doesn't do
- Not access control. A hidden block isn't protected, just invisible. For real restrictions, use access restrictions.
- Not inside HTML blocks. The condition applies to the HTML block as a whole, not to parts within it.
- Only one condition per block via the simple selection. Combinations need
logicalAndorlogicalOr→ Syntax.
Required fields inside hidden blocks
Check how a hidden required field behaves before putting the page into production. Test both cases — condition met and not met — all the way through submission.