The organizer's guide to first-party ticketing

A ticket marketplace solves two problems for a new event: it has a checkout, and it has an audience. Both come at a price that is easy to underestimate. This guide sets out what first-party ticketing means in practice, where the money goes, and how to evaluate a switch without betting an edition on it.

Where the fee goes

Marketplace pricing usually combines a percentage of the ticket price, a fixed amount per ticket and a buyer fee added at checkout. On a $150 conference ticket the total often lands between 12% and 20%. Part of it funds payment processing, which any checkout pays. The rest funds the marketplace's marketing, much of which promotes other events to your buyers on the confirmation page and in its newsletters. First-party ticketing keeps the processing cost, typically under 3%, and removes the rest.

Who owns the buyer

The larger cost is the record. On most marketplaces the buyer belongs to the marketplace: you receive names and emails for fulfilment, but consent to market to them is theirs, and the purchase history that would tell you who to invite back is not exportable in a useful form. On your own domain the buyer is yours, with consent captured at checkout and a purchase history that grows edition over edition.

• Can you export every field, including consent status and purchase history?
• Can you email past buyers about the next edition from your own sender?
• Does the confirmation page promote other organizers' events?

What a first-party checkout needs

A checkout on your domain has to be at least as good as the marketplace's, and for most events that means four things. It must handle the release-day spike without falling over, because a sold-out wave that crashes is a wave that sells on someone else's site. It must support the ways your buyers actually buy: individuals on a phone, companies sending a team on one invoice, groups with a code. It must offer add-ons at the moment of purchase, which is where workshops, dinners and upgrades sell. And it must connect to the rest of the event, so that a ticket becomes a badge, an app login and a record without re-keying.

How to switch without risk

1. Move the website first and let search catch up while the marketplace still sells.
2. Open the next edition's early-bird on your own checkout to past buyers only, and measure.
3. Keep the marketplace listing live but point its ticket link at your site.
4. Switch general release once the early-bird proves the checkout under load.

Organizers who follow this order usually complete the switch within one edition and report that the early-bird wave to past buyers alone covers the platform cost for the year.