Title: Error: Consent doesn’t update
Last modified: August 18, 2024

---

# Error: Consent doesn’t update

 *  Resolved [robineero](https://wordpress.org/support/users/robineero/)
 * (@robineero)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/error-consent-doesnt-update/)
 * I use CookieYes plugin, not a premium user and it is NOT connected to CookieYes
   web app (because I run out of the free tier limits otherwise). It works really
   well for managing cookie consents.
 * I have tried to implement Google Consent Mode using the [Method 2: Implementation using the custom script](https://www.cookieyes.com/documentation/google-consent-mode-v2-upgrade/#Method_2_I_8:~:text=Republish%20the%20script.-,Method%202%3A%20Implementation%20using%20the%20custom%20script,-For%20existing%20users)
   but the GCM status check on CookieYes web app gives the **Error: Consent doesn’t
   update**.
 * What would be the suggested way to implement Google Consent Mode using this setup
   or is there a way to get it to work at all?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [CookieYes Team](https://wordpress.org/support/users/cookieyesteam/)
 * (@cookieyesteam)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/error-consent-doesnt-update/#post-17963957)
 * Hi [@robineero](https://wordpress.org/support/users/robineero/),
 * Greetings from CookieYes!
 * The Google consent mode will work only for CookieYes-connected websites.
 *  Thread Starter [robineero](https://wordpress.org/support/users/robineero/)
 * (@robineero)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/error-consent-doesnt-update/#post-17964794)
 * Can you please confirm that unless CookieYes WP plugin is connected with web 
   app then there is **absolutely no way** to get Google Consent Mode to work.
 * I don’t mean being able to turn it on and off in the web app but I mean getting
   it to work (without using web app UI at all). CookeYes plugin works very well
   but not being able to implement consent mode at all without premium… does not
   make life simpler 🙂
 *  Plugin Support [CookieYes Team](https://wordpress.org/support/users/cookieyesteam/)
 * (@cookieyesteam)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/error-consent-doesnt-update/#post-17977144)
 * Hi [@robineero](https://wordpress.org/support/users/robineero/),
 * The GCM feature available in our plugin will work only for CookieYes-connected
   websites. You may try the Consent mode feature in the Google site kit plugin,
   which works with the WP Consent API. Our latest release [v 3.2.6] is integrated
   with WP Consent API.
 *  Plugin Support [CookieYes Team](https://wordpress.org/support/users/cookieyesteam/)
 * (@cookieyesteam)
 * [1 year, 9 months ago](https://wordpress.org/support/topic/error-consent-doesnt-update/#post-17988765)
 * Hi [@robineero](https://wordpress.org/support/users/robineero/),
 * This thread has been inactive for a bit, so we are going to mark it as resolved
   now. Please feel free to open a new thread or follow-up if you have any further
   questions or still need help.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Error: Consent doesn’t update’ 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: [CookieYes Team](https://wordpress.org/support/users/cookieyesteam/)
 * Last activity: [1 year, 9 months ago](https://wordpress.org/support/topic/error-consent-doesnt-update/#post-17988765)
 * Status: resolved