How to Implement Prior Consent and Cookie Auto-Blocking

Under GDPR, you need to take consent for any cookies that are not necessary for the technical functionalities of a website. This means any cookie that does not fall under the category of strictly necessary cookies should not be set on the user's browser until they have given their consent to use it.

So, until the users have not given prior consent until then all the cookies should be blocked and there should be no data collected from the users. Also, the cookies should not be set if the users have rejected the use of cookies.

If you are new to CookieYes, sign up here.

You can effectively block scripts before obtaining user consent using CookieYes settings. In this method, you need to specify the script URL pattern (a pattern that matches the URLs of the scripts) to block cookies set by third-party scripts. CookieYes will recognize any script that matches that pattern and prevent it from setting cookies on your website users' browsers until they provide their consent, ensuring that user data isn't collected through cookies without proper consent.

To implement this, click on the Cookie Manager on the top navigation panel. Here, you can see different categories of cookies – necessary, non-necessary (functional, analytics, performance, advertisement) and uncategorised. Cookies that haven't been categorized yet are listed under "Uncategorized."

To block a specific cookie under a particular category (non-necessary or uncategorized), navigate to that category and click the + Add Cookie button.

Here you can give details such as Cookie ID, domain, duration and description. To block the script, enter the Script URL Pattern of the third party to block cookies from them.

If a third-party script with the code <script async src='https://www.example-analytics.com/analytics.js'></script> sets a cookie, you can specify its "Script URL Pattern" as example-analytics.com.

<script async data-cookieyes="cookieyes-analytics" src="https://www.googletagmanager.com/gtag/js?id=UA-144842869-1"></script>

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'UA-144842869-1');
</script>

<script async data-cookieyes="cookieyes-analytics" src="https://www.googletagmanager.com/gtag/js?id=UA-144842869-1"></script>

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'UA-144842869-1');
</script>

<script>
function executeScript() {
    // Executed only if "analytics" category is accepted
    const script = document.createElement("script");
    script.setAttribute("src", "<URL of your script>");
    document.body.appendChild(script);
}

function handleConsentUpdate(eventData) {
    const data = eventData.detail;
    if (data.accepted.includes("analytics")) executeScript();
}

document.addEventListener('cookieyes_banner_load', (eventData) => {
    const data = eventData.detail;
    if (data.categories.analytics) {
        executeScript();
    } else {
        document.addEventListener('cookieyes_consent_update', handleConsentUpdate);
    }
});
</script>

<script>
function executeScript() {
    // Executed only if "analytics" category is accepted
    const script = document.createElement("script");
    script.setAttribute("src", "<URL of your script>");
    document.body.appendChild(script);
}

function handleConsentUpdate(eventData) {
    const data = eventData.detail;
    if (data.accepted.includes("analytics")) executeScript();
}

document.addEventListener('cookieyes_banner_load', (eventData) => {
    const data = eventData.detail;
    if (data.categories.analytics) {
        executeScript();
    } else {
        document.addEventListener('cookieyes_consent_update', handleConsentUpdate);
    }
});
</script>

This script can be pasted into your base HTML file by replacing <URL of your script> with the URL of your script file.

Note:

The category names to be added in the blocking code above are pre-defined in CookieYes. They are ‘functional’, ‘performance’, ‘analytics’, and ‘advertisement’.

CookieYes allows you to classify cookies into categories according to their purpose. This allows the users of the website to enable and disable cookies in each category, giving granular control over the cookies based on their purpose.

For example, if your website has cookies in three categories, namely Advertisement, Analytics, and Performance, and the user decides to allow only the Performance cookies, then the scripts for only the "Performance" cookies will be installed on the website when they click on Accept.

But to ensure that the cookies of only the selected category are used when given consent, make sure that the scripts of that cookies are added in the right category. Or if the 'data-cookieyes' attribute is used, assign the right attribute value according to the category based on the type of cookies being set by the scripts.

For example, the scripts for Google Analytics should be added in the scripts section of the Analytics category. This will ensure that if the user turns off the Analytics category, the Google Analytics scripts will not be rendered and vice versa.

Note:

The users cannot disable the cookies that are categorized as type Necessary. The website does not need to have user consent to be using them.

To ensure that the cookies are blocked and added when the consent is recorded, you can use the developer console of your user. First, load your website after clearing all the current cookies on the browser or checking from a private browser window. After the site has been loaded, check the developer console if any cookies have been set.

Follow the steps to identify cookies set on the browser for Chrome:

Right-click on the page, and click on inspect. This will open up the developer console. From the developer console, go to the Applications tab and then click on the cookies dropdown. This will show all the cookies that are being set on the browser by the website.

Note:

Cookies are only blocked according to consent in the “Explicit” and “Implicit” consent type. In the Info consent type, cookies are not blocked at all.

How to Implement Prior Consent and Cookie Auto-Blocking

On this page

How to Block Cookies Using CookieYes?

1. Adding script URL

2. Adding Blocking Code to the Script

Giving Granular Control Over the Cookies.

How to Ensure That the Cookies are Being Blocked?

Have more questions?