How to Setup Cookie-Script with Google Tag Manager

The Cookie-Script is one of the most widespread platforms for Cookie Consent. Besides GDPR, it supports many other privacy regulations (GDPR, CCPA, LGPD, CNIL).

It offers a Free plan: 2 domains, 20,000 pageviews monthly, cookie manager. There is an option for “RELOAD PAGE AFTER A USER ALLOWS/REJECTS COOKIES”. The free plan does not provide scheduled cookie scans (can be done manually – 10 pages per scan), nor does it offer statistics.

Check the available packages here.

It has an affiliate program.

Cookie-Script is a Google Certified CMP Partner.

The installation will be done using Google Consent Mode (GCM), which is the most widespread technique. It should be noted that there is also an alternative technique (more strict) using blocking triggers.

If you use Google Advertising, Google Consent Mode v2 is mandatory for European traffic, from March 2024. Details here.

If you use Google Advertising, Google Consent Mode v2 is mandatory for European traffic, from March 2024. Details here.

Basic Installation

The basic installation is described here and includes using a template from the Community Library (CookieScript CMP (Consent Mode)) of Google Tag Manager.

cookie-script GTM template
cookie-script GTM template

Google Consent Mode

Next, the Google Consent Mode (GCM) should be enabled from the container settings (if not already enabled).

It should be noted that only Google Tags (GA4, Google Ads, Conversion Linker, and Floodlight) have built-in Consent Mode. For other tags (e.g., Facebook Pixel, Linkedin Insight, TikTok pixel, etc.), the level at which they fire or not must be defined.

In most cases, these settings are sufficient.

IAB TCF v2.2 Compliance with Cookie-Script

Cookie-Script is now compatible with the Transparency & Consent Framework (TCF) TCF2.2 (replacing TCF2.0) according to IAB.

This change is significant for Ad Publishers:

If you do not migrate by the required deadline of November 20, 2023, any TC strings obtained under TCF v2.0 after that date will be considered invalid. This could adversely affect your agreements with advertisers, potentially resulting in a decrease in your ad revenues.


However, this feature is only available in paid plans.

cookie-script tcf2.2
cookie-script tcf2.2

Privacy trigger position

Often, the privacy trigger (the icon that changes user preferences) needs to be moved. It is supported in paid plans, but it can also be done in the free plan easily with a simple CSS like:

#cookiescript_badge {
	margin-left: 100px;
	margin-bottom: 10px;


Shopping Cart
Scroll to Top