What is server-side tagging?

Server-side tagging means that your website sends its tracking data to a server you control, and that server passes it on to Google Analytics, Google Ads, Meta and the rest. The platforms no longer talk to the visitor's browser directly. That one change moves the tags, the cookies and the control from a place you do not own (the browser, with its blockers and limits) to a place you do. This page explains what that means in practice, without assuming you have run a server before.

Tagging or tracking?

Two words for the same thing. "Tagging" comes from Google Tag Manager, where every tracking snippet is a tag, so Google's name for the technique is server-side tagging and its server product is the server container, often shortened to sGTM. "Tracking" is the everyday word for what those tags do. Marketers in the Netherlands mostly search for server-side tracking; the setup they find is server-side tagging. You will see both on this site.

How client-side tracking works today

On a normal site, Google Tag Manager loads from googletagmanager.com, and each tag inside it sends its data straight from the browser to its own platform: the GA4 tag to google-analytics.com, the Meta pixel to facebook.com, and so on. Every one of those connections is visible to the browser and to anything installed in it. Ad blockers recognise the domains and stop the requests. Safari treats cookies set by those scripts as short-lived and deletes them after seven days. Privacy browsers strip the click IDs from your landing URLs. None of that is a bug; the browser is doing what its maker decided. You simply have no say in it.

What changes with a tagging server

With server-side tagging, the browser sends one stream of events to a tagging server that lives on a subdomain of your own site, for example mbase.yoursite.com. That server runs a Google Tag Manager server container: the same kind of container you know, with clients that receive the events and tags that forward them to each platform. Three things follow:

• Requests become first-party. The browser talks to your own domain, which block lists and browser rules treat differently from a known tracking domain. Your website keeps loading one script from your own address, and that script is what Measurebase calls the Enhanced script: a loader whose path is masked so filter lists have nothing fixed to match.
• Cookies can be set by a server. A cookie set by your own server in an HTTP response keeps its full lifetime, where the same cookie set by JavaScript is capped at seven days on Safari. Our guide to first-party and third-party cookies walks through what each browser does.
• You decide what goes where. The server container sees every event before any platform does. You can add data the browser could not know, such as the visitor's country or the profit on an order, strip data you do not want to share, such as a full IP address, and send one event to five platforms with one identifier so none of them counts it twice.

What a tagging server does not do

It does not make consent optional. The visitor's choice still governs what is sent, and Consent Mode travels with every event to the server container, which has to respect it; the guide on Consent Mode v2 server-side covers that. It does not hide you from the platforms: Google, Meta and the others receive the same data they would have received, from your server instead of the browser. And it does not fix a broken setup: a tag that fires twice fires twice on the server too.

Where the server runs: sGTM hosting

A server container is configuration; it needs a machine to run on. That machine is what "sGTM hosting" refers to. You can run it yourself on a cloud account, which means managing the instances, the certificate, the scaling and the updates, or you can use managed sGTM hosting, where a provider runs the server under your subdomain and you keep working in Tag Manager as before. Where that server stands matters for privacy: a tagging server in the EU keeps your visitors' raw data on EU infrastructure, which is the point of hosting server-side GTM in the EU.

Measurebase is managed sGTM hosting in the Netherlands. You connect or paste your server container, add one DNS record for your tagging subdomain, and the server, the certificate and the monitoring are taken care of. The power-ups then run on that server, in front of your container: ad blocker protection, cookie lifetime, click ID recovery, data enrichment and the rest.

What it means for your numbers

• More of your visits measured. Hits that blockers used to stop arrive. How much you recover depends on your audience; the guide on ad blockers and your GA4 numbers puts figures to it.
• Returning visitors stay recognised. Server-set cookies live for their full lifetime, so a visitor who comes back in week three is the same visitor, and a conversion three weeks after the click still has its source.
• Better-matched conversions. Google Ads enhanced conversions and the Conversions APIs of Meta, TikTok and LinkedIn all work best when hashed customer data and click IDs arrive with the event; the server is where you add them once, for every platform.
• One place to check. Every event passes your server, so you can log it, audit it and alert on it. That is what the Measurebase request logs, the nightly tracking audit and the monitoring are built on.

How to set it up

Four steps, in the order you will do them: create a server container in Google Tag Manager (or connect the one you have), point a subdomain of your site at the tagging server with one A record, replace the Tag Manager snippet on your site with the first-party loader, and set server_container_url on your Google tag so the hits go to your subdomain. The complete setup guide takes you through each step with Measurebase; the server container guide and the web container guide cover the Tag Manager side.

Frequently asked questions

Is server-side tagging the same as server-side tracking?

Yes. Tagging is Google Tag Manager's word for it, tracking is the everyday word. The setup is identical.

Do I still need Google Tag Manager in the browser?

Yes. The web container keeps running on your pages; it sends its events to your server container instead of to each platform. Only its loader changes.

Is a tagging subdomain first-party?

Yes, it is a subdomain of your own site. Safari adds one rule: cookies from a subdomain whose server runs elsewhere are capped at seven days. Serving the tagging from a path on your own website (Same-Origin Tracking) lifts that cap.

Does server-side tagging bypass consent?

No. Consent Mode signals travel with every event, and the server container is expected to respect them. Tracking without consent is as unlawful server-side as it is in the browser.

How long does the switch take?

With an existing server container, about fifteen minutes plus DNS propagation. Without one, add the time to create the container and import your tags.

What does managed sGTM hosting cost?

Measurebase starts free for one domain and 15,000 requests a month; paid plans scale by requests and domains. See the pricing page.