Cookie Consent - April 25, 2026 - 202604.2.0
General Availability
- Table Enhancements for Scripts
-
Tables and table functionalities on the Scripts screen have been upgraded to improve usability, accessibility, and customization, including resizable columns, more records per view, and clearer row actions. These updates are designed to provide a consistent and improved user experience, helping users work more efficiently with data and tailor their experience to their specific needs.
For more information, see Table Enhancements Across the OneTrust Platform and Table Enhancements User Guide.
- Tracking Technology Deletion on Opt‑Out
-
Automatically delete tracking technologies when users opt out of a given category. This enhancement deletes tracking technologies after users opt out to better support enforcement and compliance directives.
- New Get List of Applications API
-
Added the new Get List of Applications API that allows you to retrieve a paginated list of applications with optional filtering capabilities. This API enables programmatic access to application data to support CMP deployments at scale through public, API‑driven workflows.
Fixed
-
Resolved an issue that prevented the Compliance assistant from returning scans for some enabled frameworks.
-
Resolved an issue that copied the production script instead of the test script when the test script was copied from the Website details screen.
Existing Public Preview Features
- Enhanced Auto-Blocking Interface
-
Leverage an improved Auto-Blocking experience, featuring a redesigned safe list, block list, and match list. The enhanced Auto-Block tab is designed for a quicker and easier user experience when reviewing and blocking URLs.
For more information, see OneTrust Cookie Auto-Blocking (Enhanced Interface).
- Banner SEO Configuration
-
Deploy your banner script with header (
<h>) tags replaced as paragraph (<p>) tags for improved search engine optimization.For more information, see Publishing and Implementing Cookie Consent Scripts, or contact OneTrust Support or your account representative.
- Support for Multi-Language Privacy Policy Links
-
Configure privacy policy links in multiple languages on the Dynamic Links section of the Website Details screen. This feature enables you to offer privacy policy links and information in each language relevant to your business needs.
For more information, see Configuring Domain Branding.
- Enhanced State Support for the Global Privacy Platform
-
The Global Privacy Platform (GPP) settings now support consent strings for the following US states:
-
Delaware
-
Iowa
-
Nebraska
-
New Hampshire
-
New Jersey
-
Tennessee
For more information, see Configuring Global Privacy Platform Settings.
-
- Bulk Export APIs
-
The following APIs are now available for use to create and cancel bulk exports and retrieve their status, progress, download details, and credit details. These APIs enable users to extract large volumes of cookie receipts at once with a limit of six bulk exports per month.
- Authenticated Consent for New and Existing Users
-
Transfer consent from local storage to new and existing data subject IDs (DSIDs) for user profiles when leveraging Cross-Device Consent. This enhancement allows you to apply previously captured consent to user profiles to streamline consent collection.
- Always Inactive Consent State
-
Leverage the new Always Inactive consent state to allow users to display tracking technologies that are present but not enabled on their websites. This consent state enables you to notify your end users that a tracking technology is deployed but not active.
For more information, see Cookie Consent Models and Configuring Geolocation Rules.
- Enable Global Privacy Platform on TCF 2.2 Templates
-
Enable the Global Privacy Platform setting on TCF 2.2 templates. This setting allows you to enable the IAB Tech Lab - Global Privacy Platform (GPP) and populate the IAB TCF EU section of the GPP string.
For more information, see Configuring the Global Privacy Platform Settings.
- Vendor Identification, Categorization, and Consent
-
Vendor Identification, Categorization, and Consent enables you to categorize any vendor services on your website and provide detailed consent options to your visitors. This feature streamlines vendor disclosure and consent by detecting known services and linking them to tracking technologies. Leverage Vendor Service Identification, Categorization, and Consent to perform the following actions:
-
Identify known vendor services when scanning your websites.
-
Categorize the vendor services active on your websites.
-
Link tracking technologies to identified vendor services.
-
Allow end users to configure consent for vendor services on the Preference Center.
-
Capture records of consent at the vendor service level.
-
Configure IAB templates to capture and disclose vendor service information.
-
View source URLs for tag initiators on the Initiators tab of the Scan Results screen.
For more information, see Vendor Identification, Categorization, and Consent Feature Guide.
-
- Legitimate Interest Configuration for Reject All on IAB Templates
-
Implement a Reject All button on your Preference Center and Cookie Banner that prevents objection to legitimate interest. This enhancement improves compatibility with Google Limited Ads.
For more information, see Customizing the Preference Center Template.
- Server-Side Rendering
-
Server-side rendering is now available for Cookie Banner HTML and CSS.
For more information, see Server-Side Rendering: Performance and Availability.
Accessibility Conformance
-
The “List of Partners" link is now correctly identified by screen readers as a link instead of a button (WCAG-A 4.1.2: Name, Role, Value).
-
Unnecessary heading levels have been removed from
<tablist>elements on the preference center (WCAG-A 4.1.2: Name, Role, Value). -
The elements
<fieldset>and<legend>have been added to the preference center to improve screen reader navigability of the cookie list filters (WCAG-A 3.3.2: Labels or Instructions).
Things to Know
- About Known Defects
-
Issues that may impact our customers are documented in our Known Defects Database located here with approved workarounds and targeted releases for resolving the issue.