Conditional Guest Fields

Introduction / Overview:

Conditional guest fields allow certain guest registration fields to appear only when specific answers are selected earlier in the guest registration form. This simplifies the experience for guests by ensuring they’re only shown questions that are relevant based on their previous responses.

For example, if a guest selects “Yes” to travelling by plane, additional fields such as “Flight Number” or “Arrival Airport” can then appear.

This feature is managed at the company level.

Activation & Set-up:

Step 1: Go to Guest Registration Fields in Settings

Navigate to Company Settings > Lists > Guest Registration Fields and find the existing field you'd like to make conditional.

Step 2: Edit or create a field

Click Edit next to the field. Or, to create a new field, select Add Guest Field. If adding a new guest field, select your desired field type and then scroll to the new section called Dependent field settings, found just above the Save button.

This section will be collapsed by default unless dependencies have already been added.

Supported field types for conditional logic include:

• Dropdowns, multi-select checkboxes, and radio lists. 

Step 3: Add Dependent Fields

Click Add dependent field to begin creating a condition. A pop-up window will open where you can define the logic for your conditional rule.

Steps / How-To:

Creating a Condition

Set the trigger rule:

Choose the parent field and define the logic. For example:
If “Travel Method” is equal to “Flight”

Choose a logic rule:
Available options:

• equal to any of

• not equal to any of

Enter values:

In the input field, enter one or more values, separated by commas.
Example: Oxford, Manchester, Liverpool, London

Select the dependent field:

Choose the field that should appear when the condition is met. You can only select from fields that don’t already have an existing dependency.

Save your settings.

Once saved, the conditional logic is live. Guests filling out the form will only see the dependent fields if the specified conditions are met.

Managing Existing Conditions

• All dependencies are shown in a table labelled Child field dependencies.

• You can edit or delete these using the buttons next to each rule.

• Fields with dependencies will be marked with a special icon in the guest field list. 

Warnings & Safeguards

• If you delete a field that has dependent fields, you’ll be prompted to either:

  • Delete all child fields, or

  • Unlink the child fields

• If you delete a specific field value that has a condition attached, a warning will appear listing the affected dependent fields.

• Dependent fields support up to three layers of dependencies (grandparent, parent, and child). You will not be able to add any additional layers beyond this limit.

Guest Form Behaviour

• When guests open a form, any dependent fields will be hidden by default.

• If the condition is met while completing the form, the relevant fields will automatically become visible.

• Admins can use Guest Preview to test the guest form experience, including viewing how conditional fields behave based on different responses.

• It is supported within Edit guests on a request and on registration forms

FAQs

Q: Can I apply this at the event level?
A: Dependencies can currently only be created at the company level.

Q: Which field types support conditional logic?
A: Most standard field types are supported- including text, drop-downs, and number fields. For date fields, conditions work using text format (e.g. “26/06/2023”).

Q: Can I use the same field as both a trigger and a dependent?
A: No-  a field cannot both trigger and depend on itself, or be used in multiple conflicting dependency rules.

If you have any questions, please reach out to [e-mail] or your Customer Success Manager.