Server-side tracking is a way of sending conversion data from a server you control, rather than from code running in the visitor's browser. For Meta ads, the server sends events such as purchases to Meta's Conversions API, usually alongside the Meta Pixel.
Client-side and server-side tracking
| Client-side (browser) | Server-side | |
|---|---|---|
| Where the code runs | The visitor's browser or phone | A server you or a partner control |
| Example in Meta | The Meta Pixel | The Conversions API |
| Who shapes the data | Each tag sends data to its own vendor | You decide what is sent and where |
| Events it can send | Website actions | Website, app, offline, CRM and messaging events |
| Setup | Add a tag to the site | A platform integration, a partner or a developer |
Let Madgicx's AI do the work
Its AI marketer finds what's working and prepares the next move. You approve.
Try for Free ($0 Trial)How it works
Google's introduction to server-side tagging explains the model well. A typical setup runs tags in the page, and each sends data to its own collection server. A server container runs on a server you control instead. Only you can access its data until you send it on.
The server receives requests from the visitor's device, turns them into events and routes them to each destination. For Meta, that destination is the Conversions API.
Meta says server events are processed like Pixel events, so they can feed measurement, reporting and optimization. Meta's Help Center calls the Conversions API a more reliable connection between your marketing data and Meta.
Server-side tracking options for Meta
Meta's comparison of setup options gives four routes:
| Route | What it is | Cost and effort |
|---|---|---|
| Meta-enabled Conversions API | A web-only server connection that runs alongside your Pixel | Free, one click |
| Commerce platforms | Shopify, WooCommerce, Wix or BigCommerce | No additional cost, a few clicks |
| Partners | Google Tag Manager, Adobe, Tealium and others | Depends on the partner |
| Direct integration | Your own server code calling the API | A developer, 2 to 4 weeks for a new integration |
Keep the Pixel running. Meta recommends a redundant setup that sends the same events from browser and server. Meta deduplicates them when the event name and event_id match.
How to set it up
- Choose a route: the Meta-enabled option, your store platform, a partner or a direct integration.
- Use the same Pixel ID for browser and server events.
- Send the same event_id from both sources, so Meta counts each conversion once.
- Send customer information with each event, and watch Event Match Quality. Meta rates it from 0 to 10 based on the last 48 hours.
- Compare server-tracked purchases with your store's orders for the same days.
Benefits and trade-offs
- Control. You decide what data leaves your server and where it goes.
- Reach beyond the website. Events from your app, CRM, store or billing system can reach Meta.
- Effort. A direct integration needs a developer and ongoing maintenance, and partner costs vary.
- Deduplication. If event IDs don't match, conversions are counted twice.
- Consent still applies. Send only the data you are allowed to share.
Example. A subscription business tracks web sign-ups with the Pixel. Renewals happen in its billing system, where no browser is involved. It sends those renewals to Meta from its server, so Meta can optimize for paying customers, not just sign-ups.
In Madgicx. Madgicx's conversion tracking sends your conversions to Meta from a server, so they don't rely on the browser alone.
FAQ
Is server-side tracking the same as the Conversions API?
No. Server-side tracking is the general method of sending data from a server. The Conversions API is Meta's endpoint that receives those server events.
Do I still need the Meta Pixel with server-side tracking?
Yes, Meta recommends keeping the Pixel. Meta's redundant setup sends the same events from the Pixel and the server, then deduplicates them.
Is server-side tracking hard to set up?
No, not always. Meta's one-click option and commerce platform integrations need no developer. A direct integration does, and Meta estimates 2 to 4 weeks for a new one.
Does server-side tracking work with Google Tag Manager?
Yes. Google Tag Manager offers server containers that run on a server you control, and Meta lists Google Tag Manager among its Conversions API partners.
What events can server-side tracking send to Meta?
Server-side tracking can send website, app, offline and business messaging events to Meta through the Conversions API.
Related
Sources
- An introduction to server-side tagging, Google for Developers
- Conversions API overview, Meta for Developers
- Meta's developer page on deduplicating Pixel and server events, Meta for Developers
- About Conversions API, Meta Business Help Center
- Compare Conversions API setup options, Meta Business Help Center
- Meta's help page on Event Match Quality, Meta Business Help Center
