12 May 2026 · 3 min · Wesley Veldeman
Collect attendee details and dietary needs with forms
Need names, dietary requirements or a T-shirt size? Attach a form to a ticket type and gather exactly what you need at checkout. Forms are on every plan; CSV export is Pro.
Sometimes a ticket is not enough
For plenty of events, you need more than a name and an email. A dinner needs dietary requirements. A workshop needs each attendee's name. A run needs T-shirt sizes. A conference needs to know which session someone picked. Chasing all of that by email after the sale is miserable, and the answers arrive in a dozen different formats.
Forms solve it by collecting what you need right at checkout. Attaching a form to a ticket type is available on every plan. CSV export of the answers is a Pro feature.
Attach a form to a ticket type
A form is attached to a ticket type, which means you can ask different questions for different tickets. A "dinner" ticket can collect dietary needs while a plain "entry" ticket asks nothing extra. Whatever you attach is presented to the buyer during checkout, and the answers are saved with the ticket.
The field types you can use
Forms support a full set of field types, so you can ask for almost anything in the right format:
- text — short answers like a name;
- long text — paragraphs and notes;
- email and phone — contact details with the right input;
- dropdown — pick one from a list;
- checkbox — yes/no or opt-ins;
- radio — choose one option;
- number — quantities and counts;
- date — a specific day.
| Field | Good for |
|---|---|
| Text / long text | Names, notes, special requests |
| Email / phone | Contact details |
| Dropdown / radio | Choosing one option (session, menu, size) |
| Checkbox | Opt-ins and yes/no |
| Number / date | Counts and specific dates |
Once per order, or once per ticket
This is the important choice. You can collect a form's answers in one of two ways:
- once per order — asked a single time for the whole booking, good for things that apply to the buyer (a billing reference, a company name);
- once per ticket — asked for every ticket in the order, so each individual attendee enters their own details.
Per-ticket is what you want for things that vary by person. If someone buys four dinner tickets and you collect once per ticket, each of the four attendees gets their own name and dietary-needs fields, rather than the buyer guessing on everyone's behalf. That gives you accurate, person-by-person data instead of one lumped answer.
Reviewing and exporting the answers
Every answer is saved with its ticket, so you can review them inside ClearTix whenever you need. For the kitchen list, the name badges or the session breakdown, you will usually want it all in one place — and that is where CSV export comes in. Exporting the collected answers as a CSV is a Pro feature, giving you a spreadsheet you can hand to a caterer, a printer or a colleague.
A tip worth following
It is tempting to ask for everything. Resist it. Keep required fields to the minimum — every extra mandatory question is another reason for someone to abandon the checkout. Ask for what you genuinely need to run the event, make the nice-to-haves optional, and you will collect better data from more people because fewer of them give up partway through.
Where it fits
Forms earn their place wherever the event needs more than a headcount:
- dinners and galas collecting dietary requirements per guest;
- workshops and courses capturing each attendee's name;
- runs and sports events gathering sizes and emergency contacts;
- conferences letting people choose sessions at booking.
A cooking class, for instance, can collect each guest's allergies right at checkout.
Want to see exactly which capabilities sit where across the plans? The pricing page has the breakdown, and the features overview shows the rest.
Related reading
- Group bookings and invoices for companies — capture company billing details at checkout
- Sell class packs and passes — collect details across recurring class bookings