/ /

April 2026 Release Notes

Updated 4 months ago

What's new for Osano in April 2026

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.

Enhancements

  • April 27 12:40 CDT

    • Subject Rights

      • Subject Rights Forms now have a Processing section where you can add the integrations and manual tasks that will generate action items for any request to the form.

      • You can now set an integration or manual task as the priority in your Subject Rights workflows. This allows you to select which integration or task will run first.

  • April 20, 9:40 AM CDT

    • Cookie Consent

      • Consent records now capture a visitor's IPv6 address when available.

  • April 17 12:00 PM CDT

    • Web Application

      • All legacy reporting previously available as a platform feature has been replicated in the product-specific dashboards. All Subject Rights reports are available on the Reporting tab under Subject Rights. Consent Manager reporting is available on the Reporting tab under Cookie Consent, and account‑level data for consent configurations can be exported directly from the Configurations listing page.

  • April 16, 2:15 PM CDT

    • Cookie Consent

      • The Consent Search table has been updated with improved data visibility:

        • The Consent Date column now includes the time of consent (displayed in UTC, matching the consent record timestamp).

        • Additional contextual columns have been added to help consent managers better understand the demographics and context of each consent record.

      • Consent Search now supports searching by External User ID (UserData) and IP address without requiring a consent UUID.

  • April 9, 10:40 PM CDT

    • Cookie Consent

      • The Osano Shopify app has been updated to support the latest Shopify UI Extension architecture (2025-10), migrating from React to Preact + Web Components.

  • April 8, 3:50 PM CDT

    • Cookie Consent

      • The IAB Vendors page in the Osano webapp now supports multi-select for vendor management. Customers no longer need to add IAB TCF vendors one at a time. New capabilities include:

        • View and select all vendors in a single action.

        • Select multiple individual vendors and add them in one operation.

  • April 7, 3:50 PM CDT

    • Cookie Consent

      • The CMP now automatically fetches the latest IAB Global Vendor List (GVL) at runtime, ensuring customers are always in compliance with IAB TCF requirements without needing to manually save and republish their configuration.

Bug Fixes

  • April 23 11:21 AM CDT

    • Cookie Consent

      • Fixed a bug where script discoveries containing query strings in their source URL were not being matched against existing rules, causing previously classified scripts to reappear as new, unclassified discoveries.

  • April 21 10:56 AM CDT

    • Cookie Consent

      • Resolved a bug where customers using the Osano REST API to programmatically create cookie rules were receiving a 500 Internal Server Error ("Missing required arguments to create FeatureFlags object"). Rule creation via POST /v1/cookie-consent/rules now works as expected.

  • April 8 3:54 PM CDT

    • Cookie Consent

      • Resolved an ARIA markup issue in the "View Disclosures" drawer where <dl>, <dt>, and <dd> elements were incorrectly mixed with <li> elements and role="list". Screen readers (e.g. NVDA) were announcing each disclosure item as its own "Group" instead of reading them as a continuous, accessible list.

      • Resolved a bug where the consent preferences dialog rendered an invisible, empty heading element in the accessibility tree when the preferences drawer was in a closed state. This caused false positives in accessibility audit tools such as WAVE, SiteImprove, and axe (WCAG 2.2 AA).

  • April 2 12:44 PM CDT

    • Cookie Consent

      • Resolved a WCAG 2.4.7 (Focus Visible) issue where the Osano consent banner was suppressing the browser's default keyboard focus outline on interactive elements (buttons, links) without providing a replacement visible focus indicator. The focus color can be set and updated within the Styles page of the configuration.

Was this article helpful?
Subscribe to receive updates on this article