Purpose: Allows Administrators to collect important personal and contact details from registrants.
Fields might include:
Name, position, organisation, contact details (email, phone, address), gender, date of birth, etc.
Functionality:
Field creation: Administrators can add, clone, edit, or delete fields.
Form elements: Can be free text, selection lists, dates, or sections for organising the form.
Mandatory vs. Optional: Some fields can be required, others can be optional.
Field settings: Include options for labels, character limits, and help text.
Purpose: Collects extra data for marketing or specific event purposes.
Fields might include:
Dietary preferences, areas of interest, industry segments, networking preferences, etc.
Functionality:
Similar to the Personal Information page in terms of adding, editing, and deleting fields.
Admins can include questions like “How did you hear about the event?” or ask for consent on data privacy.
Administrators can configure field types (text, selection, date) with mandatory or optional settings.
Creating Forms:
Use the “+ Add” button to create a new page or form element, and name the page.
Form elements can be customized based on type (e.g., free text, selection, date).
Sections can be organized with titles and descriptions to guide registrants.
Customisation:
Fields can be reordered, expanded, or reduced in width.
Administrators can create different versions of the forms for various attendee groups.
Self-service: Registrants can view and update their personal registration details directly, allowing them to maintain up-to-date information throughout the event lifecycle.
Impact: This enhances the user experience by giving attendees control over their data and reduces administrative effort for event organizers.
This structure seems well-designed for collecting essential and additional information while giving both admins and registrants flexibility.