When you list an event on BrightStar and you're also running Meta ads for it — a boosted post for a kirtan circle, or a retargeting campaign aimed at people who looked at your retreat page but didn't book — you need Facebook and Instagram to know what actually happened after someone clicked. That's the job of the Meta Pixel: it reports each step of a visitor's path, from landing on your event page to completing a purchase, back to Meta's ad systems so those systems can learn who to show your ad to next. BrightStar installs and configures this pixel on every event page automatically. You don't add a script, generate a pixel ID, or wire up individual conversion events by hand. Tracking is already running the moment your event page goes live, which matters because a pixel that starts recording late is a pixel with holes in its retargeting audience from day one.
The path BrightStar tracks from page load to purchase
BrightStar's pixel fires five standard Meta events, each tied to a specific moment in your ticket funnel rather than to a generic page visit. Together they let Meta distinguish someone who merely landed on your page from someone who looked at prices, started checkout, or actually bought — which is what makes retargeting and conversion reporting meaningful instead of just a raw visitor count.
- 1PageView fires when someone loads your event page, sending the event ID, event name, and category.
- 2ViewContent fires when they view the ticket section, sending the ticket IDs, prices, and currency.
- 3AddToCart fires when a ticket is added to checkout, sending the ticket ID, quantity, and value.
- 4InitiateCheckout fires when the checkout modal opens, sending the order value and number of tickets.
- 5Purchase fires when the order completes, sending the order ID, value, currency, and the tickets bought.
Why does BrightStar hash buyer data before sending it to Meta?
Purchase events are also sent server-side, straight from BrightStar to Meta, rather than relying only on the pixel script running in someone's browser. Before anything is sent this way, personal identifiers — email address and phone number — are SHA-256 hashed, so Meta receives a scrambled value it can match against its own hashed records rather than a readable email or phone number. This server-side path, run through Meta's Conversions API, is preferred over the browser pixel for exactly the situation you'd expect to lose data in: someone with an ad blocker, or a browser that quietly drops third-party tracking scripts. Because the event is posted directly from BrightStar's server instead of depending on a script loading in the visitor's browser, it isn't blocked, and BrightStar reports a match rate of 95% or better as a result.
How long does BrightStar's attribution window stay open?
BrightStar uses Meta's default attribution windows: seven days for a click-through and one day for a view-through. In practical terms, if someone clicks your ad and buys a ticket within a week, that sale is credited to the ad. If they merely saw the ad without clicking, and buy within a day, that's still counted. A purchase that happens further out than either window won't be attributed to that specific ad — which is one reason the retargeting events described above matter: they give Meta more touchpoints to work with, closer to the moment someone actually decides to buy.
What conversions are already set up, and can I add my own?
BrightStar auto-creates three custom conversions in your Meta account so you have usable campaign objectives from the start: BS_TicketPurchase for any ticket purchase, BS_EventPageView for an event page view, and BS_CheckoutStarted for an initiated checkout. These are built from the standard events above, so they're live as soon as your event page is. If you need something more specific — a high-value purchase over $100, a VIP ticket purchase, or a multi-ticket order — you build that yourself in Meta Events Manager, using the same underlying event data BrightStar is already sending.