Skip to main content
Every event can ask its own questions when someone registers. A conference needs dietary requirements and an organisation name; a members’ evening needs almost nothing. Built for organisers who need more than a name and an email from the people attending, and who want the answers to land on the member’s profile and in the participant export rather than in a spreadsheet somewhere else. Replaces a Google Form bolted onto an event page, with the answers already attached to the right attendee record. The form belongs to the individual event, so building it well once does not carry over to the next.

​
Turning the form on

Open the event, choose Edit, and under Who can join switch on Require registration form for members. A Registration form entry then appears in the event sidebar. Without it, members simply RSVP. Editing the form needs event admin rights on the event’s group; organisation-wide event admins and organisation admins can edit it on every event.
Ticketed events always use a registration form. Switching an event to Paid turns this on automatically and locks the toggle, with the hint “Paid events always require a registration form”. Choosing the Public audience (or Private link) turns it on too, though there the toggle stays editable.

​
Building the form

The page header says “What people fill in when they register for this event” and shows All changes saved or Unsaved changes, with Discard, Save changes and Open public form (opens the form as a visitor sees it). The Form fields tab is a two-panel builder: Available fields left, Form fields right. Click or drag a field across to add it, drag rows to reorder (or use the move up and move down buttons on each row), tick required where an answer is mandatory, then Save changes. Email and Full Name show a lock and “Email and Full Name are always asked.” Registration form builder with Standard fields and Custom fields tabs on the left and the assembled form on the right, each row carrying a required checkbox

​
Standard fields

Twelve fields, no others, and their labels cannot be edited. For a logged-in member they arrive prefilled, so the member confirms rather than retypes. Write-back happens only when the answer is not empty and differs from what is stored. Fields marked No are still collected and exported, just not copied onto the profile by this path. Removing Email or Full Name through the API silently puts them back at the top of the form on save.

​
Custom fields

Anything the standard list does not cover becomes a custom field: use Create custom field on the Custom fields tab of the left panel. The pencil and bin icons beside a field edit or delete it. Options for the three list types are entered one per row and can be dragged into order; the order you set is the order people see, including after you reopen the field to edit it. Deleting a custom field also removes it from the form layout, and needs the same permission as editing the form.
Event custom fields belong to that one event. They are not the organisation-wide custom fields, they do not appear in the picker on any other event, and there is no way to copy them across. Budget for rebuilding them on each event, or start the event from an event template.

​
Settings tab

A live Preview beside the settings shows the effect. Settings tab of the event registration form showing the two registration option switches and the custom text box Consent checkboxes are not configured here: the GDPR checkbox appears when your organisation has a GDPR policy URL, the terms checkbox when it has a terms URL. Both come from Organisation Info.

​
Appearance tab

Hero image border radius is only applied when Selected color also has a value, so set a selected colour if you want the rounding to take effect.

​
Where the answers end up

  • Custom field answers are stored per registration, on that attendee’s record for that event. The same person answering differently at two events keeps two answers.
  • Standard answers update the profile as in the table above.
  • The participant export contains exactly the standard fields on the form, plus every custom field, once a form layout has been saved. An event that requires a form but has no saved layout exports all ten profile fields instead, and an event that does not require a form exports six legacy fields: phone, organisation, role, LinkedIn, X and Instagram. Checkbox, radio and dropdown answers export as their visible labels, dates as YYYY-MM-DD. Exporting needs organisation-wide event admin rights, event admin rights on the event, or event ownership.
Decide what you need before the event: you cannot ask retrospectively. Be sparing with required, since every mandatory field is a reason to abandon registration, and on a paid event that is a lost sale. Test in a private window: the form an anonymous visitor sees is not the one you see as an administrator.

​
Troubleshooting

It appears only when Require registration form for members is on for that event, and only for someone who can edit the event.
Public event pages are cached. Saving the form clears that cache for public and ticketed events, so reload the public page itself, in a private window, rather than the editor.
Standard field labels are fixed. Add a custom field with the wording you want and leave the standard field off the form.
Build the event once with its form and custom fields, save it as an event template, and create future events from that.
The export includes only the standard fields currently on the form. Remove a field after people registered and their answers stop appearing in the export, even though the profile values remain.