Google Tag Manager
How to configure Google Tag Manager at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics, Receive personalised marketing offers, Customise online ads
Overview
This guide explains how to implement different privacy configurations for Google Tag Manager and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. This guide covers the Google Tag Manager (GTM) web container (gtm.js) on a website, and the option of loading that container through a server-side tagging server on the operator's own domain (Google tag gateway). It covers only the container itself. Every tag fired by the container (Google Analytics, Google Ads, Meta Pixel and so on) is a separate recipient with its own purposes and must be entered and assessed separately in the Consenter Manager.
Out of scope. The tags deployed through GTM; Google Analytics and Google Ads consent mode behaviour; GTM for mobile apps.
What the service does in this scope. GTM loads a JavaScript container that decides which tags to fire. Google states that, apart from data in standard HTTP request logs (deleted within 14 days) and aggregated diagnostic data about tag firing, GTM "does not collect, retain, or share any information about visitors" to its customers' sites.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | GTM scripts are served first-party through the operator's own server-side tagging server; the container loads only after consent. |
| Configuration B — Medium risk (default) | Standard installation: gtm.js is loaded from www.googletagmanager.com; the container loads only after consent. |
No configuration without prior consent. The Administrative Court of Hanover held that GTM accesses the end device and processes data such as IP addresses, that it serves no function the user has requested, and that its use therefore requires consent under § 25(1) TDDDG (VG Hannover, judgment of 19 March 2025, 10 A 5385/22). This guide therefore offers no configuration in which GTM loads before consent. Consent mode does not change this: it governs the behaviour of the tags, not whether the container itself is loaded.
Prerequisites and limitations.
- Consenter must load the GTM container only after consent, and each tag in the container must be blocked or consent-gated in its own right.
- Configuration A requires a GTM server container, a tagging server and a custom domain.
- GTM itself has no documented settings for IP truncation or retention; HTTP request log retention is fixed at 14 days.
| Action | Configuration A — Lower risk | Configuration B — Medium risk (default) |
|---|---|---|
Source of gtm.js | Operator's tagging server (first-party path or subdomain) | www.googletagmanager.com |
| Loading of the container | Blocked by Consenter until consent | Blocked by Consenter until consent |
| Tag-level consent settings | Configured for every tag | Configured for every tag |
| Consenter Manager entries | One entry for GTM (self-hosted server), plus one per tag | One entry for GTM (Google as processor), plus one per tag |
Step 1 — Configure Google Tag Manager
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk (default) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Purposes of the tags fired through the container | Purposes of the tags fired through the container |
| 2 | Script source | Server container > Clients > Google Tag Manager: Web Container client; website snippet updated to point to the custom server domain | First-party source (operator's tagging server) | Default Google source (www.googletagmanager.com) |
| 3 | Hosting of the tagging server | Server container provisioning (Google Cloud project "or in a different environment of your choosing") | Operator-controlled infrastructure in the EU (illustrative) | Not applicable |
| 4 | Container loading | Consenter script blocking for the GTM entry | Blocked until consent | Blocked until consent |
| 5 | Tag-level consent settings | Tag > Advanced Settings > Consent Settings > Additional Consent Checks; Admin > Container Settings > Enable consent overview | "Require additional consent for tag to fire" for every tag without built-in consent checks | Same as A |
| 6 | HTTP request log retention | Not configurable. Deleted within 14 days | Fixed by Google | Fixed by Google |
| 7 | IP address handling for the container request | Not configurable in GTM | Request goes to the operator's server; the tagging server forwards the script request to Google | Visitor's IP address reaches Google with each container request |
Configuration A — Lower risk
- Intended use. Tag management in which the visitor's browser does not contact Google servers to load the container.
- Prerequisites. GTM server container, tagging server and custom server domain; Consenter can block the container snippet.
- Implementation steps.
- Set up a server container and tagging server, hosted on infrastructure you control.
- In the server container, configure the client that serves Google scripts, and update the script source on the website to the custom server domain.
- Verify in the browser's developer tools that
gtm.jsloads from your server, not fromwww.googletagmanager.com. - Configure Consenter to block the container until consent and set consent checks for every tag.
- Resulting processing. The browser requests
gtm.jsfrom the operator's domain. The tagging server forwards the script request to Google servers. Whether visitor-specific request headers are forwarded is not documented (verification point). - Why lower risk. Google does not receive the visitor's request directly, and the operator controls the server and its logs.
- Remaining risks and verification points. Check the tagging server's request forwarding and logging; the tags themselves still determine most of the privacy risk.
Configuration B — Medium risk (default)
- Intended use. Standard GTM installation.
- Implementation steps. Install the standard container snippet; configure Consenter to block it until consent; configure consent checks for every tag.
- Resulting processing. Each container request sends the visitor's IP address, requested URL and HTTP headers to Google. Google keeps HTTP request logs for up to 14 days and collects aggregated tag-firing diagnostics without IP addresses or measurement identifiers.
- Why medium risk. Direct transmission of the IP address to a US-headquartered provider on every page load after consent; no profiling by GTM itself.
Step 2 — Map the configuration in the Consenter Manager
Enter GTM as its own recipient. Every tag fired through GTM needs its own entry.
Processing location (applies to Configuration B). Google LLC is a US company. As a US provider, it can be required to disclose data in its possession, custody or control regardless of where the data is stored. The United States is therefore listed as a potential processing and access location. This reflects potential access, not confirmed disclosure.
Configuration A — Lower risk
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Purposes of the tags in the container | GTM has no purpose of its own beyond deploying tags. |
| Tracking method | No tracking | GTM sets no identifier of its own in this scope. |
| Identifier | IP address | The IP address is received by the operator's tagging server. |
| Data categories | IP address, Device characteristics | Request headers (user agent) reach the tagging server. |
| Legal role of data recipient | Self-hosted | The server container runs in an environment the operator controls. |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Per the operator's server log policy | Set by the operator. |
| Processing location | Location of the operator's tagging server | Hosting choice of the operator. |
Configuration B — Medium risk (default)
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Purposes of the tags in the container | As in A. |
| Tracking method | No tracking | No GTM identifier is stored. |
| Identifier | IP address | Included in every HTTP request to Google. |
| Data categories | IP address, Device characteristics | IP address and HTTP request headers in Google's request logs. |
| Legal role of data recipient | Processor | Google refers to the Google Ads Data Processing Terms for GTM customers subject to the GDPR. |
| Personalisation model | No personalisation | GTM does not profile visitors. |
| Maximum storage duration | 14 days | HTTP request logs are deleted within 14 days. |
| Processing location | United States (Google LLC); United States as potential access location | See the processing-location note above. |
Privacy-policy follow-up
- Recipients and roles: Google as processor for GTM (B), or the operator's own server (A); each tag's recipient separately.
- Data categories: IP address and HTTP request headers.
- Legal bases and consent handling: distinguish the ePrivacy / TDDDG consent for access to the device from the GDPR legal basis for the processing.
- Retention: 14 days for Google's HTTP request logs (B).
- Processing locations and transfers: Google LLC in the US; potential access by US authorities.
Verification checklist
- Before consent: no request for
gtm.js(to Google or to the tagging server). - After consent:
gtm.jsloads from the expected source. - Consent overview: every tag has consent settings configured.
- Tags: every tag in the container has its own Consenter Manager entry.
- Configuration A: request forwarding and logs of the tagging server checked.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on