Which blocking should I use?

What types of blocking are available?

We support multiple ways of blocking cookies. Broadly speaking, there are 2 types of blocking

Automatic Blocking (default)

Our built in automatic blocking. This will aim to block any scripts that are setting the cookie that is trying to be blocked. Unfortunately blocking at the specific cookie level is not possible with 3rd party cookies and so the only way for us to do this automatically is by blocking the script that contributes to setting the cookies. Automatic blocking will also try to block 1st party cookies at the cookie level.

Note: We cannot guarantee that automatic blocking will block all cookies or work for all cases. You are responsible for testing your site and implementing manual blocking where auto blocking doesn't work. Unfortunately accurately blocking cookies automatically this simply isn't technically possible.

Manual Blocking

This is blocking that you setup yourself based on what the user opts in/out of. We supply the variables or triggers for when a user consents. You conditionally trigger scripts firing or setting of cookies based on the consent.

Which should I use?

We would always recommend manual blocking where possible. It will ensure you accurately block the cookies you are supposed to and prevents any other undesired blocking. In some cases where sites are simple and don't have many cookies, auto blocking may suffice.

If you are using our Google Tag Manager implementation, automatic blocking is unlikely to work for you. This is because of the way Tag Manager injects scripts.

How do I implement Manual Blocking?

Firstly determine if you are using our Script tag implementation or Google tag manager implementation/template. Then refer to relevant section below.

Script Tag implementation - JS API

We have a JS API available for use. This will let you check on whether or not the user has consented to a certain category and conditionally set script tags or perform JS logic based on this. For information on how to use this, How do I use the JS API?

Google Tag Manager implementation - Multiple options

There are multiple options for blocking when using our tag manager implementation. You don't need to pick one and can use a combination of all 3 to ensure you are blocking correctly.

Consent Mode supported Tags

Some GTM tags have built in consent checks and will adjust their behaviour based on this. We provide GTM with the consent state and update it if the user changes it, so these tags will work automatically with CookieScan.

Additional Consent checks

If the tag does not support built in consent checks, you can conditionally fire that tag depending on users consent. We provide GTM with the consent state automatically, simply follow the Google documentation here to conditionally fire tags.

JavaScript API

You can additionally use the JS API in order to control the setting of JS script tags or running of JS code based on user consent. For information on how to use this, How do I use the JS API?

Turn off auto blocking

Once you have implemented manual blocking, make sure you turn off auto blocking and test thoroughly.