Server-Side Tracking Explained: How to Set Up Conversion APIs for Meta, Google, and TikTok

A browser-only pixel now captures roughly 65 to 80 percent of actual conversions, depending on the platform.

iOS App Tracking Transparency, Safari’s Intelligent Tracking Prevention, ad blockers, and consent banners each suppress browser events before they ever reach Meta, Google, or TikTok, and on some platforms the combined block rate runs as high as 35 percent.

Server-side tracking is the fix, and it’s foundational infrastructure that has to be right before any conversation about attribution, AI optimization, or first-party data means much of anything. Here’s how it works and how to set it up across all three platforms.

What Server-Side Tracking Actually Is

In a standard client-side setup, the browser sends a separate request to every vendor directly, one to Meta, one to Google, one to TikTok, each of which can be blocked independently.

Server-side tracking routes that data through a server you control first. The browser sends a single request to your own domain, and your server forwards the relevant data to each platform’s Conversions API or Events API.

Because the connection between the browser and your domain is first-party, it survives ad blockers and browser privacy restrictions that specifically target third-party tracking requests.

The One Rule That Applies to All Three Platforms: Deduplication

If you’re running both a browser pixel and server-side tracking for the same platform, every conversion fires twice, once from the browser, once from your server.

Without deduplication, each platform counts both, inflating your reported conversions and quietly corrupting whatever optimization decisions get made on top of that number.

The fix is identical across Meta, Google, and TikTok: generate a unique event_id for each conversion, pass that same event_id to both the browser event and the server event, and the platform will match them and count the conversion once. Get this wrong and every other part of your setup, no matter how well configured, is reporting inflated numbers.

Setting Up Meta Conversions API (CAPI)

Locate your dataset ID in Meta Events Manager, the same numeric ID that used to be called your Pixel ID.
Choose an implementation method: a direct server-to-server integration, a CAPI Gateway that automatically mirrors Pixel events, or a Meta tag inside a Google Tag Manager server container.
Generate a shared event_id for each conversion and pass it to both the Pixel event and the CAPI event, with matching event_name values on both sides.
In Events Manager, confirm key events like Purchase show both Browser and Server sources, and check the deduplication rate. Above 90 percent is the target; below that means event_id isn’t matching correctly.
Point your integration at a current Graph API version and plan to update periodically. Meta shipped Graph API v25.0 on February 18, 2026, and events sent on a deprecated version can quietly stop being accepted.

Setting Up Google Server-Side Tagging (sGTM)

In Google Tag Manager, create a new container and set its type to Server, separate from your existing web container.
Deploy the server container on Google Cloud Run or App Engine, choosing a region close to your primary audience to minimize latency.
In your existing web container, add the server container’s URL as the transport URL on your Google tag, so browser events route through your server first.
Configure server-side tags for GA4 and Google Ads inside the server container, mirroring the events you already send client-side.
Test using GTM’s debug mode on both containers before going live, confirming events arrive at the server and forward correctly to each destination.

Setting Up TikTok Events API

Find your TikTok Pixel ID in TikTok Ads Manager under Assets, Events, Web Events, connected to your Business Center account.
Choose an implementation path. TikTok’s native Shopify app sends browser-pixel events only, no server-side calls by default, so most ecommerce teams use a third-party app or a custom GTM server-side setup for full coverage.
Generate the event_id server-side at the moment of conversion, a UUID or a hash of order ID plus timestamp works, and push that same value into the browser pixel’s data layer before it fires.
Test using TikTok Events Manager’s Test Events tool before going live.
Monitor your deduplication rate after launch. Running Pixel and Events API together with proper deduplication typically lifts total conversion capture to around 95 percent, up from roughly 65 percent on browser tracking alone.

Common Mistakes That Quietly Wreck Server-Side Tracking

Mismatched event_id or event_name between browser and server. Even a small formatting difference breaks deduplication silently, and the first sign is usually inflated conversion counts weeks later.

Assuming server-side tracking means automatic compliance. GDPR, CCPA, and ePrivacy requirements still apply. Server-side tracking changes where data is processed, not whether consent is required.

Sending events on a deprecated API version. Platforms retire API versions on a rolling schedule, and events sent to a retired version can stop being accepted without an obvious error on your end.

Never checking the actual deduplication rate. A setup that looks complete in Events Manager can still be running below a healthy dedup rate if event_id isn’t matching consistently.

Where This Fits Into a Bigger Measurement Picture

Server-side tracking makes each platform’s own reported numbers more complete, and that matters. But it’s worth being clear about what it doesn’t do: CAPI being set up correctly and ROAS still looking wrong are not contradictory.

Better signal into Meta, Google, or TikTok improves what each platform can see and optimize against, but it’s still that platform’s own attribution logic making the call, including whatever view-through credit or attribution window it applies.

Server-side tracking and independent first-party attribution solve two different problems, one feeds the platforms, the other tells you what actually happened across all of them, reconciled into a single number instead of three platforms each claiming credit for the same sale.

If you’ve got server-side tracking in place and still can’t fully trust what your dashboards are telling you, book a live AdBeacon demo and we’ll show you the layer that sits on top of it.

—-

FAQ

Do I need server-side tracking if I already have the Pixel installed?

Yes. Browser-only pixels now miss roughly 20 to 35 percent of conversions due to ad blockers, iOS privacy restrictions, and consent banners. Server-side tracking recovers most of that gap and should run alongside your existing pixel, not replace it.

Is server-side tracking GDPR compliant automatically?

No. Server-side tracking changes where and how data is processed, but consent requirements under GDPR, CCPA, and similar regulations still apply. You need a compliant consent setup regardless of whether tracking happens client-side or server-side.

How long until I see results after setting up CAPI or Events API?

Most accounts see more complete conversion data in Events Manager within 24 to 48 hours. Actual campaign optimization improvements take longer, typically two to four weeks, since the platform’s algorithm needs to accumulate enough data from the improved signal to meaningfully adjust targeting and bidding.

Can I use the same event_id format across Meta, Google, and TikTok?

You can use a consistent generation method, such as a UUID or a hash of order ID plus timestamp, across all three, but each platform’s deduplication only matches events within its own system. The event_id doesn’t need to be identical across platforms, just consistent between the browser and server events sent to that specific platform.

Do I still need first-party attribution if I’ve set up server-side tracking?

Yes. Server-side tracking improves the data each platform receives about itself, but each platform still reports performance using its own attribution logic. Independent first-party attribution is what tells you what actually happened across all your channels combined, not what each platform claims individually.