Tickets
Create ticket structure, pricing, categories, and availability.
Tickets define how people register and what access they receive.
A strong ticket setup gives you better control over capacity, pricing, and guest flow.
Think in audience segments
Design tickets around audience behavior (VIP, early access, standard, partner), not just around price labels.
What you can configure per ticket
For each ticket, you can set:
- ticket name,
- free or paid pricing,
- available quantity,
- guests per ticket,
- schedule/timeslot,
- category placement,
- active or paused state.
| Ticket setting | Why it matters |
|---|---|
| Price type | Controls paid vs free entry experience |
| Quantity | Controls scarcity and sell-out behavior |
| Guests per ticket | Controls group entry limits |
| Timeslot | Controls date/time access windows |
| Category | Keeps complex ticket sets organized |
How ticket organization works
Categories
Categories let you group tickets by purpose, such as VIP, Early Access, or Day 1.
Date-aware setup
Tickets can be linked to event dates and timeslots so multi-day events stay clean and easy to manage.
Reordering
Tickets and categories can be reordered to match your selling strategy.
Capacity and availability
A ticket can become unavailable when:
- it is paused,
- its quantity is sold out,
- or it is outside its schedule window.
That ticket can close even while the overall event is still active.
Paid ticket context
If your event has paid tickets, you may be asked to complete payout setup before full paid flows are available.
Ticket invitation rule (important)
Invitation-based registrations are complimentary for invited guests.
This remains true even when the linked ticket type is usually paid in normal checkout.
Recommended ticket setup flow
- Create your core ticket types (free/paid).
- Add categories only if they improve clarity.
- Confirm quantities and guests-per-ticket values.
- Test with a small invite batch.
- Launch wider invitation sends, then Promotions and campaigns.
Common mistakes to avoid
- Creating too many ticket types that overlap.
- Forgetting to check schedule windows for date-specific tickets.
- Using invitation sends without reviewing ticket linkage first.