The honest answer to what data to collect at registration is: far less than you think. Collect only what you will actually use to run the event and follow up afterwards, and make everything else optional or drop it entirely. Every extra field you add is a small tax on your conversion rate and a small addition to your data-protection risk, and most of the fields organisers add "just in case" get used exactly never. This guide covers the short list of what to ask, what to skip, and why a leaner form fills up faster.
The instinct is understandable. You have one shot at capturing information, so why not grab everything while people are filling in the form? Because that thinking is precisely what makes forms long, abandonment high, and your compliance officer nervous.
The rule: if you will not use it, do not ask for it
Before any field goes on your form, ask one question: what decision or action will this data drive? If you cannot name one, cut it. Job title is worth collecting if sales will segment by it. Company size is worth it if it shapes your follow-up. "How did you hear about us" is worth it if marketing actually reports on it. But collecting a field because it feels thorough, with no plan to use it, gives you nothing except a longer form and more personal data to protect.
This is not just good manners, it is the core of GDPR. The data minimisation principle requires that you collect only the personal data necessary for the specific purpose you are collecting it for. Grabbing extra information "just in case", as data minimisation guidance puts it, creates compliance risk and gives people a reason to distrust your form. Less really is more.
What to actually collect
For most events, the genuinely useful set is short. Here is the working list, grouped by whether it is essential or situational.
| Field | Collect it when | Priority |
|---|---|---|
| Full name | Always, for the badge and the record | Essential |
| Email address | Always, for tickets and comms | Essential |
| Ticket type | Always, drives access and pricing | Essential |
| Company and job title | B2B events where you segment by role | Situational |
| Dietary or accessibility needs | Catered or in-person events | Situational |
| Session or track choice | Multi-track conferences | Situational |
| Marketing consent | If you will email them later | Situational but required if used |
Notice how much is not on that list. Phone number, postal address, date of birth, second contact, "tell us about your goals for the event": all of these are candidates for the cutting-room floor unless you have a concrete, named use for them.
What to skip or make optional
Some fields are almost always worth dropping to a plain "optional" or removing outright. Phone numbers, unless you genuinely need to call attendees, tend to spook privacy-conscious people. Postal addresses matter only if you are mailing something physical. Long free-text boxes ("what do you hope to learn?") look engaged and get either left blank or filled with "n/a". Demographic questions can be sensitive and often are not used. If a field is nice-to-have rather than need-to-have, make it optional so it never blocks someone from completing the form.
The conversion cost of a nosy form
Here is the part that turns this from a compliance chore into a commercial win. Shorter forms convert dramatically better. Research cited by form-analytics specialists and widely replicated found that reducing a form from four fields to three can lift conversion by almost 50%, that forms with fewer than five fields achieve 20% to 50% higher conversion, and that more than 30% of marketers report their best conversion from forms with just four fields. Asking for irrelevant information is a documented cause of form abandonment, so cutting unnecessary questions helps completion rates rather than hurting them.
Every field you add is a tiny toll booth between your attendee and their ticket. Some tolls are worth it. Most are just slowing traffic for data you will never read.
Read that together and the picture is clear: the leaner form is the higher-converting form and the more compliant form at the same time. You almost never have to choose between filling seats and respecting privacy. The same edit helps both.
GDPR data minimisation, in one paragraph
You do not need to be a lawyer to get this right. Collect only what you need for a specific, stated purpose. Tell people why you are asking for each piece of sensitive data. Do not repurpose data you gathered for registration into something they never agreed to, like adding every attendee to a permanent marketing list without consent. Keep it only as long as you need it. That is the spirit of data minimisation, and it happens to produce exactly the short, respectful form that also converts best.
Collect more later, not all at once
One trick that keeps forms short without losing data: progressive profiling. Ask for the bare essentials at registration, then gather the nice-to-have details later, when the person is already committed and more willing to give them. A pre-event email can ask for session choices a week before the doors open. A post-event survey can capture the feedback you were tempted to squeeze onto the sign-up form. Spreading the ask across the journey means each individual step stays short, so completion stays high, while you still end up with the full picture by event day. The registration form does not have to be the only moment you ever talk to your attendee, and treating it that way is what makes it bloated.
How to design a lean registration form
Put it into practice with this order of operations.
Step one: draft the field list from the follow-up backwards. Ask what you will do after the event, then list only the data those actions need. This stops speculative fields at the door.
Step two: mark each field essential or optional. If it is not essential to issue a ticket or run the event, it is optional by default.
Step three: show the right questions to the right people. If only in-person attendees need dietary details, do not ask your virtual guests. Conditional logic keeps forms short by hiding irrelevant questions, which we cover in our guide to showing different questions to different attendee types.
Step four: capture consent cleanly. A clear, unticked opt-in for marketing, separate from the act of registering, keeps you honest and compliant.
Step five: make sure the data you do collect actually flows. There is no point asking a smart question if the answer gets stranded in an export nobody opens. A platform like eventcloud keeps registration answers, including your custom fields, attached to the attendee record so the data you deliberately collected is there when you need it, not lost in a CSV. We covered the flip side, chasing details you failed to capture, in the hidden cost of chasing missing registration details.
When you genuinely do need to ask more
Trade-off time, because minimalism has limits. Some events legitimately need more data. A sporting event may need emergency contacts and medical notes. A residential conference needs dietary and accessibility details and possibly room preferences. A regulated industry event may need verification fields. The rule does not change: collect what you will use. It is just that for those events, the list of what you will genuinely use is longer, and that is fine. The failure mode is not "asking a lot", it is "asking a lot for no reason".
So the short version stands. Start from what you will actually do with the data, ask for that and nothing more, make the rest optional, and let conditional logic hide the irrelevant. Your form fills faster, your attendees trust you more, and your compliance risk shrinks, all from the same edit. If you want to build registration forms that stay lean while still capturing what matters, take a look at the eventcloud product.
