CMP configuration functionality_storage

CookieYes (CMP) — consent fix

CookieYes is detected as CMP, but auto-blocking lets trackers through before consent. Common causes: (1) "Auto Blocking" is off or the CookieYes script loads after the GTM snippet, so tags fire before the blocker is active; (2) categories default to "on" (opt-out instead of opt-in); (3) the reject button ("Reject All") is less prominent than "Accept All" — a dark pattern; (4) Google Consent Mode v2 is not enabled, so Google tags do not wait for the consent signal.

Domains

  • cookieyes.com
  • cdn-cookieyes.com
  • app.cookieyes.com

Cookies

  • cookieyes-consent

Fix instructions

Required consent type: functionality_storage

  1. Place the CookieYes script as high as possible in <head>, before the GTM snippet, so auto-blocking is active before tags load.
  2. Turn on "Auto Blocking": CookieYes Dashboard → Site Settings → Auto Blocking. Then check each script category to confirm every tracker is correctly classified (unknown scripts often default to "Necessary" and slip through).
  3. Set all non-necessary categories (Analytics, Advertisement, Functional) to opt-in / disabled by default — required under GDPR.
  4. Give "Reject All" equal visual prominence to "Accept All" (same colour, size, position on the first layer). Dashboard → Cookie Banner → Banner Settings.
  5. Enable Google Consent Mode v2: CookieYes Dashboard → Integrations → Google Consent Mode. In GTM, set all Google tags to "Consent check required" (ad_storage, analytics_storage).
  6. Test: reject consent, open the Network tab and verify that no marketing or analytics requests appear.

Go directly to CookieYes

View the official documentation and configuration options for CookieYes.

View CookieYes →

Check your own site

Scan your website for free to see if CookieYes (CMP) (or other trackers) loads before consent.

Start free scan →