Why tracking decides whether ads sell tickets

Meta, Google and TikTok all run on the same basic idea. You tell the platform what a good result looks like, and its algorithm goes looking for more people likely to produce that result. If you tell it a good result is a ticket purchase, it finds buyers. If you tell it a good result is a click, it finds clickers.

The only way the platform knows a purchase happened is if your tracking tells it. That is the whole job of the pixel and the Conversions API. When they work, every ticket sold feeds back into the campaign and makes it smarter. When they don’t, the campaign optimises blind.

Most promoter ad accounts we look at have at least one serious tracking problem. That isn’t a criticism. Ticketing checkouts happen on someone else’s website, set-up varies by platform, and nobody gets trained on it. But it is the reason we fix tracking before we spend anything.

What a pixel is

A pixel is a small piece of code that runs in the buyer’s browser. When someone views your event page, adds tickets to the basket or completes a purchase, the pixel sends a message to the ad platform saying so. The ad platform matches that message to the person who saw or clicked your ad.

Because your checkout normally lives on your ticketing platform’s website rather than your own, you don’t install the pixel yourself. You give the ticketing platform your pixel ID and it fires the events on its pages. How you do that, and which events it fires, depends entirely on the platform.

Browser pixels have limits. Ad blockers, browser privacy settings and cookie choices can stop the message being sent. Some purchases simply never get reported. That is where the Conversions API comes in.

What the Conversions API is

The Conversions API, often shortened to CAPI, is Meta’s server-side route for the same information. Instead of relying on the buyer’s browser, the ticketing platform’s server sends the purchase directly to Meta. It doesn’t depend on what happens in the browser, so more purchases get through.

To send events server-side on your behalf, the ticketing platform needs an access token. You generate that token in Meta Events Manager, for the same pixel you have already given the platform, and enter it in the platform’s tracking settings where that option exists.

The best set-up runs both together: the browser pixel and the Conversions API, reporting the same purchases. That raises an obvious question. Doesn’t that count every ticket twice?

De-duplication: counting each ticket once

It would, without de-duplication. When the browser pixel and the server both report a purchase, they each attach the same unique identifier, typically the order ID. Meta sees two messages with the same ID and the same event name, and keeps one.

When de-duplication works, you get the best of both: the coverage of server-side reporting and the speed and detail of the browser pixel, with purchases counted once. When it doesn’t, you see inflated purchase numbers, a cost per ticket that looks too good to be true, and an algorithm learning from bad data.

You can check this in Events Manager. Look at the purchase event, compare browser and server events, and check whether Meta is reporting them as de-duplicated. Then compare the total with your ticketing platform’s own sales report for the same period.

Why purchase events matter for optimisation

Ad platforms let you choose a campaign objective and an optimisation event. For ticket sales, the one you want is Purchase. Not traffic, not landing page views, not engagement.

Clicks are cheap and plentiful, so optimising for them looks efficient. But the people most likely to click are not the people most likely to buy. Optimising for landing page views has the same problem one step further down. You pay less per result, and the result isn’t a ticket.

Purchase optimisation needs two things to work: purchase events that are genuinely purchases, and enough of them. On small events, the volume can be thin early in the run, which is another reason budget belongs later in the curve, when purchases are flowing and the algorithm has something to learn from.

It also needs the purchase value. Sending the order value lets you report revenue and return on ad spend, and lets you calculate cost per ticket properly rather than cost per order.

Common mistakes we fix

These come up again and again in promoter accounts. None of them are exotic. All of them cost money.

  • One pixel shared across several brands or promoters. Audiences and data blur together, and every brand’s campaigns learn from everyone else’s buyers.
  • The Conversions API token missing, or generated for a different pixel from the one on the event.
  • Events firing on the wrong page, so a “purchase” is recorded when someone loads the checkout rather than when they complete it.
  • Duplicate purchases, because browser and server events aren’t de-duplicating.
  • Pixels added to some events and not others, so the account learns from half the sales.
  • Campaigns optimising for clicks, traffic or landing page views because nobody trusted the purchase data.
  • Domain and dataset set-up that doesn’t match the business structure, which limits what the ad account can do.

Tracking builds your audiences too

Pixels don’t just report purchases. Every event page view, basket and purchase becomes an audience you can use: people who viewed but didn’t buy, people who bought last year, people who look like your buyers.

This is why one pixel per brand matters so much. A clean pixel that has been on every event for two years is an asset. It holds your real buyers, by event and by year, and makes every new on-sale cheaper to start. A pixel shared with three other promoters holds a blurred mix of everybody’s audiences and is worth far less.

It is also why tracking should go on before the first ad runs, not halfway through the campaign. Audiences only start building from the moment the pixel fires.

A quick self-check

You don’t need to be technical to do a first pass. Open Meta Events Manager and your ticketing platform’s sales report side by side.

  • Is there one pixel per brand, and is it the one on every event?
  • Does the Purchase event appear, and does its count roughly match real orders?
  • Are server events arriving alongside browser events, and are they de-duplicated?
  • Is each campaign set to optimise for Purchase?
  • Can you calculate cost per ticket from what you see?

How it works on your ticketing platform

Set-up differs by platform, and so does what is possible. We have written a separate guide for each platform we see most often. Each one sticks to what we have confirmed. Where we haven’t confirmed a detail, we say so and check it during the audit.

A few examples. Skiddle lets promoters add pixels per event in its Promotion Centre under Promotion → Tracking, and sends purchase events to Meta server-side alongside the browser pixel using a unique order ID for de-duplication. Eventbrite supports a Meta pixel and server-side tracking via a Conversions API access token you generate in Events Manager. TicketSource booking pages sit on TicketSource’s domain, which you can’t verify in your own Meta Business Manager, and that limits some ad functionality.

For every other platform, including DICE, Ticketmaster, Ticket Tailor, Resident Advisor, See Tickets and Fatsoma, read the individual guide below. We are independent and not affiliated with any of them.

Skiddle guide Eventbrite guide DICE guide Ticketmaster guide Ticket Tailor guide TicketSource guide Resident Advisor guide See Tickets guide Fatsoma guide

Get it checked

Tracking is the least glamorous part of selling tickets and the part that decides whether everything else works. If you are not sure your purchase data is right, it probably isn’t, and it is worth finding out before the next on-sale rather than after.

The audit itself is not complicated. We look at the ad account, the pixels and datasets, the events your ticketing platform is sending and the campaigns that rely on them. Then we fix what is broken, document what we changed, and test a real purchase end to end so you can see it arrive.

Our Tracking Audit & Repair covers pixels and datasets, the Conversions API, purchase events and the ticketing platform integration, for a fixed fee that is credited against your first campaign. Or start with the free Sales-Curve Teardown and we’ll flag anything obvious along the way.

Part of how we work as a live music marketing agency that reports in tickets sold.