Thinklytics

Live Nation Regional Division · Gaming & Hospitality · Nashville, TN · 14 weeks

Ticketing and fan data governance framework deployed across 8 venues

Live Nation’s regional division was losing $940K a year due to duplicate fan records that skewed ticket sales, loyalty points, and upsell efforts. We created a data governance framework that cleaned up these duplicates and set up controls to maintain data quality going forward.

Challenge

The regional division managed 8 venues, each using a separate ticketing system and fan database. This setup created duplicate fan records across systems, leading to incorrect ticket sales attribution, repeated loyalty points, and failed upsell attempts targeting existing customers. The revenue team calculated these problems were costing nearly $1 million annually.

Approach

We created a single fan identity by matching email, phone, and purchase data across eight venue databases to eliminate duplicates. Then, we set up rules to block new duplicates from entering the system. Finally, we built a dashboard to monitor duplicate rates in real time.

Outcome

We cleaned up the fan database by merging duplicates, cutting them from 184,000 to 11,200 within 800,000 records. This fixed misattributed sales and duplicate loyalty points, stopping $940K in annual revenue losses. With accurate fan records, the upsell campaign failure rate fell sharply, from 144 to 24 failures per month, because campaigns reached the right audience.

We rolled up our sleeves and sifted through 800,000 fan records. Turns out, 184,000 were duplicates. So, we cleaned house and cut out all the repeats.

We dove into the data and uncovered 184,000 duplicate fan records out of 800,000 across eight venues. That blew the revenue team’s minds, it was way more than they expected. The duplicates had piled up over six years because each venue was managing its own data, completely siloed. There was no way to connect fan identities across locations.

Spotting problems early saved us a bunch of time and money.

First off, we cleaned up all the duplicate records. Then, we put in place some quick checks to catch duplicates the moment new fan records popped up. That small change slashed monthly duplicates down to under 4,000.

How We Put Together Upsell Campaigns That Really Reached the Right Customers, and Got Results

About 18 of every 100 of our upsell campaigns were bombing because duplicate records kept sending mixed messages to the wrong fans. So, we jumped on fixing that with identity resolution. Once we did, our campaigns hit the right fan profile 97 of every 100 times. Crisis averted.

Results

  • $940K Annual revenue leakage resolved
  • 184K to 11K Duplicate fan records
  • 8 Venues on unified fan identity
  • 144 to 24 Failed campaigns per month

We knew duplicate fan records were a problem, but we didn’t expect it to be costing us $940,000 a year. Thinklytics fixed it, and now our upsell campaigns are finally working.

VP of Fan Engagement, Live Nation Regional Division

In the client's terms

The question

Which number is right, and who gets to decide?

The situation

Eight venues, eight ticketing systems, eight fan databases. The same fan existed several times over, so sales were attributed to the wrong venue, loyalty points were issued twice, and upsell campaigns were sent to people who had already bought. The revenue team put it near $1M a year.

What we found

Nobody owned the fan record, so nobody was accountable for whether two rows were the same person. Deduplicating once would have bought about a quarter before the duplicates returned.

What it produced

Duplicates fell from 184,000 to 11,200 across 800,000 records. Misattributed sales and double-issued loyalty points stopped, closing $940K a year in leakage. Failed upsell campaigns fell from 144 a month to 24.

The roadmap

A single fan identity resolved across all eight databases on email, phone and purchase history. Then the part that matters: rules at the point of entry so new duplicates cannot be created, rather than a clean-up that has to be repeated. A live duplicate-rate dashboard so the next drift is visible while it is small.

The work behind this result

Related case studies

Frequently asked questions

How do duplicate customer records cause revenue leakage?

They split one person across several profiles. At a Live Nation regional division, 184,000 duplicates in 800,000 fan records meant sales attributed to the wrong venue, loyalty points issued twice and upsell campaigns sent to people who had already bought, costing $940K a year.

Is deduplicating a customer database a one-off fix?

No. Cleaning the existing base here would have bought about a quarter before duplicates returned. Validation was added at the point new fan records are created, which took monthly new duplicates below 4,000 and kept them there.

How much does identity resolution improve campaign performance?

At this division, failed upsell campaigns fell from 144 a month to 24, and campaigns now match the correct fan profile 97 times in 100. Around 18 of every 100 had been failing on duplicate records.