Features Pricing Documentation Blog For agencies Contact
Sign in Try for free
Documentation / Banner changes

Banner changes (client.js)

We record the banner script versions we deploy here (since 18 August 2026). Changes that affect when or what the banner sends to Google Consent Mode, dataLayer, Meta or Microsoft UET are marked.

You can find the banner version on your website in the browser console with the command cookienovoDebug.version.

What the banner sends (current version)

  • The banner does not send the default consent state. It is set by the code in the head of your website (Step 1) or by the Cookienovo template in GTM.
  • The banner sends a Consent Mode update as soon as the visitor makes a choice and then on every page load. On pages with a Google tag (GTM or gtag.js), visitors who have not decided also get it on page load, with the denied state; decided visitors may get it twice there.
  • It sends the Consent Mode update only if Google Consent Mode v2 is enabled in the banner settings.
  • Analytics cookies → analytics_storage. Marketing → ad_storage, ad_user_data, ad_personalization. Functional → functionality_storage, personalization_storage.
  • With every update (even with Consent Mode disabled) it pushes the event cookie_consent_update to the dataLayer and, for each allowed category, one of the events cookie_consent_statistics, cookie_consent_marketing, cookie_consent_preferences.
  • Based on the marketing category, it also sends consent for Microsoft UET (ad_storage) and, if the Meta pixel is on the page, for Meta (grant / revoke).
  • On pages with GTM, it sends visitors who have not decided the denied state for Microsoft UET and, if the Meta pixel is on the page, a consent revoke for Meta.
  • It stores the visitor’s choice in the cookie cn-consent and a copy of it in localStorage under the key cn-consent-mirror.

Versions

2026-11-15 · version 20261115-1717

Changes consent signals (Consent Mode, dataLayer, Meta, Microsoft UET).

  • Return to the behaviour before 10 November 2026 (identical to version 20261013-1428). The change from version 20261110-1441 is cancelled: on pages with a Google tag (GTM or gtag.js), the banner again sends a Consent Mode update and the cookie_consent_update event on page load also to visitors who have not decided, with the denied state.
  • A separate update after requesting consent again (from version 20261110-1441) is no longer sent; a visitor who has not decided gets the denied state on page load.

2026-11-10 · version 20261110-1441

Changes consent signals (Consent Mode, dataLayer, Meta, Microsoft UET).

  • On pages with GTM, the banner used to send a Consent Mode update and the cookie_consent_update dataLayer event to every visitor on page load. Now it sends them only to visitors who have made a choice.
  • A visitor who has not decided keeps only the default state set by the code on your website or by the GTM template and does not receive the cookie_consent_update event on page load. Previously they received an update with the denied state, which overrode regional defaults.
  • On pages with GTM, the banner still sends visitors who have not decided the denied state for Microsoft UET and, if the Meta pixel is on the page, a consent revoke for Meta (these do not receive a default state from us).
  • When you request consent again in the administration, the banner sends an update with the denied state so that the previous choice no longer applies.

2026-10-13 · version 20261013-1428

Changes consent signals (Consent Mode, dataLayer, Meta, Microsoft UET).

  • On an inactive website (unpaid subscription or invalid site key) the script does not show the banner and blocks nothing. It sends no consent signals to Google, Meta or Microsoft for visitors who have not decided. It logs “Site inactive, Cookienovo does nothing” in the browser console. Previously such a website permanently blocked, for example, the Meta pixel.

2026-09-28 · version 20260928-1026

Changes consent signals (Consent Mode, dataLayer, Meta, Microsoft UET).

  • The close icon and the Esc key mean “Deny all”: the refusal is saved and the same Consent Mode update, dataLayer event and Meta and Microsoft signal are sent as with the button. Previously the banner just disappeared and showed up again on the next page.
  • Smaller file thanks to lighter translations.

2026-09-25 · version 20260925-1435

  • The banner file is 45% smaller and displays faster on mobile.
  • The cookie declaration tab has its own introductory text.

2026-09-20 · version 20260920-2022

  • Cookie category descriptions in 25 languages and links to Google’s policies in 23 languages.

2026-09-04 · version 20260904-0534

  • The visitor identifier (cookie cn-bid) has a rolling validity of 365 days. Previously a copy in browser storage kept it forever; now a new one is created after a year without a visit.

2026-08-27 · version 20260827-1214

  • The banner is shown to new visitors also on websites that have no optional cookies. Previously it was hidden there.

2026-08-26 · version 20260826-0428

  • The “Allow all” and “Deny all” buttons have stable attributes data-cn-accept-all and data-cn-deny-all. You can rely on them, for example, in automated tests.

2026-08-24 · version 20260824-1107

  • If a custom logo fails to load, the banner uses the default one.

2026-08-24 · version 20260824-0732

  • The banner also renders in single-page applications (React, Vue, etc.) where the script loads only after the DOMContentLoaded event.

2026-08-18 · version 20260818-1705

  • Security update of the js-cookie library to version 3.0.8.

Older versions are not listed here. Send us questions about changes via the contact form.