Skip to Content
Platform.Ontology

Server side tagging

The site sends its analytics to its own server first, which relays it to ad vendors.

Used to track youTracking across apps and sitesIn sessionWeb browsersWhile you use itAfter you leave the site

In one line

Can send your activity to the site's own server first, then on to ad vendors

The site sends its analytics to its own server first, which relays it to ad vendors.

Moves tracking from the browser to the site's cloud container, so blockers cannot see vendor calls and cookies are set by the site's own server. The vendor can still receive IP, user agent, hashed email and click IDs the server chooses to forward.

What it can and can't do

What the user does: Nothing on your side. It happens as you use a site that routes data through its server

It can

  • Collect your visits on the site's own server
  • Pass them to ad and analytics vendors
  • Choose what data each vendor receives, including fewer details

It cannot

  • Be seen or blocked by your browser, since the relay is out of sight
  • Add details the browser never sent
  • Work unless the site has set it up
  • Give vendors your data if the site chooses not to pass it on

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11Server side, browser independent
EdgeSupported1Not listedServer side, browser independent
FirefoxSupported12004-11-09Server side, browser independent
SafariSupported12003-06-23Server side, browser independent
Safari on iPhoneSupported12007-06-29Server side, browser independent
Chrome on AndroidSupported1Not listedServer side, browser independent
Samsung InternetSupported12013-04-27Server side, browser independent

How a site asks for it

APIGoogle Tag Manager server container on a first party subdomain; Set-Cookie from server
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsServer set cookies can last up to 400 days but Safari caps IP mismatched ones at 7 days
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Event payload from server
Shape: object
How often: per event

No individual data fields. The signal is the access itself.

Technical limits

  • Server must forward data on its own authority
  • Consent rules still apply
  • Safari caps cookies from servers on different IP ranges
  • Browser mitigations like Safari 27 IP blocking do not see server to server calls

The story

What it is

A site sends its tracking to its own server first, which passes it on to ad vendors.

For you

You never see it. Instead of loading many vendor scripts, the page sends one stream to the site's own server. Blockers cannot see vendor calls, and cookies are set by the site's own server.

For makers

Pages load faster and the company controls what each vendor gets. It also gets around blockers and short cookie limits. The server can still forward IP, hashed email and click IDs.

Where you see it

TypeExampleApps
analyticsA shop sends all events to its own server, then to Google Analytics and Meta, so pages load faster.Google Tag Manager
adsAn advertiser sets a first party cookie from its own server, so it lasts longer than a script cookie.Google Ads, Meta Ads
gamesA game store sends purchase events through its server to ad networks, with no vendor script on the page.Steam
mediaA publisher removes dozens of ad scripts from the page and sends data from its server.The New York Times
securityA company hashes email on its server and drops IP before sharing, to cut what vendors see.None named
shoppingA retailer adds server events to fill gaps when shoppers use blockers.Shopify

Risks

  • Cannot be blocked in your browser
  • Company decides what each vendor sees

What the platform says

Good uses and abuse

Legitimate uses

  • Performance, data control

Known abuse

  • Evading blockers, covert hashed email forwarding

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2020-08, all: Google Tag Manager server side tagging announced
  • 2021-09, all: GA4 server side support expanded

Sources

How well checked: Based on official documentation.

On this page