Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Web

v33.2.0 - (September 23, 2026)

Features:

  • A Meta/Facebook consent mode integration has been added to the CMP. This feature can be activated from the backoffice.

Fixes:

  • The CMP does not display correctly in the internal navigation on X/Twitter for Android

  • The CMP does not display correctly when the page is in quirks mode

  • The "Settings" button appears as text instead of icon on some mobile devices.

v33.1.0 - (August 12, 2026)

  • A UTIQ integration has been added to the CMP. This feature can be configured from the configuration interface.

  • Added an option to the show method to force the CMP to be displayed on excluded URLs

  • In the mobile web view, the "Refine by partner" link was not centered correctly on Layer 2

v33.0.0 - (July 22, 2026)

  • To limit the amount of data downloaded, the CMP downloads a streamlined version of the notice configuration to the "Layer 1" display.

  • The CMP can now inject scripts for the following events: display, init, and saveDone

  • To optimize the display of text on "Layer 1," the CMP title has been moved by default next to the logo. A second configurable option in the configuration interface allows you to position the title and text to the right of the logo.

  • A new method has been added to retrieve the current consent UUID. __tcfapi('getUuid', 2, (uuid) => { console.log(uuid) })

  • From now on, you can configure the display of consent buttons in vertical orientation from the configuration interface.

  • The CMP version now appears in the "My Privacy ID" menu on the "Settings" page.

  • To better comply with Rule 7 of TCF compliance, we have modified how the "purposes" are displayed. From now on, this list will be displayed automatically without any action required from the user. Two display options are available: table mode and text mode. Both options can be configured via the configuration interface.

  • A glitch appeared on the consent toggles on the "Settings" page when viewing the site on a mobile device

  • On the consent buttons, the border color was not consistent with the button color when a user interaction occurred.

v32.13.1 - (May 28, 2026)

  • Bugfix : The CMP was no longer displayed in outdated / deprecated implementations.

v32.13.0 - (May 27, 2026)

  • Device Storage Disclosures updates under the Transparency and Consent Framework (TCF).

v32.12.1 - (April 20, 2026)

  • The first-party cookie feature could cause the CMP to crash if a cookie set by the host website used a non-compliant encoding.

v32.12.0 - (April 2, 2026)

  • A new feature Excluded URLs from display has been added to the configuration interface that allows you to specify URLs on which the CMP will not be displayed. This is useful for pages such as privacy pages.

  • A new feature called 1st party user UUID has been added to the configuration interface, which allows you to store the user UUID in a cookie and identify a user across subdomains

  • You can now configure the color of the CMP overlay from the configuration interface

  • Improved accessibility on Layer 1 of the CMP Clear

  • Fixed: When the cookie deletion on withdrawal of consent feature was enabled, first-party cookies associated with a domain were not deleted properly.

v32.11.0 - (January 22, 2026)

  • TCF 2.3 amendments specifications have been added.

    • The new segment for disclosed vendors has been added.

  • A new event named “new_consent_raised” has been added to the "dataLayer" variable to indicate whether a user has given or changed their consent.

  • Bugfix: LiTE execution (script injection) was no longer performed after a second /hello

v32.10.0 - (December 3, 2025)

  • To comply with Transparency & Consent Framework policies, requiring that consent be changed to a single click, two buttons (“Refuse all and close” and “Accept all and close”) have been added to the settings page.

  • On clear version, the illustration images can be customized from the configuration interface.

  • The CMP can now display custom images (logo and illustrations) in webp format

  • Fix: The Close button on the settings page did not reset the user's selection when the cmp was displayed for a consent change.

  • Fix: Under certain conditions, the xchange script could not be injected into the website page.

v32.9.1 - (August 4, 2025)

  • Fix : the "language" property used to force the detection of the current language was no longer being applied.

v32.9.0 - (July 3, 2025)

  • A system for deleting 1st Party cookies ( exluding http only ) has been added when consent is withdrawn. This feature is deactivated by default, but can be activated on a source form in the configuration interface.

  • A new "appconsent_choice_available" event is now injected in the dataLayer when a choice is available.

  • The consent retention period label has been modified in layer 2 to make it easier for users to understand.

  • fix bug: privacy widget could be displayed incorrectly with the Tailwind CSS library

v32.8.1 - (May 26, 2025)

  • Fix : The cmp was not displayed on sites with http://, because the cmp used the subtle function of the crypto web api, which only works in a secure context (e.g. https).

v32.8.0 - (May 12, 2025)​

  • Update iab framework to version 1.5.16 [ Mandatory for all CMPs vendor]

  • Cmp build size reduced to improve loading performance

  • A search bar has been added to the list of vendors

  • New customization properties have been added. It is now possible to customize :

    • hover color on consent buttons.

    • Layer 2 icon color (only available on CMP Clear).

  • The error message indicating that Google Tag Manager (GTM) is initialized before Appconsent CMP is now transformed into a warning message.

  • Fix: The size of the logo has been fixed to no longer impact performance when displaying the CMP.

  • Fix: On the Classic version of CMP, the bottom banner mode was not displayed correctly. The consent buttons on Layer 1 no longer take up the full width of the screen.

