Per-product fields
You’re here because…
different ticket types need different questions — a workshop needs experience level, a dinner needs a meal choice.
Fields are configured per product, so each ticket type asks only what’s relevant to it.
Tailor questions to the ticket
Because the fields live on the product, a “Workshop” ticket can ask for experience level while a “Gala Dinner” ticket asks for a meal choice and dietary needs — even within the same event. Attendees only ever see the questions that apply to the ticket they bought.
Keep checkout short
Asking only the relevant questions per ticket keeps checkout fast and avoids confusing buyers with fields that don’t apply to them. Add what you need where you need it, and nowhere else.
Reuse a set: for ticket types that need the same questions, configure one and replicate the fields to keep them consistent.
Was this article helpful?
No or partially? Tell us what was missing →