A conditional custom field appears, becomes required, or changes its options based on other field values. Used well, conditional fields keep forms short and contextual without losing data depth.
Three Kinds of Conditional Behaviour
- Conditional visibility: Field appears only when conditions met.
- Conditional requirement: Field becomes required only when conditions met.
- Conditional options: A dropdown's options depend on another field's value.
Setting Up
- Open the field's configuration.
- Scroll to Conditional section.
- Pick the conditional behaviour to enable.
- Define one or more conditions: trigger field, operator, value.
- Combine with AND/OR.
- Save.
Operator Choices
- equals / not equals
- greater than / less than
- contains / does not contain
- is empty / is not empty
- matches regex
Worked Examples
- Visa status: Visible and required only when nationality ≠ UK. Options vary by nationality (US options different from EU options).
- Refund reason details: Visible only when reason = “Refund request”; required when visible.
- Tax-exempt certificate upload: Visible only when customer ticks “Tax exempt”; required upload to complete.
- Cascading dropdowns: Selecting Country in one field filters the State/Province options in the next field.
- Age-gated medical fields: Show parental-consent capture only when age < 18.
- Subscription tier-specific: Premium-only fields shown only when subscription tier = Premium.
Tip: Server-side validation must mirror conditional rules — the platform handles this automatically. If you write custom validation code, replicate the condition checks or you'll either block valid input or accept incomplete data.