Meta Conversions API + TrackPlay
Browser pixels get blocked, and iOS drops them. A conversion that never reaches Meta cannot train Meta. TrackPlay sends it from our server.
Watch-time signals Meta can train on
TrackPlay posts events to graph.facebook.com with your system-user token. The click id from the ad rides along, so the sale lands on the campaign that earned it.
- Emails, phones and names are SHA-256 hashed before they leave our server
- Ad blockers and iOS privacy features do not touch it
- Hot viewers who have not bought arrive as a custom HotLead event
Live in three steps
Two fields from Meta Events Manager.
Copy your Pixel ID
From Meta Events Manager.
Create a system-user token
A Conversions API access token. Paste both into Integrations.
Check the Test Events tab
Optionally add a test event code and watch events arrive.
The events Meta receives
Sent server to server, with value and currency on purchases.
Purchase- Your cart posts the sale back
Lead- A lead is captured
ViewContent- CTA clicks and watch milestones
HotLead- A hot viewer has not bought yet (custom event)
Works with the rest of your stack
Every ad platform gets the same sale. Browse all integrations
Meta CAPI questions
Does TrackPlay send conversions to the Meta Conversions API?
Yes. When your cart posts a sale back, TrackPlay sends a Purchase event to Meta server-side with value and currency.
What Meta events does TrackPlay send?
Purchase on a cart postback, Lead on a lead capture, ViewContent on CTA clicks and watch milestones, and a custom HotLead event for hot viewers who have not bought yet.
Does TrackPlay work without the Meta browser pixel?
Yes. Delivery is server to server. Ad blockers and iOS privacy features do not touch it.
How does the sale get matched to my ad?
The click id (fbc and fbp) captured on the session is attached to the server event, alongside SHA-256 hashed email, phone, and name.