How to Add Custom Questions to Checkout

Step-by-step guide to adding checkout questions, choosing question types and scoping, using templates, and exporting attendee responses — with an interactive builder to configure questions as you learn.

What Are Custom Questions?

Fields you add to checkout to collect information from buyers and attendees

4 Question Types

Short text, long text, dropdown select, and checkbox

Flexible Scoping

Per-attendee or per-order — you choose who answers

CSV Export

Download all responses as a spreadsheet with one click

Build Your First Question

Configure a checkout question and see the live preview, checkout appearance, and API schema

Question BuilderInteractive
Select from options
Checkout Preview
Dietary Requirements *
👤 Asked per attendee
Vegetarian
API Schema
{
  "label": "Dietary Requirements",
  "type": "dropdown",
  "scope": "per_attendee",
  "required": true,
  "options": [
    "None",
    "Vegetarian",
    "Vegan",
    "Gluten-Free",
    "Kosher",
    "Halal",
    "Other"
  ]
}

How to Add Custom Questions

Follow these steps in your event dashboard

1

Open the Questions Tab

Navigate to your event in the dashboard and select the Questions tab. This is where you manage all checkout questions for the event.

2

Add a New Question (or Use a Template)

Click Add Question to create from scratch, or choose a Template for common questions like dietary restrictions, t-shirt size, emergency contact, or waiver acceptance. Templates auto-fill all fields.

3

Configure the Question

Set the label (what buyers see), choose the type (text, long text, dropdown, or checkbox), and add options if using dropdown. For dropdowns, keep options concise — 4–8 choices is ideal.

4

Choose Scope & Required

Set per-attendee (asked per ticket holder) or per-order (asked once). Toggle required if the question must be answered. Use per-attendee for individual needs like dietary; per-order for group-level info like "How did you hear about us?"

5

Save & Preview

Save the question and it appears at checkout immediately. Preview your event page to see how it looks to buyers. Reorder questions by dragging them in the dashboard.

Best Practices
  • Keep it short: 3–5 questions max. Every extra field increases checkout abandonment.
  • Use dropdowns over text fields when possible — easier for buyers, cleaner data for you.
  • Only mark questions as "required" if you genuinely need the data. Optional fields get answered more honestly.
  • Use per-attendee for individual data (diet, sizes, contacts) and per-order for group data (attribution, billing).
  • Start with templates — they cover the most common use cases and save configuration time.
  • Test your checkout before going live. Preview as a buyer to verify question flow.

Per-Attendee vs Per-Order

The most important decision: who answers the question?

Asked for every ticket holder. If someone buys 3 tickets, they answer 3 times — once per person.

Best for
Dietary Requirements
Each attendee may have different needs
T-Shirt Size
Each attendee wears a different size
Emergency Contact
Unique to each person
Skill Level
For workshops — each participant differs
Waiver Acceptance
Legal: each person must agree individually
Checkout Preview
Ticket 1 — Alex M.
Vegetarian
Ticket 2 — Jordan K.
Gluten-Free
Ticket 3 — Sam R.
None
Each attendee answers independently

Question Types Explained

Each type is designed for specific data collection needs

Aa

Short Text

Up to 500 characters

Best for names, phone numbers, one-line answers. Example: "Emergency contact name and number"

Long Text

Up to 2,000 characters

Best for detailed responses, medical notes, special requests. Example: "Please describe any accessibility needs"

Dropdown Select

Custom options list

Best for fixed choices — diet, sizes, skill levels. Example: "T-Shirt Size" with S, M, L, XL, XXL

Checkbox

Yes / No toggle

Best for waivers, opt-ins, confirmations. Example: "I accept the liability waiver"

Troubleshooting & Edge Cases

Common questions when things don't behave as expected

Question not showing at checkout

Check that the question is enabled in the dashboard. Also verify the event is on an Elevate or Amplify plan — Custom Questions aren't available on the free tier.

Missing data in CSV export

If a question was added after some tickets were sold, earlier orders won't have answers. The CSV will show blank cells for those rows. Future orders will include the new question.

Checkout feels too long

Reduce the number of required questions. 3–5 questions is the sweet spot. Move nice-to-have questions to optional. Consider merging related questions into a single dropdown.

Editing a question after launch

You can edit question labels, options, and required status at any time. Changes apply to future orders only. Past responses are preserved with the original question text.

Frequently Asked Questions

Was this article helpful?