Universal Consent & Preference Management - December 5, 2025 - 202512.1.0
General Availability
- Table Enhancements for Collection Points
-
Tables on the Collection points screen have been upgraded to improve usability, accessibility, and customization, including resizable columns, more records per view, clearer row actions, and more. 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.
- New Parameter for Get Data Subject’s Preferences API
-
Updated the Get Data Subject's Preferences API to include the
authorizationheader parameter. This ensures secure, authenticated access to a user’s consent profile by leveraging a JSON Web Token (JWT) generated through the cross-device consent process.
Fixed
-
Resolved an issue when saving data elements on a consent profile that caused some data elements to retain older values despite receiving updated information from more recent interactions.
-
Resolved an issue that caused the Get Data Subject Details V4 API to return a 404 error after merging data subjects.
-
The Profiles screen has been enhanced for improved performance when accessed by users in a non-root organization.
Existing Public Preview Features
- CMP Consent Context
-
Added support to our existing data hierarchy to allow CMP consent users to provide consent for a purpose multiple times when using consent groups. When using consent groups with the unified profile feature, the CMP will use the same data subject for different consent groups, eliminating the need to create additional profiles.
Things to Know
- End of Support Notification for Get Data Subject’s Preferences V1 API
-
The Sunset Period for the Get Data Subject’s Preferences V1 API has ended. As of November 23, 2025, this API is now deprecated. Any customers leveraging this API are encouraged to use the Get Data Subject’s Preferences V2 API.
For more information, see OneTrust API Sunsetting & Deprecation Guidelines.
-
Salesforce single sign-on (SSO) is now supported when users log in to preference centers.
- 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.