How to Sell More Event Tickets

1. The Prior-Attendee List

Highest return by a wide margin, and it is not close.

The people most likely to buy a ticket to your event are the people who bought one last time. That much is obvious. What is not obvious is how few event teams have a clean, current list of prior attendees who have not bought yet, because producing it means matching two rosters against each other, and nobody does that by hand.

In the operation this came from, 414 of 1,225 buyers were returning attendees, a third of the whole audience. That segment had never been identified before, because the roster match had never been run.

How to build it

1. 1

   Export both rosters

   Pull this cycle's registrant list and last cycle's full attendee list out of your ticketing platform as CSVs.

2. 2

   Match on email, verify on name

   Match the two lists on email address, then verify each match against first and last name. People change jobs and email addresses, so an email-only match both misses returning attendees and wrongly flags current ones.

3. 3

   Exclude unassigned group tickets

   Where an organization has bought tickets but not yet named the attendees, exclude that organization entirely. Otherwise all of those people land on your 'has not bought' list.

4. 4

   Segment the result

   You now have three lists: returning buyers, first-time buyers, and prior attendees who have not bought yet. The third is the one you work.

5. 5

   Work it personally

   Short, specific, from a human's address rather than a marketing alias, referencing something concrete about last cycle.

2. Sell Earlier

Open sales to your own list before you open them to the public.

Early sales do three things at once. They de-risk the budget, so you are not guessing in month two. They give you time to react to a bad pace while there is still time to change something. And they compound, because attendees who commit early start telling colleagues they are going.

The presale also gives your prior-attendee list a reason to exist beyond "please buy". You are offering them something before everyone else gets it, which is a materially different email to write.

3. Segment by Role

One email to everybody is the default, and it is the weakest option available.

The operation resolved its audience into eleven job-function segments. Eleven roles want eleven different reasons to attend, and a message written for all of them lands squarely with none.

The obvious objection is that you do not have role data. Neither did they: the prior cycle had usable role data on 64 of 907 records. The current cycle had it on 815 of 1,225, a twelvefold improvement. That was achieved by inference and enrichment from data already collected, not by adding fields to the registration form.

This matters because every extra form field costs you registrations. The way to get better data is almost never to ask for more of it.

4. Sell to Organizations, Not Just People

The operation drew from 170 distinct organizations. Where an organization sent several people last cycle, the highest-leverage move is not emailing all of them. It is talking to whoever organised it.

One conversation can cover many tickets, and the person who coordinated last time already knows the value, already has the budget line, and often just needs a nudge and a date.

5. Reach Multipliers

A reach multiplier is any structure where you recruit one person who brings many. Satellite hosts and watch parties are the clearest example.

The economics are different in kind, not degree. You are not selling a seat and paying acquisition cost per seat. You are equipping a host, who then does the recruiting inside a network you could not have reached and would not have been trusted in.

In the archive, a host program produced 678 host registrations reaching roughly 2,000 people. Sell the host, not the seat.

6. Fix the Data First

Duplicates and stale records quietly cap every campaign above them on this list. A duplicate makes one person look like two, inflates every rate you calculate, and eventually emails somebody twice with contradictory information.

One failure worth naming specifically: if you migrate ticketing platforms mid-cycle, imports from the old platform can land as zero-value records. Real sales then exist only in the old platform's export, and your year-over-year comparison becomes fiction without anyone noticing.

Reconcile before you report. A confident number built on a broken join is worse than no number.

7. Pace Against a Model

A running total tells you nothing on its own. What you need is a projection you update weekly, built from your current pace and the shape of last cycle's curve, so you know whether to act.

In the archive that looked like this: a live pace of 7.8 tickets per day, against a modeled full-cycle projection of 1,503 to 1,765 tickets. Having the band mattered more than having the point estimate, because it made the decision obvious rather than debatable.

The reason to bother is timing. Acting on a bad pace in week three is a campaign. Acting on it in the final week is a discount.

8. Make the Ask Specific

This applies to your team as much as your audience. A specific, solvable gap motivates in a way a large round number does not.

"We need 60 more tickets, which is twelve organizations sending five people" is a plan. "We need to sell more tickets" is a mood.

What Order to Do This In

If you only do one thing, do lever one. If you have a week, do this:

1. Fix the obvious data problems, so the rest is not built on sand.
2. Build the prior-attendee list and work it personally.
3. Stand up a pace model so you can see whether it worked.
4. Segment by role and rewrite the campaign for the two biggest segments.
5. Then everything else.

Steps two and three are both byproducts of one report, which is why the year-over-year ticket report is the first thing to build. It is free, and it is the whole skill.

Frequently Asked Questions