Definition
Server-side tagging moves tag processing from the visitor’s browser to a server container you control. The browser sends events once, and the server forwards them to each destination.
In practice
With Google Tag Manager, this means a server container hosted on a first-party subdomain such as tag.yourdomain.com. The web container sends events to it, and server-side tags deliver them to GA4, Google Ads, the Meta Conversions API, LinkedIn and TikTok.
The benefits are better data control, fewer third-party scripts on the page and more reliable delivery. You can remove or transform fields before data leaves your server.
Server-side tagging does not remove consent obligations. Consent signals still need to reach the server container, and tags should respect them.
Learn more: Server-side GTM setup.
Related terms
- Data layerA data layer is a JavaScript array, usually window.dataLayer, that a website uses to pass structured event and page data to Google Tag Manager.
- Conversions API (CAPI)The Conversions API (CAPI) is Meta’s server-to-server way to send website and offline events, such as Purchase or Lead, directly from your server to Meta.
- Google Consent ModeGoogle Consent Mode is a way to pass a visitor’s consent choices to Google tags so they adjust their behavior.
- Event deduplicationEvent deduplication is how an ad platform recognizes that a browser event and a server event describe the same action, so the conversion is counted once.
How Markitech helps
Markitech connects your AI to Google Ads, GA4, Google Tag Manager, Meta and 12 more platforms, so it can check how Server-side tagging is set up in your own accounts and tags and propose fixes. Every change is held until you approve it.