Conversions API and server-side tagging: when they are worth it
Server-side tracking sends conversions from your server or a tagging server instead of only from the visitor's browser, so fewer are lost to ad blockers and browser limits. It is worth it once the browser setup is correct and you spend enough for a few percent more matched conversions to matter. It does not replace consent, and it doubles the places a purchase can be counted twice.
Published 2026-10-27
The three things people mean
- Meta Conversions API (CAPI): your server, shop platform or a partner integration sends events such as Purchase to Meta directly. Meta processes them like pixel events.
- Google enhanced conversions: the Google tag sends hashed (SHA-256) customer data, such as the email from the order, with the conversion so Google can match it to a signed-in account.
- Server-side Tag Manager: the browser sends one stream of data to a tagging server on your own domain, which forwards it to Google, Meta and others. You run and pay for that server.
What they improve
- Conversions that the browser never sent, because an ad blocker stopped the pixel or the visitor closed the tab on the confirmation page, can still arrive from the server.
- Better matching: hashed email or phone lets a platform tie a purchase to a person it showed ads to, which helps when click IDs or cookies are missing.
- Fewer scripts in the browser with server-side Tag Manager, and more control over what each vendor receives.
What they do not fix
- Consent. Sending data from a server does not remove the need for consent. Your server-side events need to follow the visitor's choice just as the pixel does.
- A broken browser setup. Server events usually start from what the browser sends. A missing purchase tag, wrong values or lost click IDs carry straight through.
- Duplicates. Pixel plus server means two copies of every purchase. Meta drops one only if both carry the same event name and event ID and arrive within 48 hours of each other.
Costs
CAPI through a shop platform's built-in integration (Shopify, WooCommerce and others offer one) costs nothing to run. Enhanced conversions is a setting plus the customer data your confirmation page already has. Server-side Tag Manager needs hosting, typically on Google Cloud Run or a managed provider, plus someone who maintains it; plan for a monthly bill and a few days of setup and testing.
A sensible order
- Get the browser setup right: tags fire, consent works both ways, purchase values and IDs are correct, click IDs survive redirects. The free scan checks all of this.
- Turn on your shop platform's CAPI integration and Google's enhanced conversions, with deduplication IDs set.
- Consider server-side Tag Manager once ad spend is high enough that a few percent more matched conversions pays for the server and its upkeep, or when you need control over what each vendor receives.
- After each step, compare daily platform purchases with shop orders (see why the numbers don't match) to confirm the share went up and did not double.
Run the free scan: it loads your page in a real browser, accepts and rejects the banner, follows redirects with test click IDs and reports what every platform received.
Check your own site
- Meta pixel checker
- Consent Mode v2 checker
- Ad pixel fires before consent or after "reject": how to fix it
Sources
- Meta: Conversions API
- Meta: Handling duplicate pixel and Conversions API events
- Google Ads: About enhanced conversions
- Google: An introduction to server-side tagging
- Google: Why and when to use server-side tagging
- Google: Set up server-side tagging with Cloud Run
Based on the platforms' public documentation; menus and names change, so check the linked pages if a step looks different.