Server-side tracking

Server-side tracking sends conversion events from your server to ad and analytics platforms, instead of relying only on scripts in the visitor's browser.

What is server-side tracking?

Server-side tracking means a conversion event is sent to a platform like Meta, Google Ads, GA4 or TikTok from a server you control, rather than only from a pixel running in the visitor's browser. The browser may still record the visit, but the event that matters (a purchase, a booking, a signup) travels server to server.

Most platforms offer a dedicated endpoint for this: Meta has the Conversions API, Google Ads accepts offline conversion uploads, GA4 has the Measurement Protocol, and TikTok has the Events API.

Why browser-only tracking loses data

A browser pixel only reports what it can see. Ad blockers can stop the script from loading, browser privacy features can shorten cookie lifetimes, and the visitor can close the tab before the request finishes. Some conversions never happen in the browser at all: a Stripe payment confirmed later, a Calendly booking, or a deal closed in your CRM.

A server already knows about these events because it processed them. Sending them directly avoids the browser as a point of failure.

What server-side tracking needs to work well

A server event is only useful if the platform can tie it back to an ad click or a person. That means capturing click ids (such as gclid, fbc or ttclid) when the visitor lands, and sending hashed identifiers like email and phone with the event.

If you run a browser pixel and a server event for the same conversion, both need to carry the same event id so the platform can count it once. Without that, server-side tracking can inflate your numbers instead of fixing them.

How TracerKit handles it

TracerKit forwards conversions server-side to Meta Conversions API, Google Ads offline conversion upload, GA4 Measurement Protocol and TikTok Events API. It captures click ids on the landing hit, hashes email and phone with SHA-256 before storage, and shares an event id with the browser pixel so the pair dedupes. Conversions can also arrive by webhook from Calendly, Typeform, Stripe or any tool that can POST JSON.

See how TracerKit handles this: Server-side forwarding

Take a look →

questions

Asked and answered.

Does server-side tracking replace the browser pixel?+

Usually not. Most setups run both: the pixel captures on-site behavior and click ids, and the server sends the conversions that matter with better reliability. Deduplication keeps the overlap from being double counted.

Is server-side tracking the same as server-side GTM?+

No. Server-side Google Tag Manager is one way to do it, using a tagging server you host. Server-side tracking is the general approach of sending events from a server, whatever tool does the sending.

Does server-side tracking get around consent requirements?+

No. Consent rules apply to the data, not the transport. A server event should respect the same consent state the visitor gave in the browser.

related terms

Conversions API

The Conversions API (CAPI) is Meta's server-to-server endpoint for sending conversion events directly to Meta, alongside or instead of the pixel.

Event deduplication

Event deduplication is how ad platforms count one conversion once when the same event arrives from both the browser pixel and a server-side API.

Click IDs

Click IDs like gclid, fbclid and ttclid are URL parameters ad platforms add to ad links so a later conversion can be tied back to the specific click.

First-party tracking

First-party tracking loads scripts and sends events through your own domain, so browsers and blockers treat it as part of your site, not a third party.

Find out what your tags are really doing.

The free sweep shows every tracking script on a page, plus dead pixels, render-blocking tags and double-counting risks.

Start free Sweep your site free