View new changes and fixes for Privacy Controls and Cookie Solution delivery channels. More about current, beta and stable channels, how to change them and how to choose a specific version on this guide.
1.70.0
BETA November 26, 2024
- We’ve ensured the privacy widget stays in the correct position by introducing a setting that stores user preferences, even when remote configuration is enabled
- We’ve increased the focus color contrast in dark mode for better visibility and accessibility
- We’ve updated the mobile SDK to ensure the banner closes immediately after consent, preventing any delay or overlapping popups
- We’ve added the
tcfVendors
field to the default configuration, eliminating the “tcfVendors
not recognized” warning. The field is now properly included in the settings.
- Bug fixes and minor improvements
1.68.0
BETA October 15, 2024
CURRENT October 22, 2024
STABLE November 21, 2024
- We’ve added a configuration option
invalidateConsentBefore
(“YYYY-MM-DD”, milliseconds from epoch, default null) to invalidate consents collected before a specific date. You can also provide a date range using invalidateConsentInterval
with startDate
and endDate
to target consents within that period
- We’ve enhanced the AMP system for greater reliability and performance
- We’ve implemented support for Microsoft’s update to consent signal enforcement for end users
- Bug fixes and minor improvements
1.66.1
BETA September 10, 2024
CURRENT September 17, 2024
STABLE October 23, 2024
- We’ve added the option to embed the Newsletter Opt-in Booster widget directly on the page with inline positioning. Now, you can place the widget within a specific section of your page. Additionally, it’s now possible to customize the banner with custom colors, including the main background, text color, button background, and button text color, offering more control over the widget’s appearance
- We’ve improved language configuration and automatic detection. The system can automatically detect the user’s language and adjust settings accordingly, applying only to the languages that have been enabled by the user
- We’ve added more callbacks for the Mobile SDK, similar to those available on the web version. The new callbacks include:
onStartupFailed
, onError
, onFatalError
, onBannerShown
, on2ndLayerShown
, and onPreferenceFirstExpressed
- We’ve added Finnish, Hungarian, Latvian, Lithuanian, Slovenian, Estonian, Croatian, and Slovak as available languages for the Privacy Controls and Cookie Solution
- Bug fixes and minor improvements
1.65.1
BETA August 01, 2024
CURRENT August 13, 2024
STABLE September 06, 2024
- We’ve added Finnish, Hungarian, Latvian, Lithuanian, Slovenian, Estonian, Croatian, and Slovak to the supported languages
- We’ve added a verbose logging mode to help verify Google Consent Mode (CoMo) implementation
- Bug fixes and minor improvements
1.64.0
BETA July 18, 2024
CURRENT July 30, 2024
STABLE August 26, 2024
- We’ve added support to
localstorage
in safe-tcf-v2, this means now the Safe TCF script is compatible with both localStorage
and cookies
- We’ve ensured that TCF and Google advertising partners toggles act independently in the second layer, even when additional consent mode is enabled
- Added Norwegian to the supported languages
- Bug fixes and minor improvements
1.63.0
BETA July 12, 2024
CURRENT July 22, 2024
STABLE August 20, 2024
- We’ve optimized the loading of the Google Additional Consent Mode vendors list, ensuring the vendors are fully loaded when opening the widget
- We’ve added the ability to apply custom styles to the Newsletter Opt-in Booster widget, enhancing UI customization options
- We’ve improved some markup on the templates that could impact SEO
- Bug fixes and minor improvements
1.62.0
BETA June 19, 2024
CURRENT June 26, 2024
STABLE July 24, 2024
- To meet Google’s requirements, we’ve ensured that the developer ID for iubenda is set as early as possible
- We’ve added a configuration to support integration with Google’s
TCData.enableAdvertiserConsentMode
flag, allowing Google to infer consent settings for ad storage and personalization from the TC string
- We’ve changed the domain for analytics requests from
hits-i.iubenda.com
to idb.iubenda.com
, improving the reliability and performance of analytics data collection
- We’ve implemented a check for
localStorage
availability. If localStorage
is not available, the Newsletter Opt-in Booster widget will not load or will be disabled to prevent potential issues
- We’ve added
_iub.csConfiguration.storage.autoSync
to enable automatic synchronization of stored preferences between cookies and local storage. When set to true, preferences are switched seamlessly between cookie and local storage
- Bug fixes and minor improvements
1.61.0
BETA May 16, 2024
CURRENT May 23, 2024
STABLE June 20, 2024
- We’ve added
googleUrlPassthrough
and googleAdsDataRedaction
to allow customization for Google Consent Mode
- We’ve added
_iub.csConfiguration.emailMarketing.showFromPageView
to make the Newsletter Opt-in Booster widget display timing configurable based on the number of page views
- We’ve improved support for Google Additional Consent (GAC) v2 in mobile
- Bug fixes and minor improvements
1.60.0
BETA April 19, 2024
CURRENT April 26, 2024
STABLE May 23, 2024
- We’ve added the
_iub.csLangConfiguration
object, useful to specify all language-specific configuration options, such as cookiePolicyId
, allowing the system to automatically determine which options to use based on the language settings
- We enhanced the INP Core Web Vitals score for preferences in the second layer
- We’ve added the
setPreferences
API method to granularly store user preferences, including the option to hide the banner
- Bug fixes and minor improvements
1.59.0
BETA April 10, 2024
CURRENT April 16, 2024
STABLE May 14, 2024
- We’ve added
showTotalNumberOfProviders
and totalNumberOfProviders
parameters to manage and display the number of third parties involved in data processing
- Added Bulgarian, Romanian, and Catalan to the supported languages
- Bug fixes and minor improvements
1.58.0
BETA April 02, 2024
CURRENT April 09, 2024
STABLE May 08, 2024
- We enhanced the user experience and increased performance scores on tools like Google PageSpeed and GTMetrix
- We enhanced the INP Core Web Vitals score on ‘X’ button click
- Czech has been added to the list of supported languages
- We updated
IubendaCookieSolution.getPreferences()
to include the gppString
attribute when the Global Privacy Platform (GPP) is active
- Bug fixes and minor improvements
1.57.0
BETA March 04, 2024
CURRENT March 11, 2024
STABLE April 08, 2024
- With the enforcement of TCF 2.2, when TCF is enabled, only the latest 2.2 version will be available
- Currently, we support only precise geolocation
(sd8)
as the sensitive data category. This means all other purposes currently handled, specifically sd5
and sd9
, will be deprecated
- Bug fixes and minor improvements
1.56.0
BETA February 08, 2024
CURRENT February 26, 2024
STABLE March 13, 2024
- The SDK now supports a new action,
open_pref
, in mobile.htm, allowing for the opening of the preferences panel with pre-selected purposes
- We’ve added
_iub.cs.api.openAdvertisingPreferences()
to display the TCF panel with purposes highlighted and vendors collapsed, enhancing user consent interaction. Note that if enableTcf
is set to false
, the method defaults to opening the Cookie Policy panel
- Bug fixes and minor improvements
1.55.0
BETA January 22, 2024
CURRENT January 29, 2024
STABLE February 25, 2024
- We’ve implemented the new Google Additional Consent (GAC) v2
- We’ve added a new configuration parameter:
banner.howToWithdraw
, when false
, the text “by accessing the preferences panel” is omitted from the banner in all languages. If true
, the text is displayed
- When
banner.totalNumberOfProviders
is present and > 0, it is possible to display the total number of providers at the beginning of the banner text, “We and “number of providers” selected third parties.”
- Bug fixes and minor improvements
1.54.0
BETA January 04, 2024
CURRENT January 11, 2024
STABLE February 08, 2024
- We’ve updated TCF vendor counting on the second layer to differentiate the vendors number based on the legal basis they are relying on
- Bug fixes and minor improvements
1.53.2
BETA November 27, 2023
CURRENT December 12, 2023
STABLE January 09, 2024
- We’ve implemented the new Google Consent Mode v2 specification, including mapping for GDPR purposes and US law purposes. Now our Google Consent Mode plugin manages these new settings
- We’ve added a new option to store cookies using
siteId
- We enhanced the INP Core Web Vitals score
- We’ve added support for Google’s Additional Consent Mode on Accelerated Mobile Pages (AMP)
- We’ve added the
banner.ownerName
parameter to enable the substitution of “We” at the beginning of the sentence “We and selected third parties use cookies….” in the banner text with another string, typically the company name.
- Bug fixes and minor improvements
1.52.2
BETA October 23, 2023
CURRENT October 30, 2023
STABLE November 27, 2023
- We’ve added a new parameter called
banner.showTitle
to provide users the ability to select if they want to show or hide the title in the Privacy Controls and Cookie Solution Configurator
- We’ve added support for Google’s Additional Consent Mode for mobile
- We’ve added support for US law purposes in Google Consent Mode, ensuring that US user preferences are also considered.
- Bug fixes and minor improvements
1.51.0
BETA September 18, 2023
CURRENT October 12, 2023
STABLE October 23, 2023
- The
_iub.cs.api.openPreferences()
function with acceptPurposes
option is now restricted to our Ultimate plan
- For users not subscribed to the Ultimate plan, the use of the
_iub.cs.api.acceptAll()
function is now restricted. This feature is available exclusively for our Ultimate plan users
- Starting September 30th, GPP 1.1 will become the new standard version. This new version isn’t compatible with GPP 1.0, To make the transition smoother, we’ve added a
gppVersion
setting option that lets you choose between versions
- We’ve updated the
onPreferenceFirstExpressedCallback
function to better handle per-purpose consent settings. If you’re using per-purpose consent, the function now merges general and US-specific consent purposes
- Bug fixes and minor improvements
1.50.1
BETA August 07, 2023
CURRENT August 16, 2023
STABLE August 16, 2023
- We’re getting ready to support version 2.2 of IAB’s TCF
- We now support the ability to add content in place of pre-blocked scripts other than iframes (e.g. for scripts or generic content as well)
- Bug fixes and minor improvements
1.49.3
BETA June 28, 2023
CURRENT July 3, 2023
STABLE August 03, 2023
- We’ve added a new option called
usPreferencesWidgetDisplay
to handle the US widget positioning
- We’ve added a new API method called
rejectAll()
to reject everything when it’s invoked
- We’ve added new settings to help you comply with the Swiss Federal Act on Data Protection (nFADP)
- It is now possible to store the TCF preferences on
localStorage
instead of cookies, so to avoid having it transmitted to the server on every HTTP request
- We’ve added a new option called
emitGtmEvents
to allow GTM tags to be triggered just after the user gives consent
- Bug fixes and minor improvements
1.48.0
BETA May 24, 2023
CURRENT May 29, 2023
STABLE June 22, 2023
- Bug fixes and minor improvements
1.47.1
BETA May 22, 2023
CURRENT May 22, 2023
STABLE June 07, 2023
- We have added a new TCF option called
acceptTcfSpecialFeaturesWithAcceptBtn
. If you set it to false, you can prevent the activation of TCF Special Features when users click the Accept button
- The new
localConsentDomainExact
option lets you restrict cookie preferences to a specific domain, excluding its subdomains
- Bug fixes and minor improvements
1.46.3
BETA March 30, 2023
CURRENT March 30, 2023
STABLE April 19, 2023
- Now, when you exceed your plan’s page view/month limit, the cookie banner is replaced by an alert this means that you won’t be able to get visitors’ consent and release cookies. More about this here
- As of March 1, it’s no longer possible to deactivate prior blocking via code or dashboard. This means that the “Prior blocking and asynchronous re-activation” (server side) and “Prior consent” (
priorConsent
parameter) options are always active for all channels
- Bug fixes and minor improvements
1.45.1
BETA February 15, 2023
CURRENT February 15, 2023
STABLE March 15, 2023
- Now you can show granular controls in the first layer of the cookie banner by setting the new
showPurposesToggles
banner option to true
. This way, your visitors can quickly choose which categories of cookies to give consent to
- We now support more HTML elements for manual tagging. Here’s the full list:
iframe
, video
, audio
, script
, embed
, img
, object
, link
, picture
, source
- Bug fixes and minor improvements
1.44.8
BETA January 3, 2023
CURRENT January 3, 2023
STABLE January 19, 2023
- We’ve added new settings to help you comply with the latest US privacy laws (CCPA/CPRA for California and VCDPA for Virginia)
- We’ve added new themes to the cookie banner
- Bug fixes and minor improvements
1.43.0
BETA November 23, 2022
STABLE December 21, 2022
- The second layer of the cookie banner now always shows cookie category descriptions when LGPD applies
- We’ve added a new option called
preferenceCookie.tcfV2Name
to allow renaming the TCF cookie
- Bug fixes and minor improvements
1.42.4
BETA October 10, 2022
CURRENT October 20, 2022
STABLE November 2, 2022
consentOnContinuedBrowsing
will be forced to false
on November 21
- When
consentOnContinuedBrowsing
is false
and the close button is missing, acceptButtonDisplay
is forced to “true”
- The
openPreferences()
API method now supports an optional { acceptPurposes: [...] }
parameter to open the second layer with preselected purposes
- We’ve added a new API method called
acceptAll()
to accept everything when it’s invoked
- For clarity, the “Save and Go Back” button in the second layer now looks and behaves like a “Back” button (no preference is saved)
- Bug fixes and minor improvements
1.41.0
BETA August 17, 2022
CURRENT August 24, 2022
STABLE September 21, 2022
- It is possible to show a “Continue without accepting” button by setting
continueWithoutAcceptingButtonDisplay
to true
- To give the privacy widget a custom z-index, we’ve added the
floatingPreferencesButtonZIndex
option
- Mobile users are now allowed to reject cookies only when the first layer of the cookie banner has been fully scrolled
- We’ve added the callbacks
on2ndLayerShown
and on2ndLayerClosed
which are triggered when the second layer opens or closes
- Bug fixes and minor improvements
1.40.1
BETA July 25, 2022
CURRENT July 25, 2022
STABLE August 09, 2022
- We now provide a Google Tag Manager custom template that simplifies the implementation of the default command, making it codeless and allowing the update command to take effect as early as possible in the tag firing process
- We set the TCF cookie expiration to 12 months by default
- We updated the behavior of the
banner.explicitWithdrawal
condition for the LGPD support
- Bug fixes and minor improvements
1.39.1
BETA June 7, 2022
CURRENT June 13, 2022
STABLE July 11, 2022
- We’re getting ready to support the LGPD
- TCF preferences are now disabled when GDPR does not apply
- We’ve updated the cookie banner text
- We’ve modified the hover effect on the banner buttons for better accessibility
- Bug fixes and minor improvements
1.38.0
BETA April 27, 2022
CURRENT May 9, 2022
STABLE June 6, 2022
- We have updated the Brazilian Portuguese cookie banner text
- We’ve made improvements for better supporting the compliance settings for the CCPA
- Bug fixes and improvements (including better support for Google Consent Mode and i18n)
1.37.2
BETA March 17, 2022
CURRENT March 24, 2022
STABLE April 11, 2022
- We have improved some accessibility features for full compliance with WCAG guidelines.
- We have improved support for Google Consent Mode, avoiding compromising statistics in cases where anonymous statistical data can be collected regardless of user preferences
- Bug fixes and other minor improvements
1.36.2
BETA February 17, 2022
CURRENT February 17, 2022
STABLE February 28, 2022
- Granular consent within AMP pages is now supported using
perPurposeConsent: true
- Bug fixes and other minor improvements
1.35.4
STABLE February 17, 2022
- Bug fixes and other minor improvements
1.35.3
BETA December 21, 2021
CURRENT December 21, 2021
STABLE December 21, 2021
- Using
banner.closeButtonRejects: true
, the close button of the banner (the “X”) has the value of denial of consent to cookies.
- To comply with the last Italian DPA’s guidelines, “Reject all” and “Accept all” buttons need to have now the same color.
- Notice to users about their right to withdraw consent can be shown directly within the banner.
- To prevent the Privacy Controls and Cookie Solution from failing to save the consent due to a user action on the page (e.g. refresh or abandon), the operation is retried the next time the page is accessed, until the proof of consent is correctly stored.
- Consents not recorded through the Cookie Preference Log can be invalidated using the
invalidateConsentWithoutLog
option.
- Bug fixes and other minor improvements
1.34.0
BETA October 25, 2021
CURRENT November 8, 2021
STABLE December 6, 2021
- Users are now allowed to accept/reject cookies only when the first layer of the cookie banner has been fully scrolled.
- TCF consents created more than 12 months before are automatically invalidated since they could prevent Google Ads to serve ads to users that have old TCF consents
- To comply with the new Italian DPA’s guidelines, the first layer of the cookie banner mentions the use of “technical” as well as “non-technical” cookies
- Bug fixes and other minor improvements
1.33.1
BETA October 13, 2021
CURRENT October 13, 2021
STABLE October 13, 2021
- Thanks to the newly introduced support for custom attributes
suppressedtype
and data-iub-type
, our Privacy Controls and Cookie Solution can now also activate scripts other than text/javascript (e.g. module).
- We’ve introduced the Cookie Preference Log
- Bug fixes and other improvements
1.32.0
BETA August 3, 2021
CURRENT August 10, 2021
STABLE September 13, 2021
- We’ve deprecated
enableCMP
in favor of enableTcf
- We’ve added the
googleConsentMode
option
- Bug fixes and other improvements
1.31.1
BETA June 21, 2021
CURRENT June 28, 2021
STABLE August 2, 2021
- We’ve introduced the
banner.listPurposes
option (false
by default) to display purposes in the first layer of the cookie banner
- Bug fixes and other improvements
1.30.3
BETA May 17, 2021
CURRENT May 17, 2021
STABLE May 26, 2021
- We’ve simplified the implementation of Google Consent Mode (you no longer have to add a callback to your Privacy Controls and Cookie Solution snippet)
- Thanks to the
openPreferences()
method, users can update their cookie preferences even after closing the cookie banner
- We’ve introduced the
iubenda-vendor-list-link
class to allow users to reopen the TCF vendor list
- Bug fixes and other improvements
1.29.0
BETA March 23, 2021
CURRENT March 30, 2021
STABLE May 10, 2021
- We’ve further reduced the size of the JavaScript files, making the Privacy Controls and Cookie Solution 45% lighter
- The cookie banner is now WCAG compliant
- Bug fixes and other improvements
1.28.1
BETA March 5, 2021
CURRENT March 5, 2021
STABLE April 1, 2021
- We’ve completely overhauled our AMP integration, including:
- Perfected Safari support. After adding the consent refreshing feature, our support for Apple’s browser is even better.
- The tracking preferences widget. This widget – now also fully supported in AMP – allows users to re-open and edit their tracking preferences after closing the cookie banner.
- Bug fixes and other improvements
1.27.1
BETA February 16, 2021
CURRENT February 16, 2021
STABLE March 16, 2021
- Following IAB updated policies, we now disclose maximum cookie storage duration when the TCF is enabled
- Bug fixes and other improvements
1.26.0
BETA December 9, 2020
CURRENT December 16, 2020
STABLE January 18, 2021
- New
iub-prevent-consent
class. By adding it to certain links/buttons, you’ll avoid automatically giving consent when pressed
- We’ve updated the legal text of purpose 5
- Bug fixes and other improvements
1.25.0
BETA November 9, 2020
CURRENT November 16, 2020
STABLE December 16, 2020
- We’ve updated the legal text of purpose 3 in FR, DE, NL and RU
- Bug fixes and other improvements
1.24.3
BETA September 18, 2020
CURRENT September 18, 2020
STABLE September 29, 2020
- In order to comply with IAB requirements:
- now you cannot edit the cookie banner text when the TCF v2 is enabled
- we’ve introduced an automatic floating button to re-open advertising preferences
_iub.cs.api.storeConsent
can now handle TCF string to fully support Safari on AMP
- Bug fixes and other minor improvements
1.23.2
BETA September 7, 2020
CURRENT September 8, 2020
STABLE September 8, 2020
- The TCF Reject button now also applies to legitimate interest (which is now disabled by default)
- Bug fixes and other minor improvements
1.22.8
BETA August 21, 2020
CURRENT August 21, 2020
STABLE August 21, 2020
- We’ve added support for Google’s Additional Consent Mode
- We’ve shortened the TCF v2 banner text
- We now save TCF strings longer than 4096 chars in multiple cookies
- We’ve added a fix for an IAB library bug which resulted in the consent string non being passed correctly to vendors
- Bug fixes
1.21.0
BETA June 8, 2020
CURRENT June 15, 2020
STABLE July 13, 2020
- We’ve made the default cookie banner text much shorter in an effort to simplify communication with end-users
- In anticipation of IAB’s hard cutoff date, we’ve scheduled a force-switch to TCF v2.0
- Bug fixes and other minor improvements
1.20.6
BETA May 6, 2020
CURRENT May 6, 2020
STABLE May 26, 2020
- Now we also support version 2.0 of IAB’s TCF
- We’ve further improved the style of the cookie banner and added custom branding options
- We’ve updated cmp.js to version 1.5.0
- As with the cookie policy, now the privacy policy can also be opened in another window when
cookiePolicyInOtherWindow
is true
- New
onBannerClosed
callback
- Bug fixes and other minor improvements
1.19.0
BETA March 4, 2020
CURRENT March 24, 2020
STABLE April 28, 2020
- Bug fixes and other minor improvements
1.18.0
BETA February 26, 2020
CURRENT February 28, 2020
STABLE March 31, 2020
- Google Ads preferences are now also stored remotely when
isTCFConsentGlobal
option is true
- We’ve implemented the
ccpaAcknowledgeOnDisplay
option to acknowledge when the CCPA notice is shown
- New
onCcpaAcknowledged
, onCcpaFirstAcknowledged
, onCcpaOptOut
and onCcpaFirstOptOut
callbacks
- New
_iub.cs.api.ccpaApplies()
and _iub.cs.api.gdprApplies()
API methods
_iub.cs.api.storeConsent()
can now handle purposes
1.17.2
BETA February 21, 2020
CURRENT February 24, 2020
- We’ve changed the default
timeoutLoadConfiguration
to 30000 ms
- We’ve renamed the “Analytics” category into “Measurement”
- We’ve updated the TCF banner text
- Bug fixes and other minor improvements
1.16.7
BETA January 29, 2020
CURRENT January 29, 2020
STABLE February 10, 2020
- We’ve introduced the
iubenda-cs-preferences-link
class to allow users to update their cookies preferences even after closing the cookie banner
- New
onConsentFirstRejected
and onPreferenceFirstExpressed
callbacks
- We’ve updated cmp.js to version 1.4.3
- We now correctly set the
SameSite
attribute on remote cookies to comply with the stable version of Google Chrome 80
- Bug fixes and other minor improvements
1.15.6
BETA December 19, 2019
CURRENT December 19, 2019
STABLE January 29, 2020
1.14.6
BETA December 5, 2019
CURRENT December 5, 2019
STABLE January 3, 2020
- We’ve added the per-category consent feature. This way you can give users granular controls on which categories of data processing purposes to give consent to
- Bug fixes
1.13.1
BETA November 6, 2019
CURRENT November 15, 2019
STABLE December 16, 2019
- We’ve added the country detection feature to avoid showing the cookie banner when outside the EU. Set
gdprAppliesGlobally:false
and countryDetection:true
to request consent to EU users only
- Bug fixes
1.12.3
BETA October 31, 2019
CURRENT October 31, 2019
STABLE November 20, 2019
- Banner text and CSS updates
- Bug fixes
1.11.1
BETA October 11, 2019
CURRENT October 21, 2019
- We’ve added the “Reject” button
- The close button is now hidden when the “Reject” button is displayed
- We’ve updated the banner text to be compliant with TCF guidelines
- Pressing the “x” in the second modal layer – the one with the cookie policy – takes the user back to the cookie notice instead of providing consent
- API methods can now be called from an iframe
- Bug fixes
1.10.3
BETA September 16, 2019
CURRENT October 2, 2019
STABLE November 18, 2019
- You can now hide the close button (“x”) setting the
closeButtonDisplay
banner parameter to false
- Bug fixes
1.9.2
BETA September 5, 2019
CURRENT September 13, 2019
STABLE October 14, 2019
- We’ve added the “Click on the Accept button” metric to the Privacy Controls and Cookie Solution Analytics (“Consent drilldown” section)
- The cookie banner text is now shorter when the “Learn more and customize” button is enabled
consentOnElement
and consentOnScrollOnElement
options now also take CSS selectors
- Bug fixes
1.8.2
BETA August 27, 2019
CURRENT September 3, 2019
- Now the notice always displays fullscreen on native mobile
- We’ve adjusted the wording of the TCF related sections to be in line with the requirements on mobile phones/applications
- We’ve renamed the
consentOnButton
option to consentOnLinkAndButton
to make it clear that it also applies to <a>
elements
- Bug fixes
1.7.1
BETA June 5, 2019
CURRENT June 10, 2019
- New positioning options for the cookie banner
- Ability to trigger a new consent request when the vendor list is updated
- Bug fixes
1.6.1
BETA June 3, 2019
CURRENT June 3, 2019
STABLE July 9, 2019
- We’ve added “Accept” and “Customize” buttons to the cookie banner
- Bug fixes and performance improvements
1.5.4
BETA April 16, 2019
CURRENT May 6, 2019
STABLE June 6, 2019
- We’ve added the
iubenda-advertising-preferences-link
CSS class to let visitors update their advertising tracking preferences even after closing the cookie banner
- Bug fixes
1.4.0
BETA April 5, 2019
CURRENT May 6, 2019
STABLE June 6, 2019
- Ability to collect explicit consent for Google personalized ads
googleAdsPreferenceManagement
option added
isTCFConsentGlobal
option added
- Bug fixes
1.3.14.3
BETA March 11, 2019
CURRENT April 3, 2019
STABLE April 3, 2019
We’ve made some big changes to our Privacy Controls and Cookie Solution so that it’s now faster, better and more user-friendly than before. In addition to the previously available automatic prior blocking of the scripts of advertisers that are a part of the IAB Vendor Network, we’ve added these new features, available with the new Privacy Controls and Cookie Solution integration code:
- IAB Transparency and Consent Framework compatibility
Now available on all Privacy Controls and Cookie Solution channels
- Multiple options for accepting/rejecting cookies
Functionality now available on both an individual basis and as a bulk action
- GDPR protections for all users or EU users only
You can now indicate who you’d like GDPR protections applied to
- Ability to request new consent from users that previously provided consent (if the IAB Framework preference is not found)
- Cleaner markup
The cookie notice now has a cleaner markup and a stronger CSS reset in anticipation of future additions
- Dynamic notice text
The notice text displayed will now automatically change based on the detected consent collection options (e.g. when consentOnScroll
is disabled) and purposes
- Cookie notice position
You can now easily position the cookie notice from directly within the configurator, to either the top (default) or bottom of the page, without adding CSS styles
- Easily accept only explicit consent
You can now easily enable or disable the newly introduced consentOnContinuedBrowsing
property from directly within the configurator
- Second level domains
All second level domains can now be handled without additional configuration
- Speed improvements
- Now the Privacy Controls and Cookie Solution starts without waiting for all the page’s resources to be loaded (
startOnDomReady
defaulted to true)
- We sped up the loading of the inline activator by changing the
safeTimeout
default value to 0
- We decreased the
inlineDelay
default value to 500 to reduce the total time of activation