Google Analytics GDPR compliance and consent risk
Google Analytics tracks website visitors and collects behavioral data. This page combines ConsentLens detection rules with live public scan data so you can see how often Google Analytics appears, whether it fires before consent, and which compliance issues it tends to create.
67%
Of scanned sites
257 of 384 public sites include Google Analytics.
0%
Fire before consent
1 detected sites fired it before a user could consent.
1%
Seen after rejection
2 detected sites show post-rejection evidence.
MEDIUM
Consent risk
Analytics tracker classified from ConsentLens tracker database.
How ConsentLens detects Google Analytics
Domains
- google-analytics.com
- analytics.google.com
- www.googletagmanager.com
- googletagmanager.com
Globals
- window.ga
- window.gtag
Script patterns
- analytics.js
- gtag/js
ConsentLens combines these signals with request timing. If Google Analytics 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
Google Analytics continues tracking after consent rejection
2Google Analytics fires before consent
1Example public scans detecting Google Analytics
| Domain | Score | Consent timing |
|---|---|---|
| devvela.com | 10/100 | Before consent |
| 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 |
| ulansoftware.com | 20/100 | No early fire |