---
title: "Google Tag Manager and sGTM - Server-side | EdgeAngel"
description: "Google Tag Manager and server-side tagging experts: web, mobile and server containers, Consent Mode, outbound data governance, audit and run."
url: https://edgeangel.co/en/data-foundations/gtm-sgtm
lang: en
---

> Site index for agents, read it before exploring further : https://edgeangel.co/llms.txt
> Canonical HTML page, which also carries the diagrams and visuals : https://edgeangel.co/en/data-foundations/gtm-sgtm

[Other tools](https://edgeangel.co/en/data-foundations/web-tracking#approche-c4)

# Google Tag Manager and sGTM Experts

## Take back control of what your tags send, and to whom.

We design, audit and maintain your Google Tag Manager containers, from the web to the server container.

[Book a discovery call](https://edgeangel.co/en/data-foundations/gtm-sgtm#contact)

-   Learn more about: [our Google Tag Manager and web tracking agency](https://edgeangel.co/en/data-foundations/web-tracking)

[Scroll to the content](https://edgeangel.co/en/data-foundations/gtm-sgtm#expertise)

EdgeAngel Google Tag Manager expertise

## Audit, server-side and compliance

01

### GTM Audit & Migration

We analyze your tracking ecosystem to build a healthy foundation. Objective: build a reliable foundation before scaling up to server-side.

-   Audit of existing tags, triggers and variables
-   Cleanup of obsolete implementations
-   Structuring of naming conventions
-   Migration to [Google Analytics](https://edgeangel.co/en/data-foundations/google-analytics)
-   Formalization of the tagging plan
-   iOS and Android containers, configured through the Firebase SDK

02

### Server-Side Implementation (sGTM)

We deploy your custom server-side tracking infrastructure. Result: more robust tracking, focused on signal quality rather than raw volume.

-   Configuration of Server-Side containers (Google Cloud, AWS, GCP)
-   Implementation of GA4, Google Ads, Meta, TikTok clients
-   Integration of Conversion APIs (CAPI, Enhanced Conversions)
-   Management of first-party cookies and extension of their lifespan
-   Security and anonymization of data before sending
-   Collection domain on a subdomain you control
-   Hosting with a specialist such as Addingwell, or on your own platform
-   Server container mirroring the web, without double counting

03

### Governance, Compliance & Consent Mode

Server-side makes sense when articulated with a real compliance strategy. We make server-side tracking a lever of trust, not an additional risk.

-   Integration with [your CMP](https://edgeangel.co/en/data-foundations/didomi)
-   Advanced configuration of Google Consent Mode v2
-   Management of access rights and GTM environments
-   Monitoring of errors, logs and alerts
-   Documentation of flows for data and legal teams
-   Container operations through the Tag Manager API, with our MCP server

Architecture

## What a server container changes, in three pictures

Classic tracking sends data from the browser to each tool. A server container steps in between: the browser only talks to one domain, yours, and the server does the distributing.

These diagrams come from our expert note on server-side tagging, where every step is detailed.

### The classic architecture, everything from the browser

![Classic GTM Web architecture: the browser's GTM Web container calls Google Analytics, Google Ads, Facebook Ads and other ad platforms directly](https://edgeangel.co/assets/notes/server-side-tagging-avec-google-tag-manager/image-03.jpg)

Each tool gets its own call from the page. That means more scripts to load, more third-party domains, and collection that depends entirely on the visitor's browser.

### With a server container, a single point of exit

![GTM Server-side architecture: the GTM Web container sends to a server container hosted on a client subdomain, which validates, anonymises and distributes to the tools](https://edgeangel.co/assets/notes/server-side-tagging-avec-google-tag-manager/image-04.jpg)

The browser sends to **a subdomain you control**. The server container validates, enriches, strips what must not leave, then distributes. Tags it does not support stay on the page.

### Where the server container lives

![Two infrastructure options for a server container: Google Cloud with App Engine, logging and BigQuery, or Amazon Web Services with Certificate Manager, Route 53 and Elastic Beanstalk](https://edgeangel.co/assets/notes/server-side-tagging-avec-google-tag-manager/image-10.jpg)

Two schools: your own cloud, which you administer, or a specialised host that takes care of it. The choice comes down to your internal resources and to what you want to keep control of.

The tool

## GTM and sGTM, our reading

Google Tag Manager is Google's **tag management system**, and it is free. It decides which tag fires, when, and with which data: the Meta tag, the Google Analytics one, the ones your ad platforms need. Without it, every tool needs your developers; with it, everything is handled from a single interface, and above all everything is bound in one place to your visitors' consent choices. That is what makes it **the cornerstone of tracking and its governance**.

A paid edition exists, Tag Manager 360: it lifts the three-workspace cap and adds approval workflows, useful when several teams work in parallel on the same container. For the vast majority of setups, the free edition is enough.

Updated September 2026

### sGTM, a relay between your site and your tools

sGTM, server-side tagging, adds a **relay between the browser and your tools**. Instead of the page calling Google Analytics, Meta and your ad platforms each in turn, it sends everything to a server you control, and that server does the distributing. It is hosted in your own cloud, on Google Cloud for instance, or with a specialised host such as Addingwell.

The move looks technical, it changes four things. The browser loads fewer scripts, so pages are faster. Events can be enriched with data only your server holds, an order margin or a signed-in customer's email. You can strip personal data before sending, which settles much of the ePrivacy question. And everything goes through your own domain, so the libraries load where blockers do not stop them.

[GDPR, ePrivacy and consent management, our offer](https://edgeangel.co/en/data-foundations/rgpd-compliance)

### And since late 2024, the same for apps

Server-side tagging used to be web only. Since October 2024, **an iOS or Android app can send its events to the same server container**, provided it uses the Firebase SDK. The benefit is the same as on the web, with one more: site and app flows meet in a single architecture, which simplifies maintenance and makes cross-device journeys legible.

The gestures are the same as on the web: stripping an IP address or a device identifier before sending, enriching an event with a customer value, routing one event to several destinations. Setting it up takes technical maturity, and it makes most sense when a server container already exists for the site.

[App Tracking, our offer for your mobile apps](https://edgeangel.co/en/data-foundations/app-tracking)

### Our MCP server, to run your containers with agents

We built our own MCP server for GTM and sGTM. It connects your containers to our agents, and what used to take hours of clicking becomes a conversation: inventorying what exists, checking naming conventions, spotting inactive tags, auditing a container in depth. Publishing stays manual: an audit can be automated, a release is decided.

Sources : [The server container model, clients and transformations](https://developers.google.com/tag-platform/tag-manager/server-side/intro) · [The three collection domain options, and what each allows](https://developers.google.com/tag-platform/tag-manager/server-side/custom-domain)

Our expert notes : [Server-side Tagging with Google Tag Manager](https://edgeangel.co/en/notes/server-side-tagging-avec-google-tag-manager) · [Server-side GTM for Apps](https://edgeangel.co/en/notes/sgtm-for-apps) · [Google Consent Mode v2: What's New](https://edgeangel.co/en/notes/google-consent-mode-v2-essentiel-a-savoir) · [Google Ads: wbraid and gbraid parameters](https://edgeangel.co/en/notes/google-ads-nouveaux-paramtres-wbraid-et-gbraid-pour-le-suivi-des-conversions)

## Frequently asked questions about Google Tag Manager and sGTM

### What is the difference between a web container and a server container?

The web container runs in the browser and fires tags from the page. The server container runs on infrastructure you control: a client claims the incoming request and turns it into events, transformations filter parameters, then tags send data over HTTP. It is a container type within the same tool, not a separate product.

### Is server-side tagging enough to be GDPR compliant?

No, and Google does not present it that way. It moves the control point: you decide what goes to each partner, and you can strip parameters before sending. But consent is collected by a CMP, and tags must be conditioned on its signal. The container enforces a decision, it does not make it.

### Should everything move server-side?

Rarely. The approach that works is hybrid: critical flows move server-side, the rest stay client-side. Some tags do not support server mode, and a server container mirroring the web needs blocking triggers so the same event is not processed twice. Scope is decided flow by flow.

### Is the default collection domain good enough?

It works, but without the expected benefit. On the domain Google provides, the documentation states that only JavaScript cookies can be set, so without the HttpOnly attribute. The first-party gain requires delegating a subdomain you control, same-origin with the site where possible, which is the practice Google recommends.

### What is the difference between Tag Manager and Tag Manager 360?

The same tool, two editions. The standard one is free and capped at three workspaces, the default plus two. Tag Manager 360, part of Google Marketing Platform, lifts that cap and adds approval workflows, Zones and vendor support. It makes sense when several teams work in parallel on one container.

Contact

## You leave your details, we get back to you within 24 hours.

A first call to understand your context, and tell you what is feasible and under which conditions.

1.  Contact and need
2.  Tell us more (optional)
3.  Then we schedule a call

Your details are used to reply to you on this topic. [Data protection policy](https://edgeangel.co/en/a-propos/politique-de-protection-des-donnes)

Or call us directly: [+33 1 84 16 42 20](tel:+33184164220)

Paul Schmitt

Consulting Director

"Our goal is to make your data actionable to generate concrete value, quickly."

[The team](https://edgeangel.co/en/a-propos/agence)

```json
{"@context":"https://schema.org","@type":"Organization","name":"EdgeAngel","url":"https://edgeangel.co","logo":"https://edgeangel.co/assets/brand/edgeangel-logo.svg","sameAs":["https://www.linkedin.com/company/edgeangel"],"contactPoint":{"@type":"ContactPoint","email":"hello@edgeangel.co","telephone":"+33 1 84 16 42 20","contactType":"customer service"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://edgeangel.co/en"},{"@type":"ListItem","position":2,"name":"Data Foundations","item":"https://edgeangel.co/en/data-foundations"},{"@type":"ListItem","position":3,"name":"Web Tracking","item":"https://edgeangel.co/en/data-foundations/web-tracking"},{"@type":"ListItem","position":4,"name":"Google Tag Manager","item":"https://edgeangel.co/en/data-foundations/gtm-sgtm"}]}
{"@context":"https://schema.org","@type":"Service","name":"Google Tag Manager and sGTM - Server-side | EdgeAngel","description":"Google Tag Manager and server-side tagging experts: web, mobile and server containers, Consent Mode, outbound data governance, audit and run.","provider":{"@type":"Organization","name":"EdgeAngel","url":"https://edgeangel.co"},"areaServed":"France","url":"https://edgeangel.co/en/data-foundations/gtm-sgtm"}
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the difference between a web container and a server container?","acceptedAnswer":{"@type":"Answer","text":"The web container runs in the browser and fires tags from the page. The server container runs on infrastructure you control: a client claims the incoming request and turns it into events, transformations filter parameters, then tags send data over HTTP. It is a container type within the same tool, not a separate product."}},{"@type":"Question","name":"Is server-side tagging enough to be GDPR compliant?","acceptedAnswer":{"@type":"Answer","text":"No, and Google does not present it that way. It moves the control point: you decide what goes to each partner, and you can strip parameters before sending. But consent is collected by a CMP, and tags must be conditioned on its signal. The container enforces a decision, it does not make it."}},{"@type":"Question","name":"Should everything move server-side?","acceptedAnswer":{"@type":"Answer","text":"Rarely. The approach that works is hybrid: critical flows move server-side, the rest stay client-side. Some tags do not support server mode, and a server container mirroring the web needs blocking triggers so the same event is not processed twice. Scope is decided flow by flow."}},{"@type":"Question","name":"Is the default collection domain good enough?","acceptedAnswer":{"@type":"Answer","text":"It works, but without the expected benefit. On the domain Google provides, the documentation states that only JavaScript cookies can be set, so without the HttpOnly attribute. The first-party gain requires delegating a subdomain you control, same-origin with the site where possible, which is the practice Google recommends."}},{"@type":"Question","name":"What is the difference between Tag Manager and Tag Manager 360?","acceptedAnswer":{"@type":"Answer","text":"The same tool, two editions. The standard one is free and capped at three workspaces, the default plus two. Tag Manager 360, part of Google Marketing Platform, lifts that cap and adds approval workflows, Zones and vendor support. It makes sense when several teams work in parallel on one container."}}]}
```