Server-side · Meta CAPI
Meta Conversions API + TrackPlay
Browser pixels get blocked, and iOS drops them. A conversion that never reaches Meta cannot train Meta.
Server-side Meta CAPI
How it works
Copy
POST graph.facebook.com/events
1
Sent from our server
TrackPlay posts the event to graph.facebook.com with your system-user token. It does not depend on the viewer's browser.
Signalsserver
Watch milestoneViewContent
CTA clickViewContent
Hot viewer, no buy yetHotLead
2
Watch-time signals Meta can train on
Watch milestones and CTA clicks reach Meta as ViewContent events, and hot viewers who did not buy yet arrive as a custom HotLead event you can build audiences and lookalikes on.
user_datahashed
Email, phone, namesha256
fbc / fbp click idattached
Raw PII to Metanever
3
Match quality without exposing your list
Emails, phones, and names are SHA-256 hashed before they leave our server. The click id from the ad that started the session rides along, so the sale lands on the exact campaign that earned it.
Meta CAPI questions
Yes. When your cart posts a sale back, TrackPlay sends a Purchase event to Meta server-side with value and currency.
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.
Yes. Delivery is server to server, from TrackPlay to graph.facebook.com with your system-user token. Ad blockers and iOS privacy features do not touch it.
The click id (fbc and fbp) captured on the session is attached to the server event, alongside SHA-256 hashed email, phone, and name.
Two fields: your Pixel ID and a Conversions API system-user access token from Meta Events Manager. Optionally add a test event code and watch events arrive in the Test Events tab.
The rest of your stack
TrackPlay talks to the tools you already sell with.
Browse all integrations ▶See which video earned the sale.
Free plan, 1,000 plays a month, no card.
Free plan. No card required.