v32.7.1 - (February 27, 2025)​

  • Fix : Sometimes clicking on privacy widget failed to show the CMP on layer1

  • Fix : Deployment of version 32.7.0 failed due to a CDN cache expiration issue ( GCP )

v32.7.0 - (February 25, 2025) - Rollbacked​

  • 38 new languages have been added. These languages can be selected from the configuration interface

v32.6.0 - (February 5, 2025)​

  • From now on, the fonts used in the CMP are hosted by SFBX.

  • Apple Distraction Control detection is now performed on the same session.

  • Error handling on addEventListener implementations has been improved

  • Removal of the aria role attribute from the CMP iframe to improve accessibility score ( Core Web Vitals )

  • The deprecated targetCountries property is now removed from CMP

  • It is now possible to customize the color of links on the CMP from the configuration interface.

  • Fix : A visual bug appears on the list of vendors with a low number of vendors.

v32.5.2 - (December 18, 2024)​

  • TCF compliance: The text on the use of data storage has been improved on the vendor page.

  • TCF compliance: An explanation of the presence of legitimate interests has been added to layer 1.

v32.5.1 - (December 11, 2024)​

  • TCF compliance has been improved on the vendors page and the privacy widget.

  • Fix : The scrollbar is now unlocked after the consent

  • Fix : AppConsent CMP is once again compatible with older implementations

v32.5.0 - (November 14, 2024) - Rollbacked​

  • Link colours can now be customised from the configuration interface

  • CMP blocking with Apple Distraction Control is now detected. We have provided a new callback named adcDetected to allow you to react to a block.

  • The targetCountries property has been removed from the configSFBXAppConsent configuration. From now on, to target one or more countries, please configure the ‘GDPR extra countries’ property available in the notice configuration form.

v32.4.0 - (August 22, 2024)

  • TCF 2.2 amendments specifications have been added [TCF v2.2 Policies amendments: introduction of new Special Purpose 3 - "Save and communicate privacy choices" ]

    • The consent string retention period is now displayed in layer 2

    • The special purpose 3 has been added

    • Upgrade from TCF policies to version 5 (already implemented through gvl 2024-07-18 )

  • Fix UI: A scroll bar appeared in the success screen on the Clear version

v32.3.0 - (June 18, 2024)

  • The forceGDPRApplies, urlRedirect, targetCountries and privacyWidget properties can be configured from the configuration interface.

  • LiTE can now be configured and injected after the user's choice under consent, no-consent ( including datawall mode).

  • Fix bug : On consent reacquisition, url redirection did not work

v32.2.0 - (May 21, 2024)

  • Google Basic Consent Mode has been added.

  • It is now possible to activate TCF compatibility mode with Google Consent Mode (GCM)

  • An error log is now displayed in the browser console when the CMP is initialised after a Google Tag Manager tag.

v32.1.0 - (April 18, 2024)

  • Adding Catalan ( CA ) , Suedish ( SA ) and Danish ( DA)

  • ATPv2 : New version of additional consent released

  • Update GCMv2 : Now full status is sent on update consent

  • Fixed css class added to facilitate CMP customization

  • Fix bug : The list of purposes in layer 1 did not take on the custom color in CMP classic.

  • Fix bug : The title of the list of purposes was missing from the Portuguese translation.

v32.0.1 - (March 01, 2024)

  • Fix bug : In some cases, the AdSense flag (window.adsbygoogle.pauseAdRequests) was not refreshed.

v32.0.0 - (February 28, 2024)

  • New implementation of web cmp has been added. Implementation with loader now deprecated, but still functional and maintened ( No breaking Change ).

  • The enableGCM property can now be activated from the notice editing form in the configuration interface.

  • A property has been added to the notice editing form to disable GCM in selected countries.

  • An event named acextravendor_denied_ID is now added to GCM when an extra vendor is not granted.

v31.1.3 - (February 05, 2024)

  • New consent types for Google Consent Mode (GCM) v2 have been added :

    • ad_user_data

    • ad_personalization

v31.1.2 - (January 24, 2024)

  • Improve performance : CMP makes fewer calls to the backend when GDPR is not applied

  • Fix bug : Classic Template Only - Layer 1 hide the bottom buttons on small screens when « Display purposes on layer 1 » is activated.

  • Fix bug : In some cases, the count of the number of vendors in layer 2, at the stack level, was not correct.

  • Fix bug : Uncaught (in promise) error no longer appears in console in non-GPDR zone

v31.1.1 - (January 08, 2024)

  • Fix bug: Listener was undefined when gdprApplies was set to false

  • Fix bug: window.adsbygoogle.pauseAdRequests was not set correctly when gdprApplies was set to false

Old release-notes

