December 2021 Release Notes

  • Updated

Note: Any Consent Manager Platform (CMP) changes will be inherited by consent manager configurations after they are republished. Please be sure to test all changes. 

New features

  • December 16, 2021, at 9 AM CT
    • Data subject rights portal: Introducing Osano's secure messaging portal. From here you can communicate directly with your data subjects to ask and answer questions or provide updates about their requests. Read more about secure messaging HERE. 


  • December 22, 2021, at 10 AM CT
    • DSAR: All form fields besides email may now be excluded when building DSAR forms.

  • December 15, 2021, at 7 AM CT
    • API keys: Minor updates to the API Keys page under the Settings Menu
  • December 1, 2021, at 11:31 CT
    • Web application: Introducing "Quick Create" for consent manager configurations. Previously, setting up a new configuration required setting 12 different attributes before you could generate your config. Now, when adding a new consent configuration, you will be prompted for only three fields to start: Name, Domain, and Policy URL and then provided with your published Osano code. You may continue to access additional configuration settings at any time after the initial creation of your config or by clicking Advanced Settings in the creation prompt.

Bug fixes

  • 12/17/2021 - [11:18 CST]
    • Consent manager: Fixed an issue with setting the defer/async attributes on scripts and iframes via setAttribute() where the element’s property would not be set correctly. This primarily affects scripts marked as “defer” where the page is using an accelerator such as Cloudflare’s Rocket Loader.
  • 12/13/2021 - [16:13 CST]
    • Consent manager: Resolved an issue where the banner fade-in animation was not properly triggering for the consent dialog banner when first appearing on the page. This is a minor UI fix that affects all consent manager configurations
  • 12/01/2021 - [11:31 CST]

    • Consent manager: Fixed an issue with Google Recaptcha where the height of the object was not being reverted from 0 when iframe blocking was enabled. This would only affect users utilizing iFrame blocking as well as the embedded version of Google Recaptcha.