Custom Registration Fields on Eventsona: How-To
Add custom registration fields on Eventsona to collect dietary needs, sizes, and preferences at checkout—then export answers for ops and check-in.
Why custom fields matter
Default ticket checkout collects buyer basics. Custom registration fields let you ask for information that makes the day runnable: dietary needs, t-shirt sizes, accessibility notes, workshop level, or emergency contact—without a separate form tool.
Step 1: Open custom fields for your event
In the event settings, open Custom Fields (or the equivalent registration fields section). Click Add Field to start building the form attendees complete during purchase or registration.
Step 2: Choose the right field type
Pick the simplest input that gets a clean answer:
- Text / textarea: Short or longer free text
- Number: Quantities or ages when you truly need digits
- Email / phone: When you need a contact beyond the buyer account
- Select / radio: One choice from a fixed list
- Checkbox: Multiple selections (for example session interests)
- Date: When a calendar pick is clearer than free text
Step 3: Configure each field
For every field, set:
- Label: What the buyer sees (plain language)
- Required vs optional: Only require what operations cannot proceed without
- Options: For select, radio, and checkbox lists
- Order: Group related questions together
Step 4: Keep the form short
Every extra required question increases abandonment. Ask only what you will use for catering, seating, workshop placement, or safety. Mark nice-to-haves optional.
Step 5: Use answers in operations
View responses with your attendee list in the event dashboard. Export CSV when catering, production, or partners need a spreadsheet. Useful answers at the door should be easy for check-in staff to find—train them where to look before doors open.
Good use cases
- Conferences: Dietary preference, accessibility needs, badge name
- Workshops: Experience level, laptop yes/no, learning goal
- Networking nights: Industry or topics they want to discuss
Privacy and UK GDPR basics
Collect the minimum, state why you need it in your event description or policies, and do not export attendee data to tools that do not need it. Delete or restrict access when the operational need ends.
Frequently asked questions
Should every ticket type see the same questions?
Prefer one clear form for the event unless experiences differ wildly. Confusing buyers with mismatched questions slows checkout.
Can I change fields after tickets have sold?
You can adjust future registrations carefully. Changing required fields mid-sale can break incomplete carts and confuse existing buyers—document any change for support.
How do fields help on the door?
They do not replace QR check-in. Use fields for prep (catering, seating); use QR check-in for entry.
Next steps
Become an organiser and add only the fields your floor team will actually read. Pair this with managing tickets and orders and QR check-in for first-time organisers. Explore Events, book space via Venues, and review Pricing.
Related guides
How to Create Your First Event on Eventsona (UK)
Create your first Eventsona event in the UK: set up GBP tickets, add venue details, publish, and share your public event link to start selling today.
Manage Tickets & Orders on Eventsona: Complete Guide
Manage Eventsona tickets and orders: view sales, handle refunds, export attendees, and keep GBP checkout tidy before doors open and payouts clear.
Event Analytics on Eventsona: Read Sales Data Well
Use Eventsona event analytics to read ticket sales, revenue, and check-in data—then improve pricing, timing, and promotion for your next UK event.