How to Track Ticket Sales From Meta and Google Ads on Ticketmaster, Eventbrite, AXS and Etix

Post-tour wrap meeting. The Meta report says the campaign drove 1,240 purchases in one city. GA4 says 610. Google Ads claims 380. The ticketing settlement says 3,900 tickets were sold online in that city, from about 1,050 orders. The promoter asks which number is real, and the room goes quiet.

They’re all real. They’re just counting different things, over different windows, with different blind spots.

To track ticket sales from Meta and Google ads, put each ad platform’s pixel on your ticketing platform’s confirmation step (and the server-side version where the platform supports it), make sure the purchase passes order value and currency, tag every link with consistent UTMs, and then reconcile everything weekly against the ticketing platform’s own sales report, which is the only source of truth for tickets and revenue.

What each major platform supports varies a lot, and some of it isn’t documented publicly. Below is what we could verify from each platform’s help pages, and what to ask your rep where we couldn’t.

Why ad platforms and ticketing reports never match

Before fixing anything, know which gaps are normal. Every one of these shows up in event accounts we’ve worked in:

• Orders vs. tickets. Ad platforms count purchases (orders). Ticketing reports count tickets. A family of four is one purchase and four tickets.
• Face value vs. all-in. Some platforms pass face value without fees. Your settlement may show gross with fees, or net after them.
• Attribution windows. Meta credits a purchase within its click, engagement and view windows. Google Ads uses its own. GA4 uses another. One sale can be claimed by all three.
• Privacy and blocking. Eventbrite says plainly that tracking pixels “aren’t able to track every purchase,” because buyers who disable tracking or use strict privacy settings aren’t tracked, per Eventbrite’s tracking pixel overview.
• Refunds, transfers and manual sales. Eventbrite’s GA4 ecommerce data “doesn’t account for refunds, transfers, or manual transactions,” per Eventbrite’s Google Analytics article. Box office and group sales never touch a pixel.
• Broken journeys. A buyer clicks an ad on their phone and buys on a laptop, or the session breaks when they hop from your site to the ticketing domain.

So the goal isn’t to make the numbers match. It’s to know how big each gap normally is, so that when one moves you notice.

What each ticketing platform supports

We verified each of these against the platform’s own help pages or a partner’s official setup guide as of November 2026. Ticketing platforms change these features often, so confirm before a big on-sale.

Eventbrite. The setup lives under your event’s Marketing section, Tracking pixels. Per Eventbrite’s Meta pixel article, the Meta pixel fires PageView on the listing and Purchase on order confirmation, and you can add standard events like InitiateCheckout tied to the order form. To turn on server-side tracking, flip the Server side tracking toggle and paste a Conversions API access token from Meta Events Manager (Eventbrite won’t help generate it). Eventbrite also notes you can’t verify its domain with Meta, so some Meta features may be unavailable. For Google Ads, Eventbrite’s Google Ads pixel article asks only for the conversion ID (the digits after “AW-”) and the conversion label, includes total and currency when ecommerce data is available, and says Google Tag Manager isn’t used on Eventbrite. Pixels are also disabled with embedded checkout in some regions, such as Europe and the UK.

Ticketmaster. Ticketmaster clients place tags through the pixel manager in TM1. MNTN’s Ticketmaster pixel guide walks through it: Marketing tab, Add New, Pixel, then pick page types such as Event Detail Page and Confirmation Page-Primary or Confirmation Page-Resale. TikTok’s Ticketmaster pixel guide documents a Complete Payment event on the confirmation page with value (sum of face value), currency and quantity, and says no PII or Add to Cart data is shared. The practical catch for a touring show: the TM1 account often belongs to the venue or the promoter, so you may need them to place your tags. Ticketmaster’s self-serve tools also include came-from codes for source tracking, per Ticketmaster Business.

Universe. Per Universe’s Meta pixel guide, a Pixel ID is required and a Conversions API token is optional. If you use Universe’s embedded widget on your own site, you need both the Meta base code and Universe’s listener script, or the widget’s events won’t be captured.

Etix and AXS. Etix’s reporting and analytics page describes viewing “the entire patron purchase funnel, from your website to Etix.com, through your own Google Analytics account.” We couldn’t find current public documentation for Meta pixel or Conversions API support on Etix, or for client-side tag support on AXS, so we won’t guess. Use the questions in the checklist below and get the answers in writing.

Pixel plus Conversions API, and why you want both

A browser pixel depends on the buyer’s browser cooperating. Ad blockers, privacy settings and in-app browsers all drop events. The Conversions API sends the same purchase from the ticketing platform’s server, which those blockers don’t touch.

