Server-side Conversion Measurement Explained

Modified on Thu, 9 Jul at 4:53 PM

What is Server-side Conversion Measurement?

Traditionally, when someone completes an action on your site (like a purchase), a script running directly in their browser sends that data straight to advertising or analytics platforms. Server-side conversion measurement moves part of your tracking setup from the user’s browser to a server environment. The server processes, cleans, and packages that data before securely forwarding it to the analytics or advertising destinations via an API (like Meta's Conversions API or Google Analytics 4 Measurement Protocol).


Client-side tracking:

  • Browser loads tracking scripts using a web container Google Tag Manager (GTM)
  • Browser sends data directly to platforms like Google Ads, GA4, Meta, etc.


Server-side tracking:

  • Browser loads GTM (web container) running on a custom tagging server 
  • GTM (web container) sends data to GTM (server container) using GA4 events
  • GTM (server container) processes and forwards the data to vendors


Note: The combination of GTM & GA4 is the most commonly used tag management setup, but other tools can be used as well.


Why Server-Side is Better for Measurement

If client-side tracking worked perfectly for years, why is the industry shifting to server-side? The fundamental difference lies in where the tracking code executes and who controls the data flow. It boils down to accuracy, privacy, and performance.


It Bypasses Ad Blockers and Privacy Filters

Standard ad blockers and privacy-focused browsers (like Safari with ITP or Brave) look for known tracking scripts running in the browser and block them completely. Because server-side tracking routes data through your own custom domain (e.g., events.yourwebsite.com), browsers view it as essential first-party communication rather than third-party snooping. This drastically reduces missing conversion data.


Longer Cookie Lifespans

Browsers are aggressively cutting down the lifespan of third-party - and even some client-side first-party - cookies to just 1 to 7 days. If a user clicks an ad but takes 8 days to buy, client-side tracking loses the connection. Server-side tracking allows you to issue true, server-managed first-party cookies that can last much longer, ensuring accurate attribution for longer sales cycles.


More Control over Data and Privacy

With client-side tracking, a third-party SDK has free rein in the user's browser, potentially scraping URLs, personal info, or proprietary data you didn't intend to share. With server-side tracking, the data stops at your server first. You can redact or hash sensitive PII (Personally Identifiable Information) like email addresses or phone numbers before sharing it to Facebook or Google, keeping you compliant with privacy regulations like GDPR.


Client-side versus Server-side tracking 

Feature

Client-side Tracking

Server-side Tracking

Data Route

Browser => Ad Platform

Browser =>  Server => Ad Platform

Vulnerability to Ad Blockers

High (easily blocked)

Low (Bypasses most blockers)

Impact on Page Speed

Heavy (Multiple heavy scripts)

Light (One streamlined data stream)

Data Control & Privacy

Low (Platforms send what they want)

High (You choose what to send)

Cookie Lifespans

Short (Restricted by browsers like Safari)

Long (Set as first-party from your server)


How does it work?


┌────────────────────┐

│ 1. User clicks ad  │

│    via Ad Manager  │

└────────────────────┘

          │

          ▼

┌────────────────────────────────────────────┐

│ https://advertiser.nl/?token=${SSP_DATA}  

└───────────────────────────────────────────

          │

          ▼

┌─────────────────────────────────────┐

│ 2. Web GTM                          

│ - Checks Consent Mode              

│ - Reads token from URL              │

│ - Sends token via GA4 request      

└─────────────────────────────────────┘

          │

          ▼

┌─────────────────────────────────────┐

│ 3. Server-Side GTM                   │

│ - advertiser domain                  │

│ - Checks Consent Mode                │

│ - Receives GA4 request               │

│ - Stores token in secure             │

│   HttpOnly cookie                    │

└──────────────────────────────────────┘

          │

          ▼

┌────────────────────────┐

│ 4. Conversion          │

│ Purchase / Signup      │

└────────────────────────┘

          │

          ▼

┌──────────────────────────────────────┐

│ 5. Server-to-Server Attribution      │

│ - Checks Consent Mode                │

│ - server GTM reads cookie            │

│ and sends conversion to Ad Manager   │

└──────────────────────────────────────┘


Setup Server-side Measurement

More information about servers-side conversion measurement works can be found here and here.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article