Universal Consent & Preference Management - September 4, 2026 - 202609.1.0

General Availability

Integration Event Trigger for Data Subject Profile Merge Completion

Leverage the new Data Subject Merge Completed event type when building integration workflows in Integrations. This event is triggered when a data subject profile merge has been completed.

For more information, see Consent Integration Events. This feature is related to the following ideas: CD-I-160.

addendum: This release note was added on September 11, 2026.
Enhancements to Bulk Export APIs

Updated the Bulk Export APIs with the following enhancements:

  • Updated the Create Bulk Export API to support the ANONYMOUS_RECEIPTS export type, enabling bulk exports of anonymous consent interaction data. This enhancement introduces a dedicated export path for anonymous receipt records, separating anonymous traffic from identified receipt exports.

  • Updated the Create Bulk Export API and Get Bulk Export Status API to support the collection point type filter option within the params object of the request. This filter enables receipt exports to be filtered by collection point type, such as WEB_FORM, MOBILE_APPLICATION, API, COOKIE, TRUST_CENTER, and more.

  • Updated the Create Bulk Export API to separate identified and anonymous receipt data into the appropriate exports and improve the data available through the Anonymous Receipt bulk export. The API will now behave in the following manner:

    • COOKIE_RECEIPTS exports now return only identified cookie receipt data and no longer include anonymous receipt records.
    • ANONYMOUS_RECEIPTS exports now serve as the dedicated export type for anonymous receipt data and have been enhanced to return decrypted dataSubjectIdentifier, geolocation, and dsDataElements values, as well as the additional otJwtVersion, receiptJwt, and isAnonymous fields.
    • CONSENT_RECEIPTS exports now return all identified receipt data, including identified cookie receipts, when the collectionPointType filter is not specified.
    addendum: This release note was added on October 16, 2026.
Enhancements to Consent Receipts APIs

Updated the Create Consent Receipts API to include the ReactivationDate request parameter to specify when a withdrawn or opted-out consent purpose should be automatically reactivated. This parameter supports temporary consent withdrawal scenarios by allowing consent to be reactivated on a specified date and time.

Fixed

  • Resolved an issue that prevented the Get Bulk Export Status API from returning the correct value for the recordCount parameter when filter criteria was applied using the params object.

  • Resolved an issue that caused the Get List of Receipts V2 API to return isValid: true for the purposeNote object when a purpose note was not present.

  • Resolved an issue that incorrectly included deleted data subject records in the tenant usage metrics count.

  • Resolved an issue that prevented additional identifiers from populating as data elements within receipts.

  • Resolved an issue that prevented magic link tokens from populating in data subject bulk exports when parent identifiers for a data subject group were created via consent receipt.

  • Resolved an issue that prevented data subject merges from completing successfully when new consent receipts were submitted containing an additional identifier with an empty value.

  • Resolved an issue that prevented consent receipts from being stored with the incorrect organization ID after collection points were synced.

  • Resolved an issue that prevented a purpose's expiry date from clearing from the expiryDate object within the profiles object of the Get Data Subject Details V4 API after consent receipts were submitted with the ClearExpiration option enabled in the receiptOptions object.

  • Resolved an issue that prevented text for Other unsubscribe reasons on the preference center from correctly translating to Chinese (ZH-TW).

  • Resolved an issue that removed the Identifier type from data subject profiles created by collection points with the Double opt in setting enabled.

    addendum: This release note was added on September 11, 2026.

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

TheReceipt summarypane on theData subject detailsscreen now displays associatedPrivacy noticesonly when the notice's linked purposes have received consent.

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.