The short answer
Ticketing data records a transaction: a seat, a price band, a date and usually a name attached to the buyer. Fan identity is a picture of a person: who they are, what they care about and how they take part. The two overlap less than most organisations assume, and treating the first as the second is how a club ends up knowing the ticket and not the person.
What a ticket really tells you
A ticket tells you that someone bought something. Often that someone is not the person in the seat. One buyer purchases for a family, a company, a group of friends, or sells a pair on. The name on the order is the name of whoever held the card.
Even when buyer and attendee are the same person, the record is thin. It says when they bought, which game and where they sat. It does not say why they came, whether they enjoyed it or whether they will be back.
The people the ticket never sees
Plenty of fans never appear in ticketing data at all. They watch on a screen, follow on social, travel for an away day with a ticket someone else bought, or care deeply about a team they have never been able to visit. Judged by the ticket, they do not exist.
Then there are the people inside the stadium who are in the order under somebody else's name. For a sponsor trying to prove they reached an audience, that gap is expensive. They are paying to reach people the data cannot see.
Where identity actually comes from
Identity builds up over time from moments where a person chooses to show up as themselves. A fan who films a reaction, calls a score, or records what a match meant to them is telling you something no transaction record can. The platform pillars FANDEMiQ is organised around start from this: turn fan-created images, video and audio reactions into more durable audience identity over time.
The word "durable" matters. One moment is a data point. A season of moments, tied to a fan who chose to take part, is something closer to a relationship.
Closing the gap without replacing ticketing
You do not need to throw out your ticketing system. It is good at what it does, which is selling and scanning seats. The idea is to add a second source that is better at what ticketing is bad at: knowing the person.
In practice that means giving fans a reason to take part around the moments you already run, through an account of your own, and letting each contribution add to what you know. Over a season the two sources start to describe the same people from different angles. Where they disagree is often where the useful questions are.
Why the gap gets expensive
A gap in knowledge is cheap until somebody asks you to prove something. A sponsor wants to know who they reached. A commercial director wants to know whether a new fan group is growing. A board wants to know whether the people turning up are the people you think they are.
Each of those questions is about people, and each is answered badly by a list of transactions. You can approximate, and most organisations do, but approximation is where decisions quietly go wrong. A club that believes its audience is one thing while it is another will price, programme and pitch for the wrong crowd.
There is also a practical cost in the day-to-day. Marketing can only write to the people it can name. Everyone else is a number on a dashboard, and numbers do not reply to emails.
A fair way to describe your audience
When you next write a report, try separating three groups: people you can name, people you can count but not name, and people you suspect exist but cannot see. Most organisations have a tidy answer for the first, a rough one for the second and a shrug for the third.
Saying so out loud is progress. It turns an invisible problem into a visible target, and it gives you a plain way to explain to colleagues why the next piece of work is about people rather than seats.
What to ask your own data
Try three questions of what you hold today. How many of the people who engage with you could you name? How many of those could you contact, with their agreement, about something other than a ticket? And how many could you describe by what they care about rather than where they sat?
If the honest answers are few, a few and almost none, you are not alone, and you have found the work.
Quick answers
Is ticketing data first-party data?
Yes, when you sell the ticket yourself, the record is first-party. The limit is what it contains: a transaction, not a person. It is a useful starting point and a poor substitute for knowing who your fans are.
Why is the buyer not always the fan?
Because people buy tickets for families, friends, colleagues and customers, and tickets are passed on. The order tells you who paid, not who attended, and not who cares about the team.
How do you build fan identity beyond ticketing?
Give fans small, worthwhile ways to take part around the moments you already run, such as filming a reaction or calling a score, and let each contribution build up what you know, with their agreement, over a season.
Keep reading
- What is first-party fan data, and how do you collect it without forms?First-party fan data is what fans tell you directly, in your own channels. Here is what counts, why it matters, and how to gather it without another form.
- Fan engagement platforms compared: what to ask before you buyChoosing a fan engagement platform? Use this checklist on data ownership, staff time, approvals, branding and exit, and ask every vendor the same questions.
