Cookie Solution changelog

1.5.0 – 1.5.4 (2019-04-16)

• 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.3.15 – 1.4.0 (2019-04-05)

• Ability to collect explicit consent for Google personalized ads
• googleAdsPreferenceManagement option added
• isTCFConsentGlobal option added
• Bug fixes

1.3.11 (2019-03-11)

We’ve made some big changes to our 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 Cookie Solution integration code:

• IAB Transparency and Consent Framework compatibility
  Now available on all 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 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

1.3.11 – 1.3.14.3 (2019-04-03)

We’ve made some big changes to our 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 Cookie Solution integration code:

• IAB Transparency and Consent Framework compatibility
  Now available on all 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 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