Meta Conversions API — flawless tracking

When you connect your Meta Pixel to BrightStar, ticket sales get tracked from inside the visitor's browser the moment someone completes checkout. That's the standard setup, and it works — until a browser doesn't cooperate. Ad blockers strip the pixel call before it fires. iOS privacy limits cut it off partway through. Cookie restrictions in some browsers stop Meta from matching the visit to the eventual sale. Put together, browser-only tracking misses roughly 20 to 30% of the conversions that actually happened.

The Conversions API, or CAPI, closes that gap. Alongside the browser pixel, BrightStar also sends the same event to Meta server-side, straight from BrightStar's own servers rather than the visitor's device. Nothing about it changes what a buyer sees or does at checkout — it's a second, more reliable copy of the same information, sent in a way that ad blockers and browser settings can't touch. It's optional, but if you're running Meta ads for your events, it's the difference between an Ads Manager that shows most of your sales and one that shows all of them. You turn it on once, by generating a token in Meta and pasting it into BrightStar.

Picture running an ad for a weekend meditation retreat. Someone taps it on their iPhone, browses your event page, and buys a ticket ten minutes later in the same session. If iOS's privacy limits or an ad blocker interfere with the pixel call, Meta never learns that click turned into a sale — even though it did. Multiply that across every iOS visitor, every ad-blocker user, and every browser with strict cookie rules, and you can see why the shortfall lands at 20 to 30% rather than being a rare edge case.

That gap doesn't just under-report — it distorts decisions. A campaign that's actually converting well can look mediocre in Ads Manager if browser tracking is the only signal reaching Meta, which makes it harder to tell which ads are worth your budget. Sending the same event server-side, through CAPI, doesn't require the buyer's browser to cooperate at all, so it catches the sales the pixel alone would have missed, without adding any extra step for the buyer at checkout.

Adding the Conversions API token isn't required to sell tickets or run ads through BrightStar. Without it, your Meta Pixel keeps tracking from the browser as it always has, and that tracking is the default setup — it works, and plenty of organizers run on it without issue. What CAPI adds is completeness: it recovers the slice of real sales that browser tracking alone can't see, so your Ads Manager reflects what actually happened rather than what happened to survive an ad blocker or a browser's privacy settings. If you're not running paid Meta ads, or you're just getting started, there's no urgency — you can always come back and paste the token in later, and server-side sending switches on the moment both your Pixel ID and token are saved together.

Your Conversions API token functions like a password: whoever holds it can send events to your Meta ad account, so BrightStar treats it accordingly. Once you paste it in and save, BrightStar never shows it back to you — not in the dashboard, not anywhere in the browser. The field itself works like a password input, so even if you reopen the Meta Pixel tile later, you'll see the connection marked as saved rather than the token itself.

If you ever want to rotate the token, generate a fresh one in Meta Events Manager the same way you did originally, and paste it into BrightStar in place of the old one.