Tracking

Server-Side Tracking

In short

Server-side tracking sends conversion events from a server straight to ad platforms instead of the browser, so ad blockers and cookie limits matter less.

Also known as: server side tracking

Server-side tracking means conversion events are sent from a server directly to ad platforms such as Meta, TikTok or LinkedIn, rather than only from the visitor's browser. Because the data travels server-to-server, it is far less exposed to browser restrictions.

How does server-side tracking work?

With client-side tracking, the browser loads the ad platform's tracking pixel and fires events straight to it. With server-side tracking, the event first reaches a server, which enriches it and forwards it through an API: the Conversions API for Meta, the Events API for TikTok and the LinkedIn Conversions API for LinkedIn.

Personal data such as email or phone number is protected with hashing (SHA-256) before it leaves the server. The platform can still match it to user accounts, which raises your Event Match Quality.

Why does server-side tracking matter?

Browser-based measurement has been eroding for years. Ad blockers block known tracking domains, Safari's Intelligent Tracking Prevention caps script-set cookies at 7 days, and more people decline tracking. The result is signal loss: ad platforms see only part of your real conversions and optimise on a skewed sample.

Server-side tracking closes a large part of that gap. It is not a loophole, though. Without consent, marketing tracking should not happen on the server either.

Example

A visitor submits a contact form on your landing page while running an ad blocker. The browser pixel never fires. Your server still sends the Lead event to the Conversions API, including a hashed email and the click ID, so Meta can attribute it to the right ad. If the pixel did fire as well, deduplication makes sure the conversion is only counted once.

Pros and cons

  • Pros: less data loss, better campaign optimisation, more control over what is shared.
  • Cons: classic setups built on server-side GTM need a hosted server container, ongoing hosting costs and technical skills.

For the bigger picture, read why server-side tracking matters.

Server-side tracking with LeadSignal

LeadSignal gives you server-side tracking without running a server or a tag manager. You add one script, connect your ad accounts, and LeadSignal sends events server-side to the Meta Conversions API, the LinkedIn Conversions API and the TikTok Events API, in parallel with the pixel and automatically deduplicated. Google Ads is currently connected browser-side via the Google Tag with Enhanced Conversions. The guide on server-side tracking without GTM walks you through the setup.

Frequently asked questions

Is server-side tracking GDPR compliant?+

Not by default. Moving tracking to a server does not remove the need for consent for marketing purposes. It does give you more control over what data reaches ad platforms, for example through hashing and IP anonymisation.

Does server-side tracking replace the pixel?+

Usually not. The recommended setup runs the browser pixel and the server API side by side. Both send the same event ID so the platform deduplicates them and each conversion is counted once.

Do I need my own server for server-side tracking?+

Not necessarily. With Google Tag Manager you have to host a server container yourself. Tools like LeadSignal run the server infrastructure for you, so you only add one script to your site.

Guides on this topic

Privacy & Consent
GDPR-Compliant Tracking: Cookie Banner, Consent Mode v2 and Conversion Tracking Done RightGDPR-compliant tracking in plain English: what valid consent means, how Consent Mode v2 works and how to set up your cookie banner and conversion tracking.10 min read
Tracking
Server-Side Tracking Without Google Tag Manager: A Simpler sGTM AlternativeServer-side tracking setup without a server container: what sGTM really costs, when it is worth it, and a simpler way to connect Meta, LinkedIn and TikTok.11 min read
Tracking
Simple Conversion Tracking: How to Set Up Ad Tracking Without a Developer (2026 Guide)How to set up conversion tracking without a developer or Google Tag Manager: what simple tracking must cover, three setups compared and a step-by-step guide.10 min read

Articles on this topic

Related terms

TrackingClient-Side TrackingClient-side tracking captures user activity via JavaScript in the browser and sends it straight to analytics and ad tools. Easy to set up, but prone to gaps.Ad PlatformsConversions APIMeta Conversions API (CAPI)The Conversions API (CAPI) is Meta's interface for sending conversion events straight from a server to Meta, independent of the browser, the pixel and ad blockers.TrackingServer-Side GTMServer-side GTM (sGTM) is the server version of Google Tag Manager: a self-hosted server container receives events and forwards them to ad platforms.MetricsSignal LossSignal loss describes conversions and user data that never reach ad platforms because of ad blockers, cookie limits, missing consent or broken tracking setups.TrackingEvent DeduplicationAvoiding double-counted conversionsEvent deduplication makes sure that an event arriving twice, via pixel and server API, is counted only once as a conversion by the ad platform.TrackingTracking PixelA tracking pixel is a piece of code from an ad platform that records page views and conversions in the browser and reports them back to the platform.