Check explainer
Pre-consent scripts
Tracking scripts referenced in the HTML before consent are critical under GDPR/ePrivacy.
- critical
- ok
What we check
Looks for 13 cookie-based trackers referenced in the HTML before consent.
Why it matters
Tracking scripts referenced in the HTML before consent are critical under GDPR/ePrivacy.
Common causes
- GTM or gtag.js is built straight into the template instead of behind the CMP blocking.
- Shop and CMS plugins inject their pixels themselves, bypassing the tag manager and the CMP categorisation.
- "Just testing quickly" snippets from old campaigns were never removed again.
- The CMP loads asynchronously, but the trackers already sit in the initial HTML.
How to fix it
Mark scripts as "requires consent" and run a browser test without interaction (DevTools → Network).
What does a failing Pre-consent scripts finding mean?
Tracking scripts referenced in the HTML before consent are critical under GDPR/ePrivacy. Mark scripts as "requires consent" and run a browser test without interaction (DevTools → Network).
How do you fix Pre-consent scripts?
Mark scripts as "requires consent" and run a browser test without interaction (DevTools → Network).