Ticket Types, Tiers and Early Bird Pricing Explained
How to structure event tickets so the pricing does work for you: tier design, what to include, when to close early bird, and the mistakes that leave money on the table.
Ticket structure is the cheapest lever in an event. It costs nothing to change, it decides your revenue curve, and most events run the one they inherited from last year without asking whether it still fits.
Start with the segments, not the prices
Who actually comes to your event, and who pays for them? Typically: people whose employer pays, people who pay themselves, students, speakers, and sponsors' guests. Those are your ticket types. The price is the second question.
A structure that works for most conferences
- Early bird — the standard ticket with a deadline. Not a cheaper event; the same event, bought early.
- Standard — the reference price everything else is measured against.
- Student / concession — verified, and clearly a different product if it excludes the dinner.
- Group — three or more from one organisation. See group registration.
- Day pass — for multi-day events, priced above half the full rate.
- Online — if you run hybrid, priced on what it includes rather than as a discount.
Five or six types is plenty. Beyond that you are building a matrix your own desk cannot explain at check-in.
Tier by date, not by quantity
"First 100 tickets" creates an argument when you sell 103. A date closes itself, can be announced, and gives you a deadline to market against — which is where the urgency actually comes from. Our guide to early bird campaigns covers the timing.
Be precise about what is included
For each type, in one line on the ticket page: which days, which sessions, meals, the dinner, the workshops, the recordings. Most refund arguments are inclusion arguments, and they are all avoidable at the point of sale. If your platform can limit session access by ticket type, say so plainly rather than relying on people to self-police.
Four ways events lose money here
- Early bird that never closes. An extended deadline teaches people to wait for the extension.
- No group rate. The single easiest way to turn one registration into four.
- Free tickets with no commitment. Free is fine; unaccountable is not. See reducing no-shows.
- A speaker code that leaks. Issue codes per person with a use limit, not one code shared by email.
Watch the mix, not just the total
Two events can sell the same revenue with very different futures: one on early bird volume, one on late full-price panic. The mix tells you whether next year's campaign should start earlier or price higher. Track sold against target per ticket type as the weeks go — that comparison is on Gathervo's dashboard, and the metrics that matter piece explains what to do with it.
Set up your ticket types free and see the curve as it builds.
Keep reading
All articles- Registration & TicketingHow to Set Up Event Discount Codes Without Losing RevenueDiscount codes are useful and easy to get wrong. Limits, expiry, per-person codes, tracking which channel worked — and how to stop one code reaching a public deals site.October 4, 2026
- Registration & TicketingEvent Registration Forms That People Actually FinishEvery extra field costs you registrations. Here is which questions to ask, which to move to later, and the form structure that gets people to the payment screen.October 2, 2026
- Registration & TicketingCollecting Event Payments: Cards, Invoices and Wire TransfersHow people actually pay for events, why corporate buyers need an invoice, what partial payments solve, and how to stop reconciliation eating a week of your life.October 5, 2026
- Registration & TicketingReducing No-Shows at Free EventsFree events lose 30–50% of registrations to no-shows. Here is what actually moves that number — deposits, reminders, waitlists, and the commitment step that costs nothing.October 6, 2026
Comments
Continue the discussion around this blog post.
You must be logged in to participate in the discussion.
Login to CommentNo comments yet
Start the conversation by leaving the first comment on this post.