When both run, Meta needs to know they’re the same purchase. Per Meta’s deduplication docs, the pixel’s eventID must match the server event’s event_id, and the event names must match; events are only deduplicated if they arrive within 48 hours of the first one with that ID. On a ticketing platform that handles both sides for you (Eventbrite and Universe both describe server-side as an add-on to the pixel), you don’t set the IDs yourself, but you should still check Events Manager for duplicate purchase counts after turning it on.

The value matters as much as the count. Meta’s Meta’s standard events reference lists currency and value as required parameters for the Purchase event. Without value, you can’t see return on ad spend in Ads Manager, and you can’t optimize for value. Test it with a real order and look at the event details in Events Manager’s Test Events tab before you spend a dollar.

GA4 cross-domain tracking when the checkout lives somewhere else

Most tours send buyers from their own site (city pages, date finders) to a ticketing domain to check out. Without cross-domain measurement, GA4 sees the jump as a new user arriving from a referral, and the original ad click gets lost.

Per Google’s cross-domain measurement help, the setup is Admin, Data collection and modification, Data streams, select your web stream, Configure tag settings, Configure your domains, then add each domain. The linker passes IDs in a _gl URL parameter. The tag on every domain must use the same G- tag ID from the same web data stream.

That last requirement is where ticketing platforms get tricky. You can only do true cross-domain tracking if you can put your own GA4 tag on the ticketing pages. Some platforms let you add a GA4 measurement ID (Eventbrite does). Others won’t. Google also warns that redirects or pages that strip query parameters can drop _gl, and that JavaScript-driven navigation isn’t covered, so test the full path from your city page into checkout and confirm the parameter survives.

If you can’t get your tag onto the checkout, add the ticketing domain to GA4’s unwanted referrals list (also under Configure tag settings) so it isn’t credited as a traffic source, mark clicks on your “Buy tickets” buttons as an event, and rely on UTMs and the ticketing platform’s own source reports for sales. Our GA4 and Google Ads conversion guide covers marking events as key events and importing them.

Passing purchase value, and deciding what revenue means

Decide once, across the whole tour, which revenue number counts. Then make sure every platform reports that one, or note clearly which one it reports.

For media decisions, face value or order total is fine as long as it’s consistent. For return on ad spend at settlement, use net from the ticketing report and divide by total ad spend. Two other settings to check in Google Ads: count every conversion for purchases (not one per click), and use the value passed by the tag instead of a fixed value.

UTMs and naming for a multi-city tour

UTMs are the boring backbone. When pixels fail, the ticketing platform’s source report and GA4 still show where buyers came from, as long as the links were tagged.

Google’s Google’s URL builder help lists the supported parameters (utm_source, utm_medium, utm_campaign, utm_id, utm_term, utm_content and utm_source_platform) and notes that values are case sensitive, so Facebook and facebook become two sources. Use lowercase everywhere.

A convention that works for tours: utm_source=meta, utm_medium=paid_social, utm_campaign=tour26_tulsa_lastchance, utm_content=dino_reveal_15s. City and phase in the campaign, creative in the content. Keep the list in a shared sheet and generate links from it.

Ticketing platforms have their own source tools that sit beside UTMs. Eventbrite’s tracking links report page views, tickets and sales per link, with sales reported immediately. Ticketmaster has came-from codes. Use them for creators, partners and the venue’s email, where you want sales per partner without relying on a pixel.

Offline sales, box office and manual uploads

Box office walk-ups, group sales and phone orders never fire a pixel. On a family show with heavy school-group business, that can be a meaningful share of revenue. You can still send them back to the ad platforms, as long as you collected an email or phone number and have permission to use it for this.

Google Ads. Google’s offline conversion import help describes saving the Google Click ID (GCLID) with the customer record and importing it later with the conversion. Google now recommends enhanced conversions for leads, which matches on hashed customer data like email, and points to Data Manager as the quickest setup. For ticketing, this works best for group sales that start with a form on your site.

Meta. The separate Offline Conversions API was discontinued in May 2025, per Jon Loomer, and offline events now go through the main Conversions API. Meta’s server event parameters lists action_source values including physical_store and phone_call, and says events can be sent up to seven days after they happen; send a request with anything older and the whole request errors. Upload at least weekly.

For most touring shows, a weekly CSV of group and box office orders through a connector is plenty. Don’t build a custom pipeline until you know that slice is big enough to matter.

Attribution windows, and why short ones suit ticketing

Each platform credits a purchase within its own time windows after someone clicks or sees an ad.

Ticket buying is compressed. Most purchases happen within days of the decision, and late in the cycle. Shortening Google Ads’ purchase window to 7 days brings it closer to Meta’s and stops campaigns from claiming credit for a click five weeks before the show. Whatever you choose, use the same windows across every city on the tour, and write them on the report so nobody compares a 30-day number to a 7-day one.

View-through and engage-through purchases are real but generous. We report them separately and judge prospecting on click-through plus the blended numbers below.

Reconciling platform-reported vs. ticketing-reported sales

Once a week, per city, line the numbers up. It takes 20 minutes with a decent sheet.

Three metrics do most of the work:

• Tracking coverage = ad-platform purchases (click-through only) ÷ online orders in the ticketing report. It tells you what share of orders your pixels see. Track it over time; a sudden drop usually means a broken tag, not a bad campaign.
• Blended cost per order = total paid spend in the city ÷ all online orders in the city. Ad-platform cost per purchase flatters or punishes campaigns depending on tracking. Blended cost doesn’t care.
• Media efficiency ratio = ticketing revenue in the city ÷ total paid spend in the city. Same idea, in revenue terms.

For a bigger question (is this channel actually adding sales?), run a holdout. Pick two comparable cities on the route, keep everything identical except one channel, say streaming TV, and compare pace and blended cost per order. It’s not a lab experiment, but it beats arguing about attribution.

A reporting template you can copy

One row per city per week. Keep spend and ad-platform columns on the left, ticketing columns on the right, and the calculated columns at the end.

Illustrative example. Note that the coverage formula adds Meta and Google purchases, which can double-count a buyer who clicked both; read it as a trend, not a precise share. The pace index compares tickets sold to where the same date stood on past runs at the same number of days out; our guide to selling more event tickets covers building that curve.

Test before every on-sale, and mistakes we see

Before each city’s on-sale, buy a real ticket through a real ad click. Watch Meta’s Test Events tab and Google’s Tag Assistant while you do it, then confirm the purchase shows the right value and currency and appears once, not twice. Refund yourself after. Our Houston event ticket post has the hidden $1 ticket version of this for platforms that allow it.

The mistakes we see most:

• Pixels placed on the event page but not the confirmation page, so purchases never fire.
• A new event created by copying an old one, but pixel scope set to “this event only,” so the new city has no tracking. Eventbrite notes that event-only pixels don’t carry over when an event is copied.
• Value missing from Purchase, so nobody can see return on ad spend.
• UTMs typed by hand in mixed case, splitting one source into three.
• Comparing Meta’s 7-day click number to Google’s 30-day click number as if they were the same thing.
• Waiting for the venue to place tags on Ticketmaster until the week of on-sale.
• Judging a city by ad-platform purchases when the ticketing report says something else.

Our guide to marketing metrics goes broader on what to report, and our search marketing team sets up the Google side. If your tour’s numbers don’t line up and you want a senior strategist to build a tracking and reporting plan around your ticketing platform, get in touch.

Frequently asked questions

Can I put a Meta pixel on Ticketmaster?

Ticketmaster clients place marketing tags through the pixel manager in TM1, under the Marketing tab, choosing page types such as the event detail page and the confirmation page. Access usually sits with the venue or promoter that holds the TM1 account, so a touring show may need them to place its tags. Confirm which tag types and server-side options your account supports with your Ticketmaster rep before on-sale.

Does Eventbrite support the Meta Conversions API?

Yes. In Eventbrite’s Tracking pixels settings under Marketing, you add your Meta pixel ID and can switch on server-side tracking by pasting a Conversions API access token from Meta Events Manager. The pixel fires PageView and Purchase by default, and you can map extra standard events. Eventbrite notes you cannot verify its domain with Meta, so a few Meta features may be unavailable.

Why does Meta report more ticket purchases than my ticketing platform?

Meta counts purchases within its attribution windows, including one-day view-through and engage-through, so it can credit sales that other channels also claim. Your ticketing platform counts every order once, including ones from email, organic search and the box office. Compare Meta’s click-through purchases with online orders in the ticketing report, and judge overall results on blended cost per order.

How do I track ticket sales in GA4 when checkout is on another domain?

If you can add your own GA4 tag to the ticketing pages, set up cross-domain measurement under Admin, Data streams, Configure tag settings, Configure your domains, using the same G- tag ID on both sites. If the platform won’t accept your tag, exclude it as a referral, track Buy tickets clicks as an event, and use UTMs plus the platform’s own source reports for sales.

Can I upload box office or group ticket sales to Meta and Google?

Yes, if you collected contact details with permission. Meta now takes offline events through the main Conversions API, with an action source such as physical_store, and events must be sent within seven days. Google Ads supports offline conversion imports using the Google Click ID, and recommends enhanced conversions for leads set up through Data Manager. A weekly upload is enough for most tours.

Written by Sean Melton

Sean Melton is the founder of First Byte, a digital marketing agency in The Woodlands, TX. A former global CMO of a $250M software company, he has spent his career inside the businesses he markets. His team runs paid social, search, CTV and creative for brands like Equinox, Kroger and Viceroy, and shares what works here.