Custom attendee fields

Custom attendee fields let organisers collect extra details at ticket purchase — phone, dietary needs, links, dates, and more — with validation that matches what buyers type.

This guide is for organisers setting up checkout forms.

What’s available

On attendee / ticket forms, field types include:

text, textarea, option, checkbox
email, phone
number, date, url (link)

Standalone Forms also support url, alongside date and number they already had.

Build these in the custom fields section / form builder (Number, Date, and Link controls).

Validation is shared between the builder and the event form schema so what you configure is what checkout enforces.

What buyers enter

In the join / queue checkout flow, buyers fill number, date, and url fields like any other custom field.

URL: must be a valid absolute http or https link. Invalid input shows guidance such as: Enter a valid link, e.g. https://example.com
Date: ISO YYYY-MM-DD
Number: must parse as a number

When a ticket is transferred, the transfer modal can re-collect custom fields from the transferee. Previews of custom fields include the new types.

How answers are stored

Responses are stored with the waiting-list / purchase flow and later resolved against the event’s configured custom fields so exports and dashboards stay aligned with the current form definition.

Good to know

This page does not document min/max on number or date, decimal vs integer rules, protocol-relative URLs, localised date display, changing a field’s type after answers exist, or customising every error string.
Prefer absolute https links when you ask for a URL so buyers clear validation on the first try.

What’s available

On attendee / ticket forms, field types include:

text, textarea, option, checkbox

email, phone

number, date, url (link)

Standalone Forms also support url, alongside date and number they already had.

Build these in the custom fields section / form builder (Number, Date, and Link controls).

Validation is shared between the builder and the event form schema so what you configure is what checkout enforces.

What buyers enter

In the join / queue checkout flow, buyers fill number, date, and url fields like any other custom field.

URL: must be a valid absolute http or https link. Invalid input shows guidance such as: Enter a valid link, e.g. https://example.com

Date: ISO YYYY-MM-DD

Number: must parse as a number

When a ticket is transferred, the transfer modal can re-collect custom fields from the transferee. Previews of custom fields include the new types.

Good to know

This page does not document min/max on number or date, decimal vs integer rules, protocol-relative URLs, localised date display, changing a field’s type after answers exist, or customising every error string.

Prefer absolute https links when you ask for a URL so buyers clear validation on the first try.