Skip to main content
Supported event types
Virtual ✅| In-person ✅ | Webinar ✅ | Field event ✅ | Third-party
Custom fields transform Zuddl’s registration form from a one-form-fits-all gate into a data pipeline that collects exactly what marketing, sales, and operations need—without forcing every attendee through the same questionnaire.

​
Creating a field

Open Registration › Form, click + Add field, and choose a type: short text, long text, number, phone, email, URL, country selector, dropdown, multi-select, rich-text, date, date-time, or session picker. Give the field a public label (“Company size”), an internal slug (plain text for integrations), and, if needed, a description that appears beneath the input to clarify expectations (“Round to the nearest hundred employees”). Saving immediately places the field in the live preview, so you can confirm spacing and mobile breakpoints before publishing. Formflow Pn

​
Mandatory, hidden, and default Values

Every custom field supports three core settings in Advanced Options:
  • Required – blocks form submission until the attendee answers. Use for must-have compliance items like “Country of residence” or “I agree to the terms.”
  • Hidden – the field is never rendered to the attendee, yet still stores data pushed in from APIs or bulk uploads. Perfect for tags such as lead-source or segment that you don’t want registrants editing.
  • Default Value – pre-populates the input so users can accept the suggestion or overwrite it.

​
Conditional Logic

Inside Registration › Form you can attach a rule to any custom field (standard fields like First Name, Last Name, and Email remain static). Create two or more custom fields, then click Add Logic on the second one. A three-step wizard appears:
  1. Choose the earlier field that drives the rule.
  2. Pick an operator—is, is not, contains, does not contain, all of the, any of the.
  3. Select the value(s) that satisfy the condition.
When the rule evaluates true, the target field renders; otherwise, it stays hidden. Because logic references only fields that appear above the target, re-ordering a form after launch can break dependencies. For instance, use field logic to ask dietary restrictions only from in-person attendees or request a shipping address only when someone chooses a swag-eligible ticket.

​
Auto-fill across bulk tickets

For bulk purchases Zuddl can copy answers from the first attendee to every subsequent seat—ideal for shared attributes like “Company,” “Country,” or “Job title.” Toggle Auto-fill at field level, and the purchaser edits only what differs, speeding checkout while maintaining consistency across the order.

​
Mapping to integrations

During the integration’s field-mapping step you drag the Zuddl property onto its CRM counterpart and choose an overwrite policy. This one-time action guarantees that lead-scoring, nurture branches, and dashboards fire on fresh, structured data—no CSV manipulation required.

​
Bulk updates and imports

Need to edit and patch hundreds of answers? Export the attendee list as CSV, modify the custom-field columns, and upload the sheet back into People › Attendees › Bulk Update. Zuddl validates data types (e.g., blocks letters in number fields), before processing and allows you to make corrections if any.
⌘I