FTDNA Sales Banner
Ads and affiliate links like this help support the Q-M242 project's efforts to test indigenous peoples. Please read the affiliateship and business disclaimers for details. You may also donate directly here.

GDPR & The Genealogy Blogger in 2019 – That Cookie Banner

GDPR was not and is not Cookie Banner legislation. One cannot be too clear on that. It is not.

But…

It clarified already existing Cookie Banner legislation that everyone should have been following already for EU site users.

It took away some options that site owners have been using. Those included implied consent in the wording. You know… “By continuing to use this site, you agree to our site policies and the use of cookies…”

It took away accepting by clicking a close button or scrolling. Nope. You need to click a button that says you accepted. Explicit acceptance is a must unless you want to use one of the other ways of meeting GDPR requirements. I assure you, just asking people to click a button will be easier.

It made most of the easy to use Cookie Banner tools out there completely useless for GDPR compliance.

I have spent weeks scratching my head and looking at options. Here they are:

  • OneTrustOneTrust has an amazing website. I absolutely love their admin interface. Their prices are reasonable for a large site, and they have a free version. They let you run a new scan when you wish. Unfortunately, their scripts caused errors in my browser console.
  • CookieBotCookieBot has a nice site. They offer essential functions in their admin panel. Their prices are high if you have more than 100 pages on your site. They only scan your site once a month.
  • ConsentlyConsently has a lovely little site. They have designed the consent process to be built into a tag manager. Their prices are reasonable. Unfortunately, they do not have the ability to handle embedded items on site pages like YouTube videos yet.

After trying the other two, for now CookieBot is the only usable choice. Here is what is needed to get the basic code up.

  1. Go to the CookieBot website.
  2. On the upper right, click on the free trial offer.
  3. You will get a registration key sent to the email address you enter when you sign up.
  4. Enter the key back on the CookieBot website.

Your account is now ready.

The first page, Domains, lets you add websites. Be aware that the first scan will run as soon as you enter the site address. Therefore, you want to have done the rest of the prep and removed any old banner code before you add your website.

The next page is the user Dialog. Under GDPR, the method must be Explicit Consent. I suggest pre-selecting all three cookie types. This gets you the best chance of obtaining consent for them.

The third page allows you to change the Declaration. You cannot edit this if you have a free account.

Next is the Content page. They have filled in basic text, but you can change it as you wish. Paid accounts can also add multiple languages.

Finally, there is the scripts page. To add the banner to your website, you need the first script on the page.

Save all of your changes.

You are now ready to add the script to your website. I have a WordPress site and use the Header Footer Code Manager plugin to handle adding code to my pages. I highly recommend it.

First we want to create a new snippet by clicking the Add New Snippet button.

CookieBot Setup Snippet

On the next page, enter a name for the snippet. I have named this one CookieBot.

CookieBot Setup Snippet 2

Now you can scroll down and enter the CookieBot script.

CookieBot Setup Snippet 3

Once you hit save, you are done. You can now go back to the CookieBot site and add your website to the Domains page.

CookieBot Setup 6

Save your work again. The site should indicate that your first scan has been scheduled. I suggest leaving everything to run and coming back after a day.

In the next instalment I will go over how to ensure scripts do not run until consent is given.

Posts in Series

Sources & Resources

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

you're currently offline