What Is Conditional Logic
Conditional logic allows you to dynamically show and hide form fields based on the attendee's answers. Instead of a long static form, the attendee sees only the fields that are relevant to them.
Example: the "Company name" field appears only if the "Status" field is set to "Organization representative".
Rule Types
show_if — Show If
The field is hidden by default and appears when the condition is met.
Use when a field is needed only in certain cases:
- "Room number" is shown if a ticket with accommodation is selected
- "Dietary requirements" is shown if the "Meals" option is checked
hide_if — Hide If
The field is visible by default and is hidden when the condition is met.
Use when a field is needed by most attendees, except in certain cases:
- "Delivery address" is hidden if the attendee selects "Pickup"
Supported Conditions
Conditions are set based on the values of other form fields.
| Source Field Type | Available Operators |
|---|---|
| Dropdown (select) | equals, not equals |
| Radio buttons (radio) | equals, not equals |
| Checkbox (checkbox) | checked, unchecked |
| Text field (text) | filled, empty |
| Number field (number) | equals, greater than, less than |
How to Set Up Conditional Logic
- Open the event → "Registration" tab → form builder.
- Select the field you want to add a condition to.
- In the field settings panel, find the "Conditional logic" section.
- Click "Add condition".
- Choose:
- Rule type: "Show if" or "Hide if"
- Source field (which field the decision is based on)
- Operator (equals, not equals, filled, etc.)
- Comparison value
- Save the form.
Multiple Conditions
You can add multiple conditions to a single field. All conditions are combined with logical AND — the field is shown (or hidden) only if all conditions are met simultaneously.
Reset on Hide — Value Reset
When a field is hidden by conditional logic, its value is automatically reset. This ensures data correctness:
- The attendee selected "With meals" — the "Dietary requirements" field appeared, the attendee entered "Vegan"
- The attendee changed their mind and selected "Without meals" — the field was hidden, the "Vegan" value was deleted
- Result: dietary requirements for an attendee without meals will not end up in the database
Backend Validation
The backend is the single source of truth for validation. When processing the form, the server:
- Receives all values sent by the client
- Recalculates conditional logic based on the received values
- Completely ignores fields that should be hidden according to the rules
- Validates only visible fields
This protects against client-side manipulation and ensures data consistency.
Recommendations
- Don't create overly deep chains (more than 3 levels) — this complicates the form for attendees
- Test all condition branches before publishing
- Use the preview mode to ensure the logic works correctly
- Remember: hidden required fields do not block form submission