Conditional logic allows you to show or hide fields based on a supporter’s response to a previous question. This helps keep your form clean and focused, only displaying additional questions when they are relevant.
With GivePanel Event forms, conditional logic is created using Related Fields.
This article explains how it works and how to configure it.
What Is Conditional Logic?
Conditional logic means: If a supporter selects a specific option, then an additional field appears.
For example:
If someone selects “Other” in a dropdown, you can display a short text field asking them to provide more detail.
If someone selects “Yes” to a medical condition question, you can display a follow up field requesting further information.
This ensures supporters only see questions that apply to them.
Where Conditional Logic Is Configured
Conditional logic is managed inside the Editor tab of your form.
Go to: Event → Forms → Edit Form → Editor → Registration Form
Edit the field that should trigger additional questions, such as a Dropdown, Radio Button or Checkbox field.
Which Field Types Support Conditional Logic?
You can add related fields to:
Dropdown fields
Radio Button fields
Checkbox fields
Short Text, Long Text and Number fields do not support related fields.
How to Add a Related Field
Step 1
Edit your Dropdown, Radio Button or Checkbox field.
Step 2
Under the list of options, click the related field icon under “Action” next to the option that should trigger another question.
Step 3
Choose whether the related field should be required and select the type of field you would like to display when that option is selected (for example Short Text or Long Text).
Step 4
Configure the related field:
Set the field label
Add placeholder text
Add helper text
Set as required if needed
Set a character limit if relevant
Add a default value if required
Step 5
Click Save Changes.
The related field will now appear only when the linked option is selected by the supporter.
How Related Fields Behave
Related fields:
Only appear when their parent option is selected
Can be marked as required
Are included in reporting once completed
Can be reordered within their parent field
If the triggering option is not selected, the related field will remain hidden and will not be required.
Best Practice Guidance
Use conditional logic to:
Capture extra detail only when needed
Reduce form length and improve conversion
Avoid overwhelming supporters with unnecessary questions
Keep compliance related questions clear and contextual
Avoid:
Creating long chains of dependent questions
Making too many conditional fields required
Overcomplicating the supporter journey
If you need help understanding how fields are structured overall, see Understanding and Managing Form Fields.