How to Setup CookieYes with Google Tag Manager

The CookieYes is one of the most popular platforms for Cookie Consent. Apart from GDPR, it supports many other policies that can be applied depending on the visitor’s region.

It should be noted that it offers a generous Free plan: 1 domain, 25,000 pageviews monthly, very good statistics, excellent cookie detection and classification (cookie manager). There is an option “Reload page on consent action”. The free plan lacks scheduled cookie scans (can be done manually – 100 pages per scan).

See on the page Compare plans.

It has an affiliate program.

CookieYes is a Google Certified CMP Partner.

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

Basic Installation

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

Cookieyes CMP tag
Cookieyes CMP tag

After the basic installation, during the GTM PREVIEW process, one can notice a new event being pushed into the dataLayer, the cookie_consent_update.

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.

See also

Cookie Consent Update Trigger

One might expect these settings to be sufficient. This is the case with the platform Cookie-Script. However, as with the installation of CookieBot, an additional trigger will be needed for everything to work correctly when the user’s consent changes.

cookie_consent_update Trigger
cookie_consent_update Trigger

IAB TCF v2.2 Compliance with CookieYes

CookieYes 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 available only in the (higher) paid plans:

cookieyes tcf2.2
cookieyes tcf2.2

Privacy trigger (Revisit Consent Button) 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:

.cky-revisit-bottom-left {
    left: 120px !important;
    bottom: 20px !important


Shopping Cart
Scroll to Top