Show a field only when an earlier answer matches
Updated September 18, 2026
Ask a question only to the people it concerns: a field can depend on an earlier answer.
What it’s for
Every field on the Form step has a Visibility setting with three states. Always shows the field to every visitor. When… shows it only when an earlier answer matches a rule you write: a job title once a company is named, a dietary question for the people coming in person. Never hides it from the page while a link can still fill it in.
A field the rule skips is not shown, not required, not validated and not sent to your event platform. The same rule runs on the page and again when the registration is saved. It works on an in-person page as much as on a page built on a Livestorm, Zoom or Microsoft Teams event.
On step 2 · Form, open the row of the field you want to show conditionally. A field that already carries a rule sums it up under its name.
Under Visibility, pick When…: the rule then reads as a sentence under Show when. A field asked before this one, an operator and, when the operator takes one, a value. Here Job title shows when Where do you work? is not empty.
The operators follow the type of the field being read: a dropdown offers “is” and “is any of”, a date “is before” and “is after”, a checkbox “is ticked”. Look at the live preview: the field the rule hides shows as a dashed row in its place, with what would reveal it. Type a matching answer above it and the field appears. Visitors never see the dashed row: on the page, the field is simply skipped.
Add a condition to narrow the rule, up to five. Every condition joins with the same word, and or or, which you pick on the row. While a condition is still incomplete the rule is paused and the field shows to everyone, so nothing disappears from a live form while you are still picking.
A rule only reads what the visitor has already answered, so the field menu lists the fields asked before this one. A field asked after shows greyed out: drag the row below it to read it. Move a field above the one it reads and its rule pauses, with the row saying so.
Good to know
- The email can never depend on another answer: it identifies each registrant. A consent checkbox cannot either, and no rule can read one.
- On a page built on a Livestorm, Zoom or Teams event, a field the platform requires always shows: skipping it would make the platform refuse the registration. Make it optional on the platform, then re-pull. On an in-person page you own the form, so a field can be both required and conditional: required only when shown.
- Unanswered is no match: for a field the visitor left blank, only “is empty” and “is not ticked” are true. A field hidden by a rule counts as unanswered for the rules that read it, so hiding a question also retracts what it would have shown. A step whose every field is skipped is skipped too.
- A field on Never, filled from the link, can be read by a rule: it counts as answered first, wherever it sits. That is how a page asks a question only to the visitors who arrived through a given link.
- Texts compare without regard to case or spaces around them, numbers and dates by value. Rules survive a re-pull from your platform, like types and placeholders; only a field the platform has since made required loses its rule, since it must always show.
Related articles
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?