When you post an event to Instagram or boost a kirtan announcement on Facebook, you can usually see how many people tapped through and, days later, how many tickets sold. What happens in between — who lingered on the event page, who picked a ticket type, who reached checkout and left — stays invisible. BrightStar closes that gap. Every stage of the ticket funnel on your event page is reported back to Meta, so Facebook and Instagram learn which of the people who saw your ad actually became buyers, and can go looking for more people who look like them. There is nothing to install and nothing to configure on your event page: the tracking is built into the page itself, into the checkout, and into the confirmation screen a buyer sees once payment clears.
What are the four moments BrightStar reports to Meta?
BrightStar reports four moments in a buyer's path, and each one corresponds to a standard Meta signal. These four are the ones Meta's ad optimisation is built around, which is why Meta can act on them without any custom setup on your part — no event naming, no manual pixel placement, no guessing which button on your page should count as a conversion.
Why does BrightStar use two pixels, and why doesn't the data get mixed up?
Each event on your ticket funnel resolves its own set of pixels before it is sent. BrightStar's own pixel always fires, which means an organizer who has never touched Meta advertising still gets working conversion data from day one — you don't lose anything by not having connected an account. If you have connected your own Meta pixel to your BrightStar account, it is added alongside BrightStar's pixel for your events, so the same conversions also show up in your own Ads Manager, under your own account, where you can build audiences and campaigns against them.
The two pixels don't blur into each other. BrightStar sends each event to each pixel individually rather than broadcasting it to whatever happens to be loaded on the page. That matters at a gathering-heavy moment like festival season, when a visitor might browse several different organizers' event pages in one sitting — a ticket bought on your page should never leave conversion data sitting in a different organizer's ad account, and it won't.
Why is every funnel event sent twice?
Each of the four funnel events is sent to Meta twice, on purpose: once from the visitor's own browser, and once from BrightStar's servers through Meta's Conversions API. The browser copy is the fast one, arriving the moment the action happens. The server copy is the one that still gets through when an ad blocker, a private browsing mode, or an in-app webview — common on a phone opened straight from an Instagram story — swallows the browser call before it ever reaches Meta.
Sending the same event twice would normally risk double-counting a sale. BrightStar avoids that by having the server copy reuse the same identifier the browser copy already fired with, so Meta recognizes the pair and collapses them into a single event rather than two. Any contact detail included in that server-side call is hashed before it leaves BrightStar, so nothing readable is transmitted.
What happens after someone buys a ticket?
A completed purchase does more than log a conversion — it changes who sees your ads next. The buyer is added to an exclusion audience, so someone who already holds a ticket to your kirtan evening or your weekend retreat stops being shown ads for that same event. Without this, a long selling window means you can end up paying to advertise an event to people who bought in the first week and are still scrolling — money that would do more good reaching someone who hasn't bought yet.