Skip to content
NEW: Martech, explained →

Martech, explained · Data foundations · 2:07

Server-side tagging, explained

Twelve tags sending straight to twelve vendors, or one stream to a server you control with a say on every line out

Embed this film

Paste this where the film should play. It links back here.

The short answer

Server-side tagging changes the route. Instead of a dozen scripts each sending what they see straight to their own vendor, the page sends one stream of events to a server you control, usually on your own domain, and that server sends each vendor only what it needs. It doesn't replace consent, and someone has to run it.

Questions this answers

What is server-side tagging?

A change of route. Client-side, a dozen tags load with the page and each sends what it sees straight to its own vendor: twelve scripts, twelve destinations, none fully yours. Server-side, the page sends one stream of events to a tagging server you control, often on your own subdomain, and that server forwards each vendor only the fields it needs.

Why do teams move tags server-side?

Three reasons. The browser has changed: Safari limits how long a cookie set by a script can last, in many cases to seven days, so a returning customer can look new; Brave and Firefox block tracking scripts or limit cookies too. Control: before data leaves, you decide what each vendor gets. And a lighter page, so it loads faster.

Does a server-set cookie last longer than a script-set one?

Often, yes. A cookie set by your own server, on your own domain, can last longer than one a script sets in the browser, which Safari caps in many cases at seven days. Not forever, and not in every setup: Safari limits some server-side arrangements too. The film keeps it to the common case.

Does server-side tagging replace consent management?

No. A no still means no. Moving the route does not move the choice: the server has to check the person's consent before it forwards an event, just like the page did. Every event should still carry that consent, which is the third question to ask before you move. Consent management is its own film.

What does server-side tagging cost?

A server, and someone to own it. It has to run, be paid for, and be watched: a line that quietly stops sending is a cost nobody notices until a report is wrong. The catalog lists 20 server-side tagging tools and 17 tag managers (1 November 2026). Consent and tagging are converging: Didomi bought Addingwell (Market Report, autumn 2026).

Transcript

Every chapter as text. Click a time to play the film from there.

0:00 A dozen tags, a dozen routes

Open a typical product page, and a dozen tags load with it.

Each one sends what it sees straight to its own vendor.

Analytics, ads, chat, replay. Twelve scripts, twelve destinations, and you don't fully control any of them.

0:19 What server-side tagging changes

Server-side tagging changes the route.

The page sends one stream of events to a server you control.

That server sends each vendor only what it needs.

0:31 Safari, and other privacy-focused browsers

Why move? First, the browser has changed.

Take Apple's Safari. It limits how long a cookie set by a script can last, in many cases to seven days.

So a customer who comes back after two weeks can look like someone new, and your reporting splits one person into two.

And it isn't only Safari. Privacy-focused browsers like Brave and Firefox block known tracking scripts, or limit cookies too.

A cookie set by your own server, on your own domain, can last longer.

Not forever, and not in every setup. But longer.

1:11 Control over what each vendor gets

Second, control. Before data leaves, you decide what each vendor gets.

Drop the IP address for one, add the order value for another.

Third, a lighter page. Fewer scripts in the browser means the page loads faster.

1:30 What it doesn't replace, and what it costs

What it doesn't do is replace consent. A no still means no.

The server has to check the choice, just like the page did.

And it isn't free. Someone has to run the server, pay for it, and notice when it stops sending.

1:49 The choice

A dozen scripts, each sending what it likes.

Or one stream, and a say on every line.

That's the choice server-side tagging gives you.

Learn more at Martech Stack Builder, or build your own.