January 2023 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. 


  • January 31, 2023 at 4:00 PM CT
    • Assessments: Vendor Assessments are now available. Two new templates have been added for vendor security and vendor privacy. Assessments can now be assigned to third parties who will be able to access them at a dedicated portal.
  • January 27, 2023 at 11:00 AM CT

    • Consent Management: Added a global reject signal to the AMP consent integration so that when a user has denied consent for any category (marketing, analytics, personalization), non-personalized ads can be served by ad vendors who do not yet support granular consent settings. Read more about installing Osano on AMP pages.

  • January 19, 2023 at 04:00 PM CT

    • Web Application/Consent Management: Users with the Consent Manager role can now filter their configurations by Organization.

    • Web Application/Consent Management: A new option has been added to Customization Settings to disable the Timer for the implied consent banner (banner template 1). Turning this timer off will result in the banner being visible until a user clicks the 'X' to close it.

    • Web Application/Consent Management: Added an additional string to the Text Customization section to allow custom text for the drawer text for ‘View Cookies’.

    • Web Application/Consent Management: Updated styling and organization of the Settings page for better readability. 

Bug fixes

  • January 23, 2023 at 11:00 AM CT

  • January 16, 2023 at 04:30 PM CT

    • Consent Management: Fixed an issue where customers using the analytics provider Crazy Egg were sometimes unable to scroll in the CMP drawer due to a conflict with site scroll position behavior.

  • January 9, 2023 at 10:00 AM CT
    • Consent Management: Fixed an issue where, in certain cases, libraries that intercept script requests (such as jQuery) could conflict with Osano’s CMP and cause the script to execute twice. The solution was marking nodes once they are allowed and not repeating the “allow” behavior, leaving the other library to perform its interception and execution as intended.