Server-Side Tracking
Server-side tracking is a method of collecting analytics and conversion data on a web server you control, instead of directly in the user’s browser. The browser sends raw event data to your server, which processes it and forwards it to platforms like GA4, Google Ads, and Meta. This keeps data flowing when ad blockers and browser privacy settings break browser-based tracking.
Why Server-Side Tracking Matters
Server-side tracking exists because client-side tracking is losing data. Browser scripts are blocked, capped, or stripped before they ever fire. The server becomes a reliable middle layer that the browser cannot block.
Three forces drive the shift:
- Ad blockers. Roughly 30% of users run an ad blocker, and most block analytics scripts and pixels outright.
- Safari Intelligent Tracking Prevention (ITP). Apple caps cookies set by client-side JavaScript at 7 days, and often 24 hours, which breaks attribution windows.
- Firefox ETP and Apple’s App Tracking Transparency (ATT). Both cut off third-party signals that pixels rely on.
When tracking moves to the server, events are sent from your own domain. They are no longer easy to block, and cookies set server-side last far longer. The result is more complete data and more accurate conversion reporting for bidding.
Server Side vs Client Side Tracking
The core difference is where data is collected and who can interfere with it. Client-side tracking runs in the browser, so anything blocking the browser blocks the data. Server-side tracking runs on infrastructure you own.
| Server-Side Tracking | Client-Side Tracking | |
|---|---|---|
| Where data is collected | Your server | The user’s browser |
| Blocked by ad blockers | Rarely | Often |
| Affected by ITP cookie caps | Less | Heavily |
| Control over the data | Full (filter, enrich, redact) | Limited |
| Setup complexity | Higher | Lower |
| Page speed impact | Lower (fewer browser scripts) | Higher |
Most teams run both. The browser still captures the initial event, then hands it to the server for delivery. This hybrid setup is the standard for server-side tagging today.
How Server-Side Tracking Works
The flow adds one step between the browser and the analytics platform:
- A user takes an action on your site, such as a page view or purchase.
- The browser sends that event to a server container, usually a server-side Google Tag Manager (sGTM) instance running on a subdomain like
sst.yourdomain.com. - The server processes the event. It can clean the data, add first-party details, strip sensitive fields, and apply consent rules.
- The server forwards the event to GA4, Google Ads, Meta’s Conversions API (CAPI), and other endpoints.
Because the request comes from your own subdomain, browsers treat it as first-party. Cookies set this way survive longer than client-side cookies under ITP.
Google introduced server-side tagging in Google Tag Manager in 2020. It now runs on Google Cloud or any tagging server you host.
Common Misconceptions
Server-side tracking is not a privacy loophole. It does not bypass user consent. You still must honor consent choices and privacy laws like GDPR. The server actually gives you more control to redact data and enforce consent before sending anything out.
It does not eliminate the browser. Most events still originate in the browser. The server handles delivery, not collection from thin air.
It is not only for large enterprises. Server-side GTM is accessible to mid-sized teams, though it requires hosting costs and more setup than dropping a script on a page.
How to Implement Server-Side Tracking
Most setups follow the same path:
- Spin up a server container in Google Tag Manager and host it on a subdomain of your main site.
- Point your GA4 and Google Ads tags to send events to that server endpoint.
- Connect server-side destinations like Meta CAPI and Enhanced Conversions.
- Keep your UTM parameters intact. UTMs travel in the URL, so they survive cookie loss and reach the server cleanly. Build consistent tagged links with linkutm’s UTM builder so campaign data stays accurate end to end.
Frequently Asked Questions
What is server-side tracking?
Server-side tracking is the practice of collecting and sending analytics and conversion data from a server you control rather than from the user’s browser. The browser passes events to your server, which then forwards them to platforms like GA4 and Meta. It keeps tracking working when browsers and ad blockers block client-side scripts.
What is the difference between server side and client side tracking?
Client-side tracking runs in the browser, where ad blockers and privacy settings can block or shorten it. Server-side tracking runs on your own server, so the data is harder to block and cookies last longer. Most teams use both, with the browser collecting events and the server delivering them.
Does server-side tracking bypass cookie consent?
No. Server-side tracking still requires user consent and must follow privacy laws like GDPR. It gives you more control to apply consent rules and remove sensitive data before sending events, but it does not let you ignore consent.
Do UTM parameters still work with server-side tracking?
Yes. UTM parameters live in the URL, so they reach the server regardless of cookie blocking. That makes them one of the most durable campaign signals in a server-side setup.
To keep campaign data clean as you move tracking server-side, build consistent links with the free UTM builder at linkutm.