Nº 18 · Integrations
Connect Meta Conversions API to SIGNL
Forward server-side revenue events to Meta. See what syncs, where it stops and how to set it up.
Applications open soon
See the whole workspaceWorks with Meta Conversions API
What it does
Forward server-side revenue events to Meta CAPI so the ad platform learns from richer data than the browser pixel captured.
Early use: Not yet proven against Meta's test event tool.
What syncs
What it covers
4- Server-side purchase forwarding
- Hashed PII match
- Ad-platform ROAS uplift
- Post-iOS14 recovery
Automation actions
3- Send to Meta CAPI
- Add to Meta Audience
- Remove from Meta Audience
What it does not do
- Refunds are not sent here. A refund is taken back in Google Ads only.
Set it up
Connect in SIGNL
- In Meta Events Manager, choose the pixel, then Settings, Conversions API, and generate an access token. Note the pixel id.
- Enter the pixel id and token and save. SIGNL checks the token can reach the pixel.
- Connected and proven: SIGNL has used it successfully.
Questions people ask
What does SIGNL send to Meta Conversions API?
To Meta Conversions API: Server-side purchase forwarding, Hashed PII match, Ad-platform ROAS uplift, Post-iOS14 recovery. Data moves one way, out of SIGNL.
How do I set up the connection to Meta Conversions API?
It takes 3 steps, listed above. The first: In Meta Events Manager, choose the pixel, then Settings, Conversions API, and generate an access token. Note the pixel id.
Where does the connection to Meta Conversions API stop?
Here is where the Meta Conversions API connection stops. Refunds are not sent here. A refund is taken back in Google Ads only.
How ready is the connection to Meta Conversions API?
Early use: the Meta Conversions API connection is built and switched on. Not yet proven against Meta's test event tool.
Can an automation start from or act on Meta Conversions API?
Yes. The builder offers 3 actions (Send to Meta CAPI, Add to Meta Audience, Remove from Meta Audience).
Keep going
All product names and logos belong to their owners. They identify integrations only and do not imply endorsement.