Custom fields on the registration form
Beyond the standard fields (name, email, phone), JustOneEvent lets you add up to 10 custom questions to the registration form: select options, free text, integers, checkboxes. Here's how to design them effectively and stay GDPR-compliant.
"How many will be vegetarian?" "What's their level?" "Did they attend last year?" Without custom fields, these questions become an email back-and-forth after registration that quickly gets lost. With them, the answer is captured at registration time, structured, exportable to CSV, and automatically shared with your staff team.
The 5 available field types
1. Free text (500 characters max) — for open answers: "specify your allergy", "free comments". 2. Integer — for counts: "how many bottles are you bringing", "licence number". 3. Single choice (select) — for one answer among N predefined options: "beginner / intermediate / advanced", "starter / main / dessert". Ideal for statistics. 4. Multiple choice (multi_select) — for 0 to N ticked options: "allergies" (can tick several), "workshops you'd like to attend". 5. Checkbox — for a simple yes/no: "I want the newsletter", "I consent to being photographed".
For the group or for each person: the field's scope
JustOneEvent lets visitors register up to 10 people in one go. Each custom field can therefore apply to the whole group or to each person: — For the group: a single answer, given by the leader. Examples: "How did you hear about us?", "Promo code", "Company name", "VAT number". Stored only on the leader's registration. — For each person: each participant answers separately. Examples: "Dietary preferences", "Skill level", "T-shirt size", "Allergies", "Year of birth". Stored on each registration in the group. The wrong scope has two effects: "for the group" instead of "per person" and you lose the per-participant info (you won't know that 2 of the 5 registrants are vegetarian). "Per person" instead of "for the group" and you ask the leader the same question 5 times (registration friction).
GDPR: what you need to know before enabling
When you enable custom fields, you become the GDPR data controller for the data thus collected. Concretely: 1. Minimisation — only ask for what is strictly necessary to organise the event. Don't ask for a full date of birth if you only need the year. Don't ask for a phone number from every additional participant if the event doesn't need to reach each one individually. 2. Article 9 GDPR forbidden — NEVER collect via these fields: health data, political or religious opinions, sexual orientation, ethnic origin, genetic data. Unless you have a dedicated documented legal basis (rare). Practical note: "dietary regime" sits on the edge. Ask for "dietary preferences (vegetarian / vegan / gluten-free / other)" without medical detail, and state the purpose ("to adapt the catering"). If you need severe allergy information for safety, create a dedicated optional free-text field with an explicit label ("Severe allergies requiring staff attention — optional"). 3. Information — inform the registrant of each collection's purpose in the field label or the event description. "Dietary preferences (to adapt the buffet)" rather than just "Diet". 4. Retention and anonymisation — JustOneEvent automatically erases free-text answers 36 months after the event (GDPR anonymisation). Structured answers (choices, numbers, checkboxes) are kept as anonymous statistics. 5. Rights — you remain responsible for responding to access, rectification or erasure requests from your registrants. Use the CSV export from the registrations page to provide them with their data.
Step-by-step: add a field
1. Create your event (custom fields need an existing event to attach to — they become available as soon as you land on the edit page). 2. On the edit page, find the "Custom fields on the form" block (located between "Dates and times" and "Capacity and visual"). 3. Type the label (what registrants will see), pick the type, tick "Required answer" if needed, and pick the scope (per person / for the group). Click "Add the field". 4. For "single choice" and "multiple choice" types, then add your options one by one (max 20 per field). 5. Reorder fields with the up/down arrows — the order you see is the order in which they'll appear on the public form. 6. Editing after publication: you can adjust label, required flag and scope at any time. The type itself is not editable (changing a select to text would break already-collected answers). To change the type, delete the field and recreate it. Note: deletion is a soft-delete — answers already collected stay visible in your dashboard and CSV export (labelled "deleted"), but the field disappears from the public form.
Three concrete examples
🥗 Cooking workshop — buffet to adapt — "Dietary preferences (for the buffet)" — single choice: none / vegetarian / vegan / gluten-free — per person — required — "Severe allergies if any" — free text — per person — optional — "How did you hear about us?" — single choice: word of mouth / social media / press / other — for the group — optional 🏃 Charity run — bib management — "T-shirt size" — single choice: XS / S / M / L / XL / XXL — per person — required — "FFA licence number if licensed" — free text — per person — optional — "Year of birth" — integer — per person — required 🎓 Pro training — corporate billing — "Company name" — free text — for the group — required — "VAT number for the invoice" — free text — for the group — optional — "Experience level" — single choice: beginner / intermediate / advanced — per person — required
Well-designed custom fields = smooth registration + usable data
Three rules to remember: minimisation (only ask for what's useful), correct scope ("for the group" or "per person" depending on the data), and a label that explains the purpose. Available on every plan, up to 10 fields per event, with automatic anonymisation 36 months after the event. Bonus: structured answers (choices, numbers, checkboxes) remain as anonymous statistics for retrospectives across editions.
Run an event and create your fields in 2 minutes
Free plan included, GDPR compliance built in.
Create my event