Title: Google Consent Mode debugger showing wrong error Last modified: May 30, 2025 --- # Google Consent Mode debugger showing wrong error * Resolved [alekv](https://wordpress.org/support/users/alekv/) * (@alekv) * [1 year ago](https://wordpress.org/support/topic/google-consent-mode-debugger-showing-wrong-error/) * Hi * I am the developer of the [Pixel Manager for WooCommerce](https://wordpress.org/plugins/woocommerce-google-adwords-conversion-tracking-tag/). We get support requests of people showing us that CookieYes detected and error with the Google Consent Mode: [https://cln.sh/NrQwRGGJ](https://cln.sh/NrQwRGGJ) * However, this is wrong when the Pixel Manager is active. Here is an example that shows that the Google Consent mode is loaded just fine: [https://cln.sh/2fbm01w1](https://cln.sh/2fbm01w1) * In this particular case, it happens because the [lazy load feature](https://sweetcode.com/docs/wpm/plugin-configuration/general-settings#lazy-load-the-pixel-manager) of the Pixel Manager has been enabled, which loads the Pixel Manager only after user interaction. * In those cases, CookieYes is not able to correctly detect the Google consent mode configuration. * Could you please fix this? It creates unnecessary support requests on our side and probably many more unsatisfied customers. Even though everything works fine on our side, Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Support [Ryan (CookieYes Support)](https://wordpress.org/support/users/ryancysupport/) * (@ryancysupport) * [1 year ago](https://wordpress.org/support/topic/google-consent-mode-debugger-showing-wrong-error/#post-18490314) * Hello [@alekv](https://wordpress.org/support/users/alekv/), * We understand your frustration with the false error detection when using Pixel Manager’s lazy load feature. This issue is similar to what we’ve seen with other optimization tools like WP Rocket. * The problem occurs because our Google Consent Mode checker runs its verification before your lazy-loaded scripts are triggered by user interaction. When the checker runs, it can’t detect the properly configured consent mode because it hasn’t been loaded yet. * This is a known limitation with optimization tools that delay script loading until user interaction. When we check for GCM configuration, we’re looking for specific elements that aren’t present until after user interaction triggers your lazy load. * To verify this is working correctly, you could temporarily disable the lazy load feature when running our “Check GCM status” button in Advanced Settings, then re-enable it afterward. Additionally, You can follow the other methodes outlined in the documentation [https://www.cookieyes.com/documentation/check-proper-implementation-of-gcm/](https://www.cookieyes.com/documentation/check-proper-implementation-of-gcm/) * We appreciate you bringing this to our attention and we’ll look into improving our detection to better handle lazy-loaded implementations. * Thread Starter [alekv](https://wordpress.org/support/users/alekv/) * (@alekv) * [1 year ago](https://wordpress.org/support/topic/google-consent-mode-debugger-showing-wrong-error/#post-18490380) * Thanks for your quick response! * The only way such a GCM status check could and should be run is by detecting the GCM network calls on the website. For that, you could use something like Cypress or Playwright where you also could simulate a user interaction before doing the test. * If you can’t do that, please, at least, when showing the GCM warning, also explain what the limitations of your check are. * Plugin Support [Ryan (CookieYes Support)](https://wordpress.org/support/users/ryancysupport/) * (@ryancysupport) * [1 year ago](https://wordpress.org/support/topic/google-consent-mode-debugger-showing-wrong-error/#post-18490701) * Hi [@alekv](https://wordpress.org/support/users/alekv/), * Thank you for your thoughtful feedback. * We understand the limitations of our current detection method. While simulating user interaction and detecting GCM via network calls using tools like Cypress or Playwright would offer a more accurate assessment, it’s not a feasible option for us at the moment due to the complexity and performance considerations involved. * That said, we do acknowledge the importance of transparency. As per your suggestion, we will look into updating the GCM warning message to clearly explain the limitations of our current check, particularly when lazy-loading mechanisms delay script execution beyond our verification timing. * We truly appreciate your collaboration and will keep working to improve compatibility with tools like Pixel Manager. * Plugin Support [Ryan (CookieYes Support)](https://wordpress.org/support/users/ryancysupport/) * (@ryancysupport) * [12 months ago](https://wordpress.org/support/topic/google-consent-mode-debugger-showing-wrong-error/#post-18504973) * Hello [@alekv](https://wordpress.org/support/users/alekv/), * It has been quite some time since our last communication. As we did not receive any follow-up questions from you, we will mark this thread as resolved. Please open a new thread if you still have questions that require our attention. Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Google Consent Mode debugger showing wrong error’ is closed to new replies. * ![](https://ps.w.org/cookie-law-info/assets/icon.svg?rev=3007243) * [CookieYes – Cookie Banner for Cookie Consent (Easy to setup GDPR/CCPA Compliant Cookie Notice)](https://wordpress.org/plugins/cookie-law-info/) * [Frequently Asked Questions](https://wordpress.org/plugins/cookie-law-info/#faq) * [Support Threads](https://wordpress.org/support/plugin/cookie-law-info/) * [Active Topics](https://wordpress.org/support/plugin/cookie-law-info/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/cookie-law-info/unresolved/) * [Reviews](https://wordpress.org/support/plugin/cookie-law-info/reviews/) * 4 replies * 2 participants * Last reply from: [Ryan (CookieYes Support)](https://wordpress.org/support/users/ryancysupport/) * Last activity: [12 months ago](https://wordpress.org/support/topic/google-consent-mode-debugger-showing-wrong-error/#post-18504973) * Status: resolved