Cookies Declined

Hi Pete,

Thanks for reaching out!

Just installed your WordPress plugin on our site, but I’m not sure how much more I need to do to configure it?

With the plugin installed, will it (for example) stop Google Analytic cookies being dropped on a user’s computer if they refuse cookies? Or is further work needed?

Once you’ve installed the Cookiebot plugin, your site is not necessarily GDPR complaint, until you mark your cookie setting script tags with Cookiebots data attributes.

You can find more information on how to do that at our help page:

https://www.cookiebot.com/goto/help

After you’ve installed the Cookiebot plugin, you need to scan your website for cookies.

If you’re already signed up, you can request a scan for your domain through our manager:

https://manage.cookiebot.com/, under the “Cookies” tab.

Once the scan is complete, you can check the scan report, under the “Reports” tab, which shows all cookies our scanner found, and which JavaScript files set those cookies.

Once you have that information, you should be able to mark your script tags.

Also, I get how to apply the attribute “data-cookieconsent” on cookie-setting scripts – but the GA example applies to the Universal script tag, not the Global Site Tag (gtag) we use. Is there a significant difference to apply this?

There is no difference, you can use the same data attribute on the Global Site Tag. Alternatively, you can choose to control the cookie consent for Global Site Tag through Google Tag Manager:

https://cybot.uservoice.com/knowledgebase/articles/425087-google-tag-manager-deployment

[ Signature deleted ]

• This reply was modified 6 years, 11 months ago by cookiebot.
• This reply was modified 6 years, 9 months ago by Jan Dembowski.

Thanks for replying.

As far as the Google Analytics point is concerned, where would I apply the attribute if the tracking code looks like this?

<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXX-X"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'UA-XXXXXXXX-X');
</script>

The first script tag or the second?

Step 3 on our help page describes what you have to do:

To enable prior consent, apply the attribute “data-cookieconsent” to cookie-setting script tags on your website. Set the comma-separated value to one or more of the cookie categories “preferences”, “statistics” and “marketing” in accordance with the types of cookies being set by each script. Finally change the attribute “type” from “text/javascript” to “text/plain”

Example:

<!-- Global site tag (gtag.js) - Google Analytics -->
<script type="text/plain" data-cookieconsent="statistics" async src="https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXX-X"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'UA-XXXXXXXX-X');
</script>

This will ensure that gtag.js is executed when the user gives consent to statistics cookies.

If you are using gtag for marketing purposes as well, you have to use

data-cookieconsent=”statistics,marketing”

Example:

<!-- Global site tag (gtag.js) - Google Analytics -->
<script type="text/plain" data-cookieconsent="statistics,marketing" async src="https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXX-X"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'UA-XXXXXXXX-X');
</script>

[ Signature deleted ]

• This reply was modified 6 years, 9 months ago by Jan Dembowski.