Skip to main content

Google Consent Mode Troubleshooting with CookieYes

Last updated on June 21, 2024

This guide aims to provide solutions to common problems that may arise during the Google Consent Mode integration process on your website.

Note

This guide is for users who have implemented Google Consent Mode on their website. For instructions on setting up GCM, refer this document.

Select an issue to see troubleshooting instructions.

The consent tab appears empty if Google Consent Mode is not implemented on your website or if no consent data is collected.

  1. Ensure Support GCM is enabled from the Advanced Settings page in CookieYes.
  2. Unblock Google tags by enabling Allow Google tags to fire before consent.

    advanced gcm

    For further reference, checkout Google’s documentation on unblocking Google tags .
  3. Verify that Google Consent Mode is working correctly. 
    You can do this using the Tag Assistant debug console. Refer to this guide for instructions.

This error occurs when the default consent state has not been defined or properly configured during the setup of the CookieYes CMP Tag in GTM. The issue can also occur if you used the Custom Script method to implement GCM but either missed adding the custom script or included a script with missing elements.

If you’ve implemented Google Consent Mode using the CookieYes CMP template:

  1. Update the CookieYes CMP tag. To do so,
    • In the Google Tag Manager workspace, click Templates in the left sidebar and locate the CookieYes CMP template. 
    • Click on the Update icon.update CookieYes CMP
  2. Ensure proper setup of default consent settings by following these steps:
    • From the Tag Manager workspace, select Tags from the left sidebar. Next, click on the CookieYes CMP tag and then click the edit icon.
    • Click Add Setting.
    • Select Enabled/Disabled from the drop down for each cookie category based on your requirements.
    • Set the Region by entering the region’s ISO-standardised (ISO 3166-2) codes for the specific regions you intend to Geo-target with your banner. If you prefer not to Geo-target your banner to specific regions around the globe, enter All in the Regions field. Refer to the ISO 3166-2 standard for the appropriate region codes.
    • Click Add.

      add settings
    • Submit and Publish the changes to your google tag manager container.

If you used Custom Script method to implement GCM, update script to the latest version (Consent Mode v2).

This error occurs when the consent preferences of users are not properly updated or recorded.

  1. Make sure you have enabled Support GCM from the CookieYes Dashboard


  2. Update CookieYes CMP tag.
  3. Ensure the CookieYes CMP tag is fired first, before any other tags on the website.
  4. Make sure you submit and publish the changes to your Google Tag Manager container with every change you make.

    submit button
  5. If you’ve used the Custom Script method to implement GCM, update the script to the latest version (Consent Mode v2).

This error occurs when other tags are read/fired before the default consent is set.

Tag Assistant reports the error:
error

  1. Ensure that the trigger, Consent Initialization – All pages is set only for the CookieYes CMP Tag, i.e. CookieYes CMP tag is fired first, before any other tags.

    cy cmp tag
  2. Verify that all directly loaded tags are fired only after GTM is completely loaded. To verify, 
    a. Open Tag Assistant debug console.
    b. In the Summary, select the Tags tab.
    c. Click a tag to check if it fired according to the consent settings.
  3. If you used Custom Script method to implement GCM, check the order of the script is as follows:
    i. Custom Consent Mode script
    ii. gtag / GTM script
    iii. CookieYes script
  4. Ensure you do not place other scripts above the Custom Consent Mode script.

Refer to this troubleshooting guide by Google for additional help.

Have more questions?

Reach out to us and we'll answer them.

Contact us