Connect your own Meta, Google, or TikTok pixel to your events. We report the page view, the ticket added, the checkout started, and the purchase, with the ticket revenue you keep.
Spring Gala
Saturday, May 9 · The Fairmont
An illustration of one buyer's path. Every event shown is one the product really sends, with the parameters it really carries. Nothing on this page fires a pixel.
Every organizer here sells through the same cart, the same checkout, and the same order confirmation page. On most platforms that is the reason you are told you cannot have your own pixel. It is a solvable problem, and this is how it is solved.
We read the tickets in the cart back to the event, and the event back to the organizer who owns it. Not the referrer, not a cookie, not the last page someone visited.
Your Meta event names your pixel specifically. Another pixel loaded on the same page, including ours, does not receive it.
Buyers hold tickets from one organizer at a time, so a cart always belongs to exactly one of you. There is no moment where two sellers share a basket.
No names, no email addresses, no phone numbers, no billing addresses. The events carry your event ID, a ticket count, and the amount.
You paste a pixel ID and we build the tag. There is no field anywhere that accepts markup, so nothing you save can run code on a buyer's screen.
An ID that does not match the shape that network issues is refused on save and never goes live, so a typo shows up as a message rather than as silence.
Hand this table to whoever runs your ads. It is the whole contract: what we send, when we send it, and what it is called on their side.
| What the buyer did | Meta | Google Analytics 4 | Google Ads | TikTok |
|---|---|---|---|---|
| Event page viewed | ViewContent |
view_item |
not sent | ViewContent |
| Ticket added | AddToCart |
add_to_cart |
not sent | AddToCart |
| Checkout started | InitiateCheckout |
begin_checkout |
not sent | InitiateCheckout |
| Order confirmed | Purchase |
purchase |
conversion |
CompletePayment |
Google Ads receives the purchase only. Its earlier steps are separate conversion actions you create yourself, so sending them would record them against the wrong one.
Each row on the settings screen takes one validated ID and nothing else. There is no field that accepts a script, which is why this can be self-serve at all.
Facebook and Instagram ads
Meta renamed the Pixel ID to Dataset ID. It is the same number it has always been, and Events Manager shows it at the top of your dataset.
Traffic and funnel reporting
Sits under Admin, Data streams. Your ticket sales land in the same reports as the rest of your website traffic.
Search and YouTube campaigns
Google Ads needs both halves. The label is the short code after the slash in the tag it gives you, and without it the conversion is recorded against nothing.
TikTok campaigns
TikTok Events Manager shows it beside the pixel name. Paste the ID itself, not the code block around it.
There is no review queue, no verification call, and nothing to install on your own website. The screen lives in Organizer Tools under Tracking Pixels.
Open your ad platform and copy the pixel or measurement ID. Meta calls it a Dataset ID, Google calls it a Measurement ID or a Conversion ID, TikTok calls it a Pixel ID.
Go to Organizer Tools, then Tracking Pixels. Pick the network, paste the ID, and choose whether it covers all of your events or one of them.
Open your event page with Meta Pixel Helper or your platform's test tools running. The first event shows up on that first page view.
Return on ad spend is only useful if the revenue half of it is real. A platform that reports the buyer's total is counting its own fees as your income, and every campaign looks better than it is. We report the ticket revenue that reaches you. If you pass our service fee to your buyers, it was never yours and it is not counted. If you absorb it, it is subtracted.
Worth reading before you turn it on, because these are the four things people assume and we would rather say them out loud than let someone find out later.
Ad platforms will happily accept a buyer's email address to improve matching. We do not send one, so a sale reaches your ad account with no way to trace it back to a person.
There is no aggregate mode, no platform-wide audience, and no setting that would let one organizer's pixel see another's sale.
The screen takes IDs. If a network you use is not one of the four, ask us rather than looking for a place to paste a tag, because there is not one.
Browsers, extensions, and privacy settings block tracking pixels for a real share of buyers. Your Ticket Falcon reports are the truth about how many tickets you sold. Your ad account is the truth about which campaigns are working.
Most organizers set one pixel and forget it. If you run campaigns for a client, a chapter, or a single flagship event, you can be more precise than that.
Run Meta and Google together, or a separate pixel per client. Six rows, each independent, all on one screen.
Scope a pixel to everything you sell, or to a single event, so one campaign's data never mixes with another's.
Name a row "Fall gala, agency account" and the next person to open the screen knows what it is for without asking you.
Pause a pixel between campaigns without losing the ID and having to hunt for it again in three months.
The order confirmation page is bookmarked and refreshed constantly. Purchase carries a deduplication ID and is recorded as sent, so a reload cannot inflate your results.
No review, no approval, no waiting on us. Save the row and the next visitor to your event page is measured.
Attribution inside Ticket Falcon, by promoter, poster, or channel. Useful for the sales your ad platform will never see.
Explore marketing toolsThe revenue your pixel reports is money already on its way to your own Stripe account, not a balance someone else is holding.
Explore Direct PayoutsNeed the same sale in your CRM or data warehouse rather than an ad account? Take it server to server instead.
Explore the Developer APIWondering what any of this costs? Nothing extra. It is included on every account, and the ticket fees are on the pricing page.
Paste one ID and your next event page view lands in your own ad account.