Registration · cluster
Event Registration Form Design That Converts
Most event registration forms ask for too much, in the wrong order, and on a layout that breaks on mobile. Here's the field set, order and structure that actually converts.
The 5–8 fields you actually need
- Full name (single field, not first/last)
- Email address (used for confirmation + check-in lookup)
- Phone number (text-on-arrival, optional but conversion-positive when explained)
- Ticket type and quantity
- One or two custom fields (dietary, t-shirt size, child's age)
- Promo or comp code (collapsed by default)
The field order that converts
- Lead with ticket type so attendees see the price commitment up front — no surprises at payment.
- Identity fields next (name, email) — momentum builds when attendees are typing what they already know.
- Custom fields last, before payment — collect dietary or t-shirt size after the attendee is committed.
- Payment on the same page on mobile — don't redirect to a third-party page that breaks back-button trust.
Mobile patterns that don't bounce
- One field per row — no side-by-side first/last name on screens under 480px.
- Use the right input type —
type=email,type=tel— so the right keyboard appears. - Sticky checkout button at the bottom on long forms — no thumb gymnastics.
- Apple Pay and Google Pay buttons above the card form when payment is collected.
Stop losing registrations to clunky forms
HoldThat EventOS gives you mobile-first registration with built-in tickets, custom fields and confirmation emails.