v31.1.0 - (December 21, 2023)

  • The height of the CMP adjusts automatically based on the content.

  • TCF2.2: UI & Texts Enhancements

  • Now the gdprApplies is based on ip address of the user

v31.0.1 - (December 14, 2023)

  • New data format to improve notice configuration size

v31.0.0 - (November 14, 2023)

  • TCF 2.2 specifications have been added

v30.4.1 - (October 30, 2023)

  • Following the recent development regarding logo resizing and behavior, the UI of the CMP could sometimes be degraded.

v30.4.0 - (October 19, 2023)

  • The new Accept/Configure/Deny and Deny/Configure/Accept button configurations on the first display have been added.

  • The switch icons on the settings page have been inverted to avoid misunderstandings.

  • Logo display has been resized to improve image rendering

  • GCM properties are no longer denied when the notice is displayed in a country outside the RGPD zone.

  • Fix bug : Oppose legitimate interests button did not register correct consent status in consentstring

  • Fix bug : A user's consent is not properly reflected in the interface between two websites with the same appkey.

v30.3.1 - (April 27, 2023)

  • In Bottom banner mode, a javascript crash appeared when the web CMP was used with the old implementation

  • The command saveFloatingPurposes did not correctly save the values of the floating purposes in the localstorage

v30.3.0 - (April 25, 2023)

  • The IAB saveFloatingPurposes command is not persisted after a page refresh

  • A vertical display mode for the buttons on the bottom banner has been added

v30.2.0 - (March 29, 2023)

  • Added horizontal banner display mode for the clear version

  • The css class "button_skip" was missing on the "Continue without accepting" button in clear version

  • The action buttons in the "Classic" notice have been aligned to the right of the display to have the same display type as the Clear notice

v30.1.0 - (February 14, 2023)

  • Adding a preview mode which does not record the user's consent and which will be used for previews of notices on https://app.appconsent.io/.

v30.0.0 - (November 24, 2022)

  • The lazy option is activated by default

  • GCM mode is now disabled by default

  • Changing cmp cache duration

  • Improving of compatibility with the old implementation

  • Bug fixes for the new implementation

v29.0.0 - (September 08, 2022)

  • The implementation has been simplified.

    • Only the loader script and the new configuration variable of the cmp need to be implemented.

  • Compatibility with the old implementation has been maintained.

v28.11.1 - (July 06, 2022)

  • Add an option to open Privacycenter from the text

  • Add configurable URL redirection when clicking on buttons

  • Multiple bugfixes

  • Improve performance

v28.10.4 - (June 13, 2022)

  • Release clear template

  • Update IAB TCF framework to v1.4.0

  • Use day-accurate creation and update date for TCString

  • Possibility to add regexp to hide CMP on matching URLs

v28.7.16 - (May 30, 2022)

  • No more usage of eval function in dependencies

v28.7.15 - (February 11, 2022)

  • Added a cache on backend call results to improve global usage performance

v28.7.12 - (December 21, 2021)

  • Add a method to manipulate consents without displaying the CMP

  • Replace "continue without accepting" by a closing cross when CMP is displayed on a device using Italian language

v28.6.0 - (November 17, 2021)

  • Add Client-Origin header to all HTTP requests

  • Reset store if consent is expired

  • Different type for REFUSE_ALL and CONTINUE_WITHOUT_ACCEPTING actions

  • Calculate consent type on HELLO action

v28.5.2 - (October 18, 2021)

  • Display the link to the list of features

v28.5.1 - (September 14, 2021)

  • Set correct CMP id and version

v28.5.0 - (August 18, 2021)

  • New CMP methods are added: checkForUpdate, presentNotice, setExternalIds, saveExternalIds, getExternalIds,extraFloatingAllowed, isFloatingNeedUpdate, saveFloatingPurposes

  • removeEventListener callback should be called with boolean instead of null

  • ship2 request sends page url

  • Static class name for modal banner

v28.4.0 - (June 10, 2021)

  • gdprApplies init param

v28.3.0 - (May 27, 2021)

  • Grant legitimate interest on fakedeny

  • Language param

  • Upgrade @iabtcf packages

  • AMP banner/modal display bugfix

  • Gray SFBX logo

v28.2.0 - (May 04, 2021)

  • List of bugs and features deployed :

  • Created date and lastUpdated date in the consent string

  • Custom CSS for AMP

  • Modal mode for an AMP

  • SFBX Copyright

  • Colors & images customisation

v28.1.0 - (April 21, 2021)

  • Created date and lastUpdated date in the consent string

  • New privacy widget logo

  • Encode language in the consent string

  • Remove circular dependencies

  • Enable Legitimate Interest on REFUSE_ALL / SKIP

  • Skip link added for banner mode gdprApplies

  • List of internal improvements :

  • IN-90 New versionning system

v28 - (March 23, 2021)

  • Disable legitimate interest on DENY ALL

PreviousRelease Notes
NextiOS

Last updated