Meta sees the sale
Your store reports ViewContent, AddToCart, InitiateCheckout and Purchase. Adds to bag, checkouts and purchases are sent from the shopper's browser and from your server with the same event id, so Meta counts each once and still gets the sale when a browser blocks the Pixel.
- A purchase is reported once, with the order as its id, so reloading the thank-you page cannot count it twice.
- Only for a purchase, your server sends hashed contact details (SHA-256) to help Meta match the sale, never plain values.
- Staff, theme previews and bots are never tracked.
You see which campaign sold
Tag your ad links with utm_source, utm_medium and utm_campaign and your own analytics shows visits, orders and revenue per campaign, for Meta, Google and TikTok links. It complements Meta's reporting and does not replace it.
Asks before it tracks
By default a small Accept / No thanks bar appears and nothing is sent to Meta or Google until the shopper accepts. Google Analytics 4 and Tag Manager are set up on the same screen. Ad tracking is included on selected plans.
Questions, answered.
Do I use my own Pixel? +
Yes. Each store pastes its own Pixel id (and, for server-side sending, its own access token), so the data stays in your ad account.
Why send events from the server as well? +
Browsers and ad blockers can stop the Pixel. A server copy with the same event id lets Meta count the sale once and not lose it.
Can I check it works? +
Yes. A read-only connection test asks Meta whether the Pixel is reachable, and a test code sends events to Events Manager only.
Is it on every plan? +
No. Ad tracking is included on selected plans; the pricing page shows which.