All Collections
Data Protection
Cookie Consent Widget
Cookie Consent Widget

Setup the Cookie Consent Widget

Niall Diamond avatar
Written by Niall Diamond
Updated over a week ago

Setting up a cookie consent widget is an essential step for websites to comply with the General Data Protection Regulation (GDPR) in the European Union. The GDPR requires websites to obtain explicit consent from users before storing or accessing cookies on their devices, except for cookies strictly necessary for the operation of the site. This article will guide you through the basics of implementing a cookie consent mechanism, either by using an internal widget developed by your team or by integrating a compliant third-party solution like Cookiebot.

Why Cookie Consent is Important

Cookie consent is not just a legal requirement; it's a crucial aspect of user privacy and trust. By transparently managing cookies and obtaining consent, websites demonstrate their commitment to protecting user data. This is vital in today's digital landscape, where privacy concerns are increasingly at the forefront of users' minds.

Choosing the Right Cookie Consent Solution

There are two choices for setting up a cookie consent widget:

  1. EvoX cookie consent widget

    1. Built and supported by EvoX

  2. Consent Management Platform

    1. Paid for third party software

Below is an explanation of both to help you choose the right solution for your company.

EvoX Cookie Consent Widget

Pros

  1. Easy setup

  2. Works with Google Analytics App

  3. Supports Google Consent V2

    1.   'ad_storage': 'granted',
      'ad_user_data': 'granted',
      'ad_personalization': 'granted',
      'analytics_storage': 'granted'
  4. Consent saved on the users browser

  5. Uses Google Tag Manager and thus ready to support Third party cookies via Tag Manager.

Cons

  1. Doesn't automatically find Third party cookies.

  2. No easy access to stored user consent or history

  3. No storage of consent verbiage changes

Consent Management Platforms

The second option is to choose to use a CMP that is supported by Google. These can be setup by you manually or with the help of your developer. They can be configured to work with any third party cookie providers.

Recommended CMP - Cookiebot

Pros

  1. Can detect cookie automatically

  2. Supports Google's Consent V2

  3. Admin that stores user consent, consent history, and consent verbiage.

  4. Typically supports EvoX Google Analytics App and Google Tag Manager

Cons

  1. More complex to setup

  2. Not supported by EvoX customer success team

  3. Paid service

You can choose either a CMP or the EvoX cookie consent widget. Your choice should be determined by your companies needs and that meets your companies legal requirements.

Setup the EvoX Cookie Consent Widget

Edit the Footer Layout by adding or updating your Cookie widget settings:

  1. Add the cookie policies widget to the footer layout if it isn't already there (using drag and drop from the widgets tab).

  2. Open the widget settings from it's location on the layout so you can customise the messaging and options.

  3. When settings are complete, click save on the widget and click save on the layout. Check that the widget is working by using an incognito browser session to visit your site and set your preferences.

    πŸ‘ Important: Set the Position to "Float Bottom" or "Float Top"

Add a link to the cookie preferences

Once the user makes their selection the above cookie modal will disappear. Add a link in the footer of your pages to all them them to change their preferences.

Create a Custom link item

And you simply need to add the class "trigger-cookie-modal"

For a more customised experience you can create a Custom HTML item

Custom HTML Example

<button class="trigger-cookie-modal">Manage Cookie Preferences</button>

Create a Cookie Content Page

Now make sure to create a cookie content page and privacy page and link to them in your Cookie Widget.

FAQ

EvoX Cookie Widget:

Are user's cookie preferences stored?

Yes, on the users browser.

Can the users preferences be accessed?

Yes, they can find the preferences by opening inspect element on their browser. We do the same storage for all users (logged in or logged out)

What does the "customise user ads consent preference" do? How does it work?

When a user consents we send the following in Google Tag Manager.

User preference

Granted

Denied

Storage consent

'analytics_storage': 'granted'
'analytics_storage': 'denied'

Ads consent

'ad_storage': 'granted',
'ad_user_data': 'granted',
'ad_personalization': 'granted'
'ad_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied'

Is the EvoX Widget compatible with Google Consent V2?

Yes, we pass the new parameters to Google Tag Manager (ad_personalization, ad_user_data).


That's it, have a Great Day πŸš€

Did this answer your question?