Ask anything at checkout: custom questions, per order or per attendee
Every event has its own questions. Some organizers need dietary preferences for catering. Some need attendee names on each ticket. Some sell swag bundles and need t-shirt sizes. Until today, Usetix asked the same four things of every buyer: name, email, phone, and (for B2B) billing info.
Starting today, you define the questions.
Two scopes, chosen per question
Every custom question is asked in one of two ways:
- Per order — once per checkout. A single “Any dietary requirements?” question the buyer answers once, no matter how many tickets they buy.
- Per attendee — once per ticket. If someone buys three tickets and the question is attendee-scoped, the form repeats three times on the checkout page — one set of answers per ticket.
The distinction matters because a single answer rarely fits both cases. “Dietary preferences” for a group-of-ten booking is often one shared answer. “Attendee name” has to be one per person. You pick the scope that matches the data.
Four field types
Cover the common shapes without getting fancy:
- Short text — names, free-form answers
- Long text — addresses, notes
- Dropdown — t-shirt sizes, meal choices, anything with a fixed list
- Checkbox — consents, confirmations
Each question can be marked required (the checkout blocks until it’s answered) or optional.
Answers show up everywhere that makes sense
You collect answers in one place, and they appear in every place you’d want to find them:
- On the order detail page in the admin dashboard — under the buyer’s info for order-scope answers, under each ticket for attendee-scope answers.
- In a dedicated attendee CSV — from the event’s actions menu, click Export attendees (CSV). One row per ticket, sorted by customer email. All custom answers as extra columns. Perfect for a check-in sheet, a catering list, or a t-shirt order.
- In webhooks — every
order.paid,order.refunded, andorder.cancelledwebhook now includes the custom answers, both at the order level and per item. If you sync Usetix to a CRM, a fulfillment pipeline, or a catering system, the data is there in real time.
What you might build
A few things we’ve seen organizers set up in the first day:
- Dietary preferences for seated dinners — one question, order-scope, catering reads it from the CSV
- Attendee names for conference badges — per-attendee text field, exported and fed into a badge printer
- T-shirt sizes for bundled events — per-attendee dropdown with S/M/L/XL, turned into a single bulk order to the supplier
- Accessibility requirements — per-order textarea, required, so front-of-house is briefed before the event
- Age confirmation — required checkbox, satisfies legal gates for age-restricted events
- “How did you hear about us?” — optional dropdown, feeds marketing attribution in your analytics tool
How to set one up
- Open an event in the admin dashboard
- Scroll to Custom checkout questions (between FAQs and performers)
- Click Add question — set a label, pick a type, pick a scope, toggle Required
- Save
The question goes live on the checkout page immediately. You can reorder questions by dragging, and edit or remove them at any time — existing orders keep their answers.
For the developers
If you’re integrating Usetix with your own systems, the webhook payload docs show the exact JSON shape for custom answers. Each answer arrives as { id, label, type, value } — stable IDs, current labels, typed values (checkbox booleans come through as booleans, not strings).
The full feature reference lives in the docs.
Try it now
Custom checkout questions are live for all Usetix accounts. Open an event, scroll, click Add question. If you run into anything or want to tell us what you’re collecting, hit [email protected].