How to geographically target your cookie compliance

General Data Protection Regulation (GDPR) is a regulation created for all websites that operate and collect user data within EU member states. It is not required to collect consent from visitors coming outside of the European Union.

A similar rule applies to California Consumer Privacy Act (CCPA), so some websites might be interested in showing cookie consent popup only for visitors from California.

In order to meet our client demand, we have created an option to only target visitors coming from EU countries, only visitors coming from California, or visitors coming from one of those locations. This can be set when getting the code of your item by selecting a geo-targeting mode. Go to your CookieScript user account > Settings > Install, where you will find geo-targeting options:

Select between a Global or a Custom geo-targeting option. New code will be generated, which should be copied and used on your website.

Since GDPR and CCPA regulations are very different, we have added the possibility to include different banners for different locations. So you can set up two different cookie banners (with different settings) and add one with EU geo-targeting and another with California geo-targeting. They will not conflict with each other and the proper script will be taken for each location. Visitors coming from somewhere else will not see the banner, all disabled third-party scripts (if you have any) will get enabled automatically.

Few more things to note when using geo-targeting:

Note: The geo-targeting functionality does not function when it is simply saved in your banner. You have to choose proper geo-targeting, then copy generated code and insert it to your website/GTM. Geo-targeting is part of the generated code.

Note: It requires you to update the CookieScript code on your website if you are not using EU geo-targeting yet.

Note: All third-party scripts will be automatically activated if a visitor comes outside of the geo-targeted location.

Note: Geo-targeting does not work with self-hosted code since visitor IP is checked on CookieScript servers.