Conditional custom fields let you show or hide follow-up questions during checkout based on how a customer answers a previous field. Instead of displaying every possible question upfront, your booking form stays clean and only reveals additional fields when they're relevant.
For example, if you ask "Do you want to add lunch?" with a checkbox, you can set it so "Dietary Restrictions" and "Food Allergies" fields only appear when the customer checks Yes.
Getting Started
Conditional fields are configured in the custom fields editor. Navigate to Setup > Custom Fields to see all your existing custom fields.
Before setting up conditional fields, you need:
- A parent field that acts as the trigger — this must be a Checkbox or Dropdown field type
- One or more child fields that should appear when the parent has a specific value
Note: Only Checkbox and Dropdown fields can serve as parent triggers. Text fields, date fields, and other types cannot trigger conditional logic. Conditional fields support single-level nesting only — a child field cannot act as a parent to another child.
Setting Up a Conditional Field
Step 1: Make sure both fields exist and share an activity
You need two custom fields: a parent (must be a Checkbox or Dropdown) and a child (any field type). Both fields must be assigned to the same activity for conditional logic to work.
If you don't already have both fields, create them under Setup > Custom Fields before continuing.
Step 2: Add conditional logic on the parent field
Open the parent field (the Checkbox or Dropdown that should control visibility). At the bottom of the field editor, you'll see a Conditional Logic section. This is where you define which child fields appear based on the parent's value.
Select the child field you want to show conditionally, then set the condition value — the specific answer that should trigger the child to appear:
| Parent Type | Condition Value | Example |
|---|---|---|
| Checkbox |
1 (checked) or 0 (unchecked) |
Show "Dietary Restrictions" when "Add Lunch?" is checked → condition value = 1
|
| Dropdown | The exact text of the dropdown option | Show "Skill Level Details" when "Experience" = "Advanced" → condition value = Advanced
|
You can add multiple child fields under the same parent. Save the field when you're done. The list view will show a "Triggers N conditional fields" note beneath the parent field name so you can see the relationship at a glance.
Note: Only custom fields assigned to the same activity as the parent will appear as options in the Conditional Logic section. If you don't see the child field you're looking for, check that both fields are assigned to the same activity.
How It Works During Checkout
When a customer reaches the custom fields section of your checkout widget:
- Child fields are hidden by default
- When the customer sets the parent field to the matching condition value, the child field smoothly appears
- If the customer changes the parent value so it no longer matches, the child field hides again and its value is automatically cleared
Note: If a child field is assigned to an activity but its parent field is not, the child will display unconditionally (always visible). Conditional logic only activates when both the parent and child fields are assigned to the same activity.
Common Examples
| Scenario | Parent Field | Condition | Child Field(s) |
|---|---|---|---|
| Lunch add-on | "Add Lunch?" (Checkbox) | Checked (1) |
"Dietary Restrictions", "Food Allergies" |
| Experience level | "Skill Level" (Dropdown) | "Beginner" | "Do you need equipment rental?" |
| Transportation | "Need Pickup?" (Checkbox) | Checked (1) |
"Hotel Name", "Room Number" |
| Group booking | "Booking For" (Dropdown) | "Corporate Group" | "Company Name", "PO Number" |
Managing Conditional Fields
Deleting a parent field
If you delete a parent field, its child fields are not deleted. They become regular (unconditional) fields and will display to all customers. You can reassign them to a new parent or leave them as standalone fields.
Viewing relationships
The custom fields list view shows which fields have conditional logic configured. Parent fields display a subtle indicator below their name showing how many child fields they trigger.
FAQ
Can I chain conditions (child of a child)?
No. Conditional fields support single-level nesting only. A child field cannot act as a parent to another conditional field.
Which field types can be parents?
Only Checkbox and Dropdown fields. Text, date, and other field types cannot trigger conditional logic.
What happens to the child field data if the parent value changes after the customer filled it in?
The child field's value is automatically cleared when the parent no longer matches the condition. The customer would need to re-enter the information if they toggle the parent back.
Can a child field be required?
Yes. If a child field is set as required, it is only enforced when the field is visible (i.e., when the parent condition is met). Customers won't be blocked by a required child field they can't see.
Does this work in the walk-up / POS checkout?
Yes. Conditional visibility works in all checkout contexts — the online booking widget, walk-up checkout, and reseller checkout.
Can one parent trigger multiple child fields?
Yes. You can set multiple child fields to reference the same parent with the same or different condition values.