Eventually Ticketing
Creating Events

Custom registration questions and fields

Custom registration fields let you collect additional information from attendees beyond the standard name and email. You can add custom questions to your event to capture dietary restrictions, t-shirt sizes, session preferences, or any other details your event requires.

What you can collect

Add custom questions to your event registration form using these field types:

  • Text fields: Short text or Long text responses

  • Choice fields: Single select, Multi-select, Checkbox (single), or Yes/No. Single select and Multi-select take an Options list, and Multi-select lets attendees pick several options. Checkbox (single) is a single consent or agree box with no options list; Yes/No offers two fixed choices.

  • Contact fields: Email or Phone

  • Number: numeric input

  • Date: date picker

Each question can be marked as required (attendees must answer) or optional, and you can add helper text to clarify what you're asking. A required Multi-select question needs at least one choice, while a required Checkbox (single) needs the box checked.

Helper text supports links: type [text](https://example.com) or paste an http(s):// address, and it renders as a clickable link. Helper text is limited to 500 characters and rejects HTML when saved. Links are the only formatting helper text supports; Markdown styling such as bold and italic is not applied. Helper text appears on the registration form, the completion page after checkout, and the staff add-guest form.

Ask a question on all tickets, specific tiers, or add-ons

Each registration question has an Asked on control that sets which ticket types the question applies to. The default is All tickets, and the control also offers Specific tickets and Specific add-ons. Choose Specific tickets to select the ticket types that should see the question.

A registration question is scoped to seat tiers or to add-on tiers, never both. If a tier switches from one kind to the other, the question's selection is pruned so it never mixes the two. A question scoped to an archived add-on tier is still an add-on question.

A question with no selected ticket types continues to apply to every ticket, so existing events keep their previous behavior until you change a question's setting. Guests see and answer only the questions that apply to their ticket type.

Add-on questions are asked once per unit

Buyers see an add-on-scoped question only when that add-on is in their order, and the question is asked once for each purchased unit: three shirts means three size fields. A required add-on question must be answered for every unit. Add-on questions are collected at checkout, and they are not included when the event collects attendee information after purchase.

Add-on answers appear per unit in the attendee detail view, the guest drawer, and the attendee CSV export, and they follow their add-on unit through transfers, tier changes, and partial refunds. Manually adding a guest does not collect an add-on-scoped question.

Attendees see these answers on the add-on card in the confirmation email and on the public ticket page for that add-on. Both present the add-on as the item itself, with pickup guidance rather than door check-in wording.

Add and reorder questions

Custom questions are managed in the event editor under Registration questions. Name and email are always collected by default and cannot be removed or reordered.

You can reorganize custom questions at any time by dragging them into your preferred sequence. The saved order is used on the public registration form.

Question labels cannot contain a web address or HTML. If validation fails, the editor keeps the question open and shows the message under the label.

Edit or remove questions after registrations

You can edit, reorder, or relabel custom questions after attendees have registered, in the event page editor and the event wizard. Existing answers stay attached to the same question, so editing a question never discards what buyers already answered.

Removing a question keeps the answers attendees already gave. The removed question no longer appears on the registration form for new registrants, and its saved answers still appear in attendee views, the attendee CSV export, and Evie can still read them.

In the event wizard, click View deleted questions under the question list to see removed questions marked Deleted, each with Restore. A restored question returns to the end of the active question list.

Restoring a question marked as required can mean orders placed while it was deleted need to answer the question again.

If a question save fails, the editor shows Questions weren't saved instead of an error page.

Where registration data appears

Responses to your custom questions appear in:

  • Attendee details: view individual attendee responses in your dashboard

  • CSV export: each current custom question becomes its own column after the standard attendee columns, headed by the question label and ordered with your saved question order. Answers from checkout, manual guest add, and post-purchase attendee information are included. See Exporting attendees to CSV.

  • Confirmation email: the answers for each attendee appear under their ticket card as Your answers, with empty answers omitted

  • Check-in view: access custom field responses during event check-in

Plan requirements

Custom registration fields require the Essentials plan or higher. The Free plan does not include custom registration fields.

Registration questions and their helper text, including any links, never appear on the public event page or the calendar widget before checkout. They render only inside the attendee form: during checkout in Before mode, or on the completion page in After mode.

My waiver link doesn't show on the public event page before checkout

A registration question is not event-page content. It renders only inside the attendee form, and no setting places it on the public event page before checkout. To make a waiver link part of registration, paste the address into a question's helper text: type [text](https://example.com) or a plain http(s):// address, and it renders as a clickable link wherever the question appears. A link to Paperform or another external waiver service behaves the same way: it is a question with a link, not a pre-checkout waiver step.

Was this helpful?
Was this helpful?