Also known as: Server-Side Tracking, Server-Side GTM
Server-Side Tagging moves tracking-tag execution from the user's browser to a server the marketer controls. Conversion and analytics data is collected server-side and forwarded to platforms from there, rather than by scripts running in the browser.
Instead of a browser loading multiple third-party tracking scripts, the page sends a single stream of event data to a server-side container the marketer runs, typically a server-side Google Tag Manager container on their own subdomain. That server then forwards the events to analytics and conversion endpoints from a first-party context, out of reach of most browser-level blocking.
Because the forwarding happens server-to-server, ad blockers and Intelligent Tracking Prevention cannot strip the tags the way they strip in-browser scripts, so more conversions are counted and attributed. For an affiliate whose Safari or ad-blocked traffic was under-reporting, that recovered data can lift measured performance and therefore payable commission without buying a single extra click. It does not, however, remove the need for valid consent; the same GDPR obligations that govern browser tags still apply to the data flowing through the server.
The marketer hosts a server-side GTM container on their own subdomain.
The page forwards event data to the container instead of firing many browser tags.
Consent state is checked before any tracking event is processed.
The container relays events to analytics and conversion endpoints first-party.
Events survive ad blockers and tracking prevention that would strip browser tags.
The partner compares recovered conversions against prior browser-only counts.
Why it matters for partnership: Ad blockers, browser tracking-prevention and the decline of third-party cookies increasingly break browser-based tracking, causing under-reported conversions and lost commission. Server-side tagging recovers much of that lost data, protecting a partner's measured performance.
An affiliate whose Safari traffic was under-reporting conversions moves to server-side tagging via a server-side GTM container. Attributed conversions rise noticeably because tracking no longer depends on the browser cooperating.
| Attribute | Client-side (browser) tagging | Server-side tagging |
|---|---|---|
| Tags run in | The user's browser | A server the marketer controls |
| Exposure to ad blockers | High, easily stripped | Low, forwarded server-to-server |
| Consent still required | Yes | Yes |
If a large share of your traffic is on privacy-strict browsers, server-side tagging can meaningfully raise your countable conversions without buying any more traffic.
Deploying server-side tags without a compliant consent basis, trading a tracking gain for a data-privacy exposure.
No. It changes where tags run, not whether you need user consent; GDPR obligations still apply.