Check explainer
Reject is respected
If marketing or analytics still fire after "Reject", that is the single most common GDPR finding at supervisory authorities.
- critical
- ok
What we check
Checks whether marketing/analytics requests or non-essential cookies still appear after "Reject".
Why it matters
If marketing or analytics still fire after "Reject", that is the single most common GDPR finding at supervisory authorities.
Common causes
- The tags were never tied to the consent status in the tag manager, the banner is effectively decoration.
- A pixel added after the CMP setup was never categorised and runs straight past the tag-blocking.
- Hardcoded tracking snippets in the theme or template fire outside the tag manager.
- The CMP stores the rejection correctly, but scripts already loaded simply keep running for the session.
How to fix it
Enforce CMP tag-blocking: load tags only after opt-in, the reject state must produce no marketing requests or cookies.
What does a failing Reject is respected finding mean?
If marketing or analytics still fire after "Reject", that is the single most common GDPR finding at supervisory authorities. Enforce CMP tag-blocking: load tags only after opt-in, the reject state must produce no marketing requests or cookies.
How do you fix Reject is respected?
Enforce CMP tag-blocking: load tags only after opt-in, the reject state must produce no marketing requests or cookies.