CookieYes
CookieYes (formerly GDPR Cookie Consent by Cookie Law Info) is one of the consent management platforms (CMPs) the Pixel Manager integrates with automatically. This page explains how the integration works, which settings we recommend, and what to check when the Pixel Manager does not appear to recognise CookieYes.
Short answer
CookieYes is supported and compatible with the Pixel Manager for WooCommerce. It works in the free and in the Pro version, and it works whether you install the CookieYes WordPress plugin or load CookieYes as a script from the CookieYes console. Nothing needs to be configured on either side for the consent signal to reach the Pixel Manager.
If you are replacing Cookiebot for cost reasons, CookieYes is a working option. Enable Explicit Consent Mode in the Pixel Manager, and read the recommended configuration below.
How the Pixel Manager detects CookieYes
The integration runs entirely in the visitor's browser and relies on two things CookieYes provides on every page:
- The
cookieyes-consentcookie. CookieYes writes it as soon as the banner loads. Until the visitor decides, the category values in that cookie are empty, and the Pixel Manager treats every category as denied. Once the visitor accepts or rejects, the cookie carriesyesornoper category and the Pixel Manager reads the decision on every following page load. The older per-category cookies (cookielawinfo-checkbox-*andcookieyes-*) from previous CookieYes versions are still read as well. - The
cookieyes_consent_updateevent. CookieYes fires it when the visitor interacts with the banner. The Pixel Manager listens for it and applies the new consent state immediately, on the same page view, without a reload. Pixels whose category was approved load right away.
CookieYes categories map to the Pixel Manager's consent categories like this:
| CookieYes category | Pixel Manager category |
|---|---|
necessary | necessary |
functional | preferences |
analytics | statistics |
advertisement | marketing |
performance, other | not used |
Plugin or console install: no difference on the storefront. The cookie and the event are written by the CookieYes script itself, so they exist whether that script is delivered by the CookieYes WordPress plugin or by the snippet you paste from the CookieYes console. We have verified this on a live shop that runs CookieYes from the console only: the Pixel Manager logged CookieYes CMP consent detected, blocked all pixels before the choice, and loaded them after "Accept all".
The admin card only knows the WordPress plugin. The "Consent Management Platforms" card in the Pixel Manager settings is built on the server and checks whether the CookieYes WordPress plugin is active. If you load CookieYes from the console, that card says "None detected on this site" even though the storefront integration works. The card is informational. It has no effect on tracking. See Your CMP shows as "None detected" for the general explanation.
CookieYes support is not a Pro feature. Every CMP integration is included in the free version.
Recommended configuration
This is the setup we have verified on customer shops and recommend for a GDPR store.
- Enable Explicit Consent Mode in WooCommerce > Pixel Manager > Consent Management. Without it the Pixel Manager runs in implicit mode, fires pixels before the visitor answers the banner, and only stops after an opt-out. Details in the Consent Management overview.
- Leave Explicit Consent Regions empty unless you have a reason to track visitors from other regions without consent. Empty means Explicit Consent Mode applies to every visitor worldwide, which is the strictest setting. If you list only the EU, visitors outside the EU are tracked before they answer the banner. See Explicit Consent Regions.
- Enable Google Consent Mode v2 in the Pixel Manager. The Pixel Manager sets the consent defaults for Google tags itself. CookieYes's own "Support GCM" toggle can stay on. If the CookieYes scanner then reports "Default consent set too late", read the troubleshooting entry below.
- Keep "Always send server-side events" switched off under Server-Side > General. That toggle deliberately sends server-side events even when consent blocked the pixels. With it off, neither the browser pixel nor the Conversions API sends anything before marketing consent.
- Leave the IAB TCF add-on in CookieYes switched off unless you sell programmatic ad inventory, and keep Google TCF Support in the Pixel Manager off as well. Google recommends running either TCF or Consent Mode, not both. See Google Ads stopped recording conversions below.
- Run a current Pixel Manager version. Same-page consent updates require version 1.42.5 or newer.
Nothing needs to be configured for detection. The Pixel Manager finds CookieYes on its own.
Verify the integration
- Open your shop in a private browser window, logged out of WordPress. Tracking is off for administrators by default, so a logged-in test shows nothing.
- Append
?pmwloggeronto the URL and open the browser console. See the Console Logger guide. - Before you answer the banner you should see:
Pixel Manager: CookieYes CMP consent detected
Pixel Manager: CMP consent applied from: CookieYes
Pixel Manager: The pixel has not loaded because you have not given consent for it yet. - mode: explicit, category: marketing, pixel: Facebook, source: cmp (CookieYes)
- Click "Accept all". The Pixel Manager logs that the approved categories were unlocked, for example
The category marketing has been approved. Loading the Facebook pixel, and the pixel scripts load on the same page without a reload. - To read the current state at any time, run
pmw.consent.categories.get()in the console.
If the first line is missing, CookieYes is not writing its cookie on that page. Check the troubleshooting section.
Troubleshooting
The admin says "None detected" but CookieYes is installed
If you load CookieYes from the CookieYes console rather than the WordPress plugin, this is expected. The admin card checks for the WordPress plugin only. The storefront integration does not depend on it.
To confirm the integration works, follow Verify the integration. If the console shows CookieYes CMP consent detected, everything is fine and the admin notice can be ignored.
If the console does not show that line:
- Confirm the CookieYes script is actually loaded on the storefront page and writes the
cookieyes-consentcookie. Open the browser's cookie inspector on a product page. - Disable script optimisation for the test. Plugins that delay, defer or combine JavaScript can load the Pixel Manager before CookieYes has written its cookie, or serve a stale Pixel Manager bundle after an update. The Caching and Optimization Exclusions page lists what to exclude.
- Clear all caches (plugin, server, CDN) and test again in a fresh private window.
- If you switched to CookieYes from another banner, a consent decision saved by the Pixel Manager before the switch can still be present in the browser. In the console,
CMP consent applied from: PMW cookie/storageinstead ofCookieYestells you that. Versions 1.66.0 and newer no longer store consent that a CMP relayed, and clear old records.
The general checklist is on the Platforms page under Your CMP shows as "None detected".
CookieYes reports "Default consent set too late"
This message comes from CookieYes's own Google Consent Mode scanner. It means a Google tag issued a request before CookieYes's default consent call ran. It does not affect the CookieYes integration described on this page, which is based on the cookie and the event, not on Google Consent Mode.
Two things to check:
- Explicit Consent Mode must be on. Shops that saw this warning together with a drop in GA4 and Meta events after installing CookieYes had Google Consent Mode v2 enabled but Explicit Consent Mode disabled. In that combination the Pixel Manager fires pixels before the visitor decides, and the scanner is right to complain. Enable Explicit Consent Mode and the Pixel Manager sets every Google consent default to denied before any tag runs.
- The Pixel Manager places gtag.js deliberately early. Scanners sometimes flag this placement. Google Tag Scanner Warnings: Why They're Wrong About Pixel Manager's gtag.js Placement explains the mechanism and why the placement is compliant.
Events dropped after installing CookieYes
A drop in GA4 sessions or Meta events right after installing a consent banner is expected to a degree: visitors who do not accept are no longer tracked. Two things make the drop larger than it should be:
- Explicit Consent Mode off. Pixels fire before the choice and are then blocked when the visitor declines, which produces inconsistent data. Enable Explicit Consent Mode.
- Reading the "update on save" column as a CookieYes limitation. CookieYes fires
cookieyes_consent_updateon the visitor's choice and the Pixel Manager loads the approved pixels immediately, so the first page view is measured once the visitor accepts. You do not need a different CMP for that.
Purchases are usually less affected than sessions, because the server-side purchase event carries the consent the shopper gave at checkout. The Pixel Manager suppresses the server-side purchase for shoppers who declined the relevant category. See Consent and server-side GA4 events.
Google Ads stopped recording conversions with CookieYes
If the IAB TCF v2.3 add-on is enabled in CookieYes, every request to Google carries a TCF consent string in addition to the Consent Mode signals. Google's documentation states that Google Ads does not record a conversion unless TCF purposes 7, 9 and 10 are granted, and recommends implementing only one of TCF or Consent Mode. We have seen a shop whose Google Ads conversion pings stopped the day it went live with this combination, while the Pixel Manager fired the purchase event correctly.
Unless you sell programmatic advertising inventory on your shop, switch the IAB TCF add-on off in CookieYes and keep Google TCF Support off in the Pixel Manager (Consent Management, Pro). Discuss the decision with whoever is responsible for your privacy setup. Background: Google TCF Support.
Version history
- 1.65.0 and newer: no version-specific requirements. Keep the plugin current.
- 1.42.4 and 1.42.5 (April 2024): the empty first-load cookie is handled, and the
cookieyes_consent_updatelistener applies consent on the same page view. - 1.32.4 (July 2023): support for the current
cookieyes-consentcookie after CookieYes changed its cookie names. - 1.7.5 and earlier: the original Cookie Law Info cookies were already read.
When to contact support
If the steps above do not resolve the issue, send us the following. It lets us reproduce your setup in one pass:
- Your store URL.
- The debug information from WooCommerce > Pixel Manager > Support.
- Whether CookieYes runs as the WordPress plugin or from the CookieYes console.
- A screenshot of the CookieYes Google Consent Mode settings, and whether the IAB TCF add-on is on.
- Which caching, script optimisation, or tag manager plugins are active.
- A screenshot of the browser console with
?pmwloggeron, taken in a private window while logged out of WordPress, before and after accepting the banner.
Pro customers use the support form. Free users find help in the WordPress.org support forum.
Frequently asked questions
Is CookieYes compatible with the Pixel Manager for WooCommerce?
Yes. CookieYes is a supported consent management platform. The Pixel Manager reads the CookieYes consent cookie and listens for its consent-update event, and blocks or unblocks the tracking scripts accordingly.
Is CookieYes supported by the Pixel Manager?
Yes, in the free and in the Pro version. No configuration is needed for the Pixel Manager to detect it.
Can I use CookieYes instead of Cookiebot with the Pixel Manager?
Yes. Both are supported. Cookiebot scores higher in our CMP ranking on technical criteria, but CookieYes works with the Pixel Manager, and we have customers running it in production. Follow the recommended configuration.
Does CookieYes require manual configuration with the Pixel Manager?
No. Detection is automatic. The settings we recommend in the Pixel Manager, Explicit Consent Mode above all, apply to every CMP, not only to CookieYes.
Why does the Pixel Manager say no CMP is detected when I use CookieYes?
Because the admin card only recognises the CookieYes WordPress plugin. If you load CookieYes from its console, the card shows "None detected" while the storefront integration works. Verify with the Console Logger.
I load CookieYes from the CookieYes console, not the WordPress plugin. Does the Pixel Manager detect it?
Yes. The console script writes the same cookie and fires the same event as the WordPress plugin. Only the informational admin card cannot see it.
Does CookieYes support "update on save"?
Yes. When the visitor accepts, CookieYes fires cookieyes_consent_update and the Pixel Manager loads the approved pixels on the same page. The first page view is measured without a reload.
Is CookieYes support a Pro feature?
No. All CMP integrations are included in the free version.
What does the PMW score of 66 mean?
The score rates the CMP against the technical criteria in our CMP ranking: standardised categories, Google Consent Mode support, ease of reading the consent cookie, documentation, and so on. It is not a compatibility verdict. CookieYes lost points mainly for changing its cookie names several times over the years, which the Pixel Manager compensates for by reading the old and the new cookies.
Does CookieYes need Google Consent Mode enabled?
The CookieYes integration does not depend on Google Consent Mode. We still recommend enabling Google Consent Mode v2 in the Pixel Manager so that Google can model conversions for visitors who decline. Enable it in the Pixel Manager, and enable Explicit Consent Mode alongside it.
