What does Cookie autoblocking do?
The cookie autoblocking feature will block cookies by default that are set directly on the root domain and are considered the first party. "First-party" includes cookies that are set by you on your own websites, as well as services such as Facebook and Google Analytics.
The root domain is the main domain that a visitor would type into their address bar in order to visit your site - e.g. cookieinformation.com
How do I enable Cookie autoblocking?
If you have created a Consent Solution recently, then this feature will be enabled by default. However, if you created your Consent Solution quite some time ago then you can now enable this feature yourself by doing the following:
Go to the Consent Solution you'd like to enable the autoblocking cookie feature on.
Click on the "Languages and Settings" tab
Click the button "Enable Cookie autoblocking"
How do I know the Cookie Autoblocking is working?
You can see if it has worked by visiting your website, right-clicking and choosing Inspect, and then going to the Application tab. Clear all cookies, and then reload the page.
You will then see the Consent Pop-up re-appear. Go to the Cookies menu and you'll be able to see that all First-Party cookies have now been blocked.
Before consenting to cookies (only Necessary category is loaded):
After consenting to cookies (all categories):
Is there anything else I need to do other than turning it on?
For best results (and to make sure that there aren't any conflicts) we recommend removing our manual SDK on any services that set first-party cookies - the Cookie Control SDK that is implemented via Google Tag Manager.
Is there anything I need to be aware of when using it?
Please do not re-classify the CookieInformation cookie that is provided by us (a necessary cookie). In order for the feature to work correctly, it must remain a necessary cookie.
As the Cookie Autoblocking feature blocks the cookie rather than the script, this means that in some cases certain services may still continue to work (so long as they are not dependant on the cookie set for their functionality).
How do I know which services set a first-party cookie?
You'll be able to tell which services are setting a first-party cookie because they'll have you as the "data processor". If you're unsure, take a look at:
The pop-up to see which cookies are provided by you
The application menu to see which cookies are directly set on the root domain
Are there any downsides to using the Cookie autoblocking feature?
There are two relatively minor downsides to using our Cookie autoblocking feature - one of which can be mitigated:
If you leave the manual Cookie Control SDK in place entirely and don't remove the SDK on services that set a first-party cookie, then our own cookie Knowledge Base classifications or your own classification in Google Tag Manager (whichever cookie_cat_xxx category you've chosen) may overwrite the autoblocking classification.
The library used for this autoblocking feature may have a very small impact on page loading times (around 15ms). As the library is always loaded (regardless of whether you have turned it on or not), it may affect you - even if you have not chosen to enable this feature.
How does this affect the cookies I have manually added to the pop-up myself?
If you have added a cookie yourself (e.g. if it's only set behind a login, or it didn't appear on the pop-up after our scanner crawled your domain), then it will also be handled by our autoblocking cookie feature provided that the cookie has been added as first-party.
Didn't find the answer you needed? Write to us at email@example.com