Skip to main content

Banner and API

This page lists the banner and API changes that matter to anyone who integrates Avacy into a site. Each entry gives the version, the date and the impact on the site. Dashboard and WordPress plugin updates are in Dashboard and WordPress plugin.

Dates are production deploy dates.

The banner version is in window.Avacy.version.

3.3.1 (17/11/2026)​

  • A custom vendor marked as strictly necessary shows Always active in the preferences panel, instead of the toggle. It always has consent, also with Reject all and when the banner is closed, and it has no legitimate interest.
  • Vendors without the flag do not change.
  • Impact on the site: nothing to change. Scripts of that vendor marked for preemptive blocking run even when the visitor rejects.

3.3.0 (11/11/2026)​

  • showPreferenceCenter() takes a single optional argument, an options object: window.Avacy.showPreferenceCenter({ section: 'vendor' }). The panel always opens as an overlay.
  • The first argument target of earlier versions is gone. A panel mounted inside a page element opened as an overlay anyway, and a selector with no match threw an error.
  • Impact on the site: if you call showPreferenceCenter(undefined, { section: 'vendor' }), switch to showPreferenceCenter({ section: 'vendor' }). With the old form the section is ignored and the panel opens on the first entry. A call with a selector or an element opens the panel as an overlay, without errors. See "Cookie Preferences" link.

3.2.5 (06/11/2026)​

  • The timestamp of getConsent() and of avacy:consent-loaded stays the moment of the choice, even after a page reload. Before, it became the load time. For a consent saved by an earlier version, the banner derives the moment from the consent expiry.
  • Web spaces migrated from the v2 banner: a script with data-iab-vendor="" or data-custom-vendor="" requires nothing and runs after the choice, as in v2. With data-purposes="", data-legints="" or data-special-features="" the script stays blocked and the console reports it with a warning.
  • If the page is still loading, the banner starts at DOMContentLoaded. On Firefox, the WordPress import map with a block theme works again: menus and interactive blocks start. The TCF stub and the Google Consent Mode default stay immediate.
  • Impact on the site: no required change. On web spaces migrated from v2, list the ids in the purpose, legitimate interest and special feature attributes left empty. See Manual marking (v2).

3.2.4 (02/11/2026)​

  • Language outside the configuration: the banner uses English if it is one of the web space languages, otherwise the main language. With 3.2.3 it always used the main language.
  • The rule also applies to changeLanguage(). Before, it showed a non-configured language with the standard Avacy texts, without the customer's texts.
  • Impact on the site: nothing to change. If you change the languages in the dashboard, the banner uses the new list after saving.

3.2.3 (02/11/2026)​

  • Automatic language: when the page language is not active, the banner uses the main language. changeLanguage() normalizes the code and ignores invalid values with a console warning.
  • The banner works with a strict CSP on style-src and script-src with a nonce.
  • If the IAB vendor list cannot be downloaded, the banner reports it. Rejecting closes the banner for the current tab.
  • The avacy_consent event fires on every v3 banner. On web spaces migrated from v2, the banner restores window.AVACY.
  • Impact on the site: no required change. With a nonce-based CSP, put the nonce on the snippet.

3.2.2 (29/10/2026)​

  • The banner waits for the page to be ready before it appears. Before, on some sites, it did not appear.
  • The default text of the preferences button is "Preferences", in all languages.
  • The banner sizes no longer depend on the site's font size. The center banner is 900 px wide.
  • Impact on the site: nothing to change.

3.2.1 (20/10/2026)​

  • The console messages about late Google tags put the Google tag check first and point to the public page on debug mode.
  • Impact on the site: only the console texts change, not the consent.

3.2.0 (19/10/2026)​

  • The banner adds the avacy_consent_update event to the dataLayer after every Google Consent Mode update, rejections included, only if Google Consent Mode is configured. With purpose mapping, it does not add it on the first visit, before the person chooses.
  • Impact on the site: a Google Tag Manager trigger can use avacy_consent_update to fire the tags that wait for consent.

3.1.0 (13/10/2026)​

  • The banner has four loading variants, which the CDN picks based on the web space settings. The variants with Google Consent Mode send the default to the dataLayer before the Google tags, with all types set to denied.
  • The banner warns in the console if a Google command arrives before the Consent Mode default.
  • getConsent() no longer mixes TCF special features with purposes and shows them in a separate view.
  • Impact on the site: the GTM 2.0 template and the snippet load the right variant without changes. Code that read special features from purposes finds them in the separate view.

3.0.0 (13/10/2026)​

  • First release of the v3 banner in production, with the @avacy/cmp-web package. The 3.0.0 number had been in the repository since 29/05/2026, but the first production release is from 13/10/2026.
  • Impact on the site: the v3 banner replaces the v2 banner on migrated web spaces.

API​

  • API v4 accepts form consents sent with an identifier and no consent_data. Before, it rejected them with an error.
  • Impact on the site: no required change. If the form identifies the person only with identifier, you can leave out consent_data. See REST API.
  • The API accepts at most 60 requests per minute from the same IP address for the same web space. Above the limit it responds 429, with the Retry-After header giving the seconds to wait.
  • Impact on the site: an integration that sends many consents from its own server must spread the requests over time and retry after Retry-After. See REST API.
  • The API saves the IP written in ip_address, if it is a valid IPv4 or IPv6 address. Before, it saved the IP the call came from.
  • Impact on the site: consents sent from your server show the person's IP. See REST API.
  • Recording a consent requires a plan that includes the consent archive.
  • Impact on the site: an integration on a plan without the archive gets 403 on every POST request. See REST API.

WordPress plugin and GTM template​


Last updated: 06/11/2026.