Google Tag Manager GDPR compliance and consent risk
Google Tag Manager loads and manages third-party tracking scripts. Its presence implies potential indirect tracking. This page combines ConsentLens detection rules with live public scan data so you can see how often Google Tag Manager appears, whether it fires before consent, and which compliance issues it tends to create.
68%
Of scanned sites
302 of 444 public sites include Google Tag Manager.
0%
Fire before consent
0 detected sites fired it before a user could consent.
0%
Seen after rejection
No post-rejection evidence found in public scan data.
HIGH
Consent risk
Tag manager tracker classified from ConsentLens tracker database.
How ConsentLens detects Google Tag Manager
Domains
- googletagmanager.com
- www.googletagmanager.com
Globals
- window.dataLayer
Script patterns
- gtm.js
- GTM-
ConsentLens combines these signals with request timing. If Google Tag Manager sends a data request during the first 500ms of page load, it is treated as a pre-consent tracking risk and connected to the relevant scan evidence.
Common compliance issues
Tag manager detected with no consent mechanism
163Tag manager present — verify all tags respect consent
139Google Conversion Linker tracking cookie set without consent
59Example public scans detecting Google Tag Manager
| Domain | Score | Consent timing |
|---|---|---|
| mederi.jp | 20/100 | No early fire |
| yourselfirst.com | 20/100 | No early fire |
| devomech.com | 20/100 | No early fire |
| zazz.io | 20/100 | No early fire |
| beewebsystems.com | 20/100 | No early fire |
| cybercraftinc.com | 20/100 | No early fire |
| angrynerds.co | 20/100 | No early fire |
| isbx.com | 20/100 | No early fire |