What you'll be able to do
- Classify any ticketing platform into one of three tracking tiers in five minutes
- Build the correct measurement setup for whichever tier you're stuck with
- Understand why your ticketing contract is secretly a marketing decision
The short version: DAS 100 taught you the machine runs on signal. Events marketing's defining technical problem: your checkout usually lives on a ticketing platform, and platforms sit in three tiers - full tracking access (your pixel + server-side events at checkout), partial (pixel yes, gaps and limitations), and walled garden (their checkout, their data). The tier determines your entire measurement architecture, which optimization events you can actually run, and how much reconciling you'll do against ticketing reports. Nobody puts this on the pricing page. It belongs in every platform negotiation you ever have.
The most expensive sentence in event marketing
"Oh, we can't install our pixel there."
Said three weeks after signing the ticketing contract, usually. The fee structure got negotiated, the payout schedule got negotiated, the scanner hardware got discussed at length - and the single variable that determines whether your ad machine can SEE ITS OWN RESULTS never came up. This module makes sure you're never in that meeting on the wrong side of the table.
If this is your first rodeo: recall the Module 3 (DAS 100) horror story - purchase-optimized campaign, checkout the pixel never touched, Meta optimizing toward people who like looking at websites. That story is not rare. It is the default state of events marketing until someone does this module's work on purpose.
The three tiers
TIER 1 - FULL ACCESS. The platform lets you install your Meta pixel AND send server-side events (CAPI) from their checkout, with purchase value and currency attached. Ticket Fairy, for example, supports full Meta pixel integration plus server-side conversion tracking when you add your access token, alongside Google Tag Manager and other ad-platform pixels (Ticket Fairy, 2026). Tier 1 means DAS 100's whole signal doctrine applies unmodified: Pixel + CAPI, dedup, EMQ above 7, purchase optimization on the table if budget allows.
TIER 2 - PARTIAL ACCESS. Pixel yes, with real limitations. Eventbrite is the canonical example, and worth understanding precisely because it's everywhere: you can add your Meta pixel ID through their self-service tracking tool - you create the pixel on Meta's side, not theirs - and by default the Purchase standard event fires on order confirmation with value and currency passed through (Eventbrite Help Center + Meta Business Help Center, accessed July 2026). Meta even offers a guided Eventbrite connection in Events Manager. But: Eventbrite itself notes pixels can't track every purchase - privacy settings and blockers eat events - and the well-documented failure mode is ROAS underreporting from cross-domain tracking limitations and iOS privacy restrictions, with the standard fix being CAPI running alongside the browser pixel (Ticket Fairy blog, Mar 2026). Tier 2 doctrine: install everything they allow, expect undercounting, reconcile weekly against the platform's own sales reports, and verify the Purchase event carries value - missing value parameters are a primary cause of underreported revenue (Ticket Fairy blog, Mar 2026).
TIER 3 - THE WALLED GARDEN. Their checkout, their data, no self-serve pixel. Some major music-world platforms operate this way - historically including closed-checkout players in the club/electronic space - because their model is being the destination and owning the discovery data. (Specific platforms move on this; the take-home Matrix tracks current status per platform with verification dates rather than this lesson asserting stale facts.) Tier 3 doctrine, and this is the module's core skill: optimize on what you CAN see. Your pixel lives on YOUR pages - so the campaign optimizes on landing page views or outbound clicks to the ticket link, and truth arrives via the platform's sales dashboard, reconciled against spend through the MER worksheet (DAS 100 Module 8). UTM every link so the platform's analytics (where offered) can at least attribute source. The machine learns on proxies; the settlement math stays honest.
›Go deeper: why walled gardens exist (know the other side of the table)
Closed platforms aren't being difficult for sport. Their pitch to venues and promoters is the platform's own audience - discovery, recommendations, their app's push notifications - and that pitch is powered by exclusively-held user data. Opening checkout to every promoter's pixel dilutes the asset. Understanding this makes you better in negotiations: a platform's tracking posture signals its strategy, and sometimes their marketing reach genuinely IS worth the data blindness for your use case. It's a trade, not a scam. Make it consciously.
The reconciliation habit (all tiers)
Whatever the tier, one ritual is universal: the ticketing platform's sales report is the truth; Ads Manager is the estimate. Weekly, per DAS 100 Module 8: platform revenue ÷ ad spend = MER. Tier 1 accounts get the luxury of decent in-platform attribution too; Tier 3 accounts live on MER entirely. Either way the settlement math is the same math.
Buyer data: the second question
Tracking is question one. Question two, ask it in every platform evaluation: do you get the buyer list? Emails, names, opt-in status - exportable, yours? Because DAS 100 Module 3 taught you buyer lists are inventory: synced custom audiences, seed lookalikes, the compounding asset that makes every next show cheaper. A platform that keeps checkout data AND the customer relationship is charging you twice. Some do. Know before signing.
From the field
A promoter running shows across two platforms - one Tier 1, one Tier 3 - asked us why the Tier 3 shows "performed worse." They didn't. The MER worksheet showed near-identical real efficiency; the Tier 3 campaigns just LOOKED broken in Ads Manager because purchases were invisible. The fix was reporting literacy, not strategy: LPV-optimized campaigns, UTM'd links, weekly reconciliation - and a calmer promoter who stopped almost firing a platform that was quietly doing fine. Sometimes the emergency is a dashboard.
Common mistakes
- Signing the ticketing contract before asking the pixel question (the most expensive sentence, above)
- Purchase-optimizing on a checkout your tracking can't see - the eternal classic
- Installing the pixel on Tier 2 and skipping CAPI, then treating the undercounted ROAS as truth
- Not verifying the Purchase event carries value and currency (primary cause of underreported revenue)
- Never exporting buyer lists because "the platform has them" - the platform having them is the problem
Take-home
Ticketing Platform Tracking Matrix - the living doc: platform-by-platform tracking tier, pixel/CAPI support, buyer-data export, verification date per row. Updated quarterly; the row you need before every contract.
Sources & dates
Eventbrite Help Center (accessed July 2026) · Meta Business Help Center, Eventbrite connection (accessed July 2026) · Ticket Fairy platform docs (2026) · Ticket Fairy blog on pixel tracking (Mar 2026)
Learn more
Optional extra credit. Nothing below is required for the quiz, the certificate, or the job - the full lesson is above. This is for the sickos who want more.
- Meta Business Help Center: the guided Eventbrite connection in Events Manager - if you're on Eventbrite, do this tonight
- Ticket Fairy's pixel-tracking guide (Mar 2026) - the CAPI-alongside-pixel fix, step by step