What Conversions API (server-side tracking) means
Server-side tracking is more resilient to ad blockers and browser restrictions, which helps ad platforms optimize. It must respect user consent and privacy laws. It takes more setup than a simple browser pixel.
Why it matters for your website
Browser restrictions and ad blockers can stop pixels from reporting conversions, which leaves ad platforms guessing about what works. Sending conversion data from your server fills some of those gaps, giving better reporting and better ad optimization. It must be set up with consent and privacy in mind.
Example
A home goods store sends purchase events to Meta through both its browser pixel and the Conversions API, with matching event IDs so Meta does not count orders twice.
Tips
- Use event IDs so the platform can match and remove duplicate browser and server events.
- Only send data you have consent to share and that your privacy policy covers.
- Check event quality in the ad platform's event manager after setup.
Common mistakes
- Sending the same event from the browser and server with no deduplication.
- Passing unhashed personal data or data from people who opted out.
Questions about Conversions API (server-side tracking)
What is Conversions API (server-side tracking)?
Sending conversion data from your server directly to ad platforms instead of relying only on browser tags.
Do I still need the Meta Pixel if I use the Conversions API?
Meta recommends using both together. The pixel captures browser activity, while the Conversions API adds server events that may be missed in the browser.
Is the Conversions API hard to set up?
It depends on your platform. Many ecommerce platforms and tag tools offer built-in integrations, while custom sites may need developer help or server-side tagging.
