The data you already have and are not using

Your season just ended. Thousands of people came through your events, every one of them bought a ticket with a name and an email attached, and every one of them is somewhere.

The problem is where. Some in your ticketing platform. Some in the spreadsheet someone on the team put together with last year’s data. Some in a Google Form from the summer giveaway. Some in the email tool’s list, which hasn’t been updated in three editions.

You have the data. What you don’t have is a database.

The difference isn’t semantic

A pile of scattered data and a database are told apart by one very simple test. Try answering this right now:

How many people came to your last two editions? Not one: both.

If answering that means exporting two files, cross-referencing them by email and cleaning up duplicates by hand, you don’t have a database. You have homework you’re never going to do, because every time you need the answer it costs half an afternoon, and you end up deciding without it.

That question, by the way, is the single most profitable one a promoter can ask. Whoever comes back is your real audience: the ones who buy in presale, the ones who bring people along, the ones who carry the slower days. And most promoters have no idea how many that is.

What you lose with every season that passes

Attendee data doesn’t fall apart all at once. It degrades slowly, on three fronts at the same time.

It loses context. A bare email address is worth almost nothing. That same email tied to “bought a full pass in presale for the last three editions, always travels in from out of town” is worth a great deal. When you export to a spreadsheet, you throw away the context and keep only the email.

It ages. Every month that passes, a share of those addresses stops existing, changes job, or gets abandoned. A list exported two years ago carries a meaningful chunk of dead contacts — ones that actively hurt you when you send to them.

It fragments. The same person shows up three times under three different emails, or once per edition, and to your tool they look like three different people. You end up paying to message the same person three times, and they receive the same message three times over.

At the end of this process you’re left with a large file that feels reassuring and is useless for making any decision.

Why a manual export isn’t a solution

The natural reaction is “I’ll just export from the ticketing platform each season and upload it.” That’s what almost everyone does, and it has three underlying problems.

The first is that it freezes the data. The file reflects reality on the day you exported it. Everything that happens afterward — a purchase, a refund, an unsubscribe — doesn’t show up until the next manual export, which in practice happens every few months, or never.

The second is that it depends on someone remembering. And during the season, nobody remembers, because there’s always something more urgent.

The third, the most expensive one: you only export what fits in a CSV. The full purchase history, behaviour across editions, what type of ticket each person chooses, whether they buy early or at the last minute. All of that lives in your ticketing platform and never makes it to the other side.

What changes when the data flows in on its own

Connecting the data source instead of exporting it isn’t a technical nicety. It qualitatively changes what you can ask.

With a list of emails, you can send the same message to everyone. With a live purchase history, you can do what actually moves the needle: notify repeat attendees first, treat someone who came once and never returned differently, spot the people who buy in presale and give them early access, or simply know how much new audience you brought in this season versus how many came back.

That last figure — the ratio of new audience to returning audience — is probably the most honest health indicator a promoter has. And it can only be calculated if every edition’s data lives in one place, kept up to date.

The time to do this is right now

This is low-season work. Nobody is going to sit down and tidy up data in April, and even less so mid-sales-campaign.

Right now, though, you have this season’s numbers on the table, a clear head, and time to ask yourself questions you can’t afford to during the year. This is the exact moment when getting your house in order costs little and shapes how you’ll work for the next twelve months.

Tools like Nevent connect to your ticketing platform so the data flows in and stays current without anyone having to export anything. But before that, the exercise I’d genuinely recommend this week is more uncomfortable and costs nothing: make a list of every place where your attendee data currently lives. There are usually more than you remember, and seeing them together is often enough to understand the problem.