DocumentationmyOneTrustDeveloper ForumTechnology Partners
Changelog
Subscribe via RSS
Back to All

November 18, 2026 - cmpapi-202611.1.0

November 11th, 2026

The following updates are available as part of cmpapi-202611.1.0 and are scheduled to deploy on November 18, 2026.

Mobile App Consent

General Availability

  • Consent Management Platform APIs
    The following APIs are available for retrieving the interface attributes needed to display the banner and preference center, retrieving active IAB and Google vendor information, logging consent interactions, and submitting global opt-out data subject access requests. These APIs enable developers to retrieve the data required for banner and preference center experiences, disclose vendor information to end users, capture consent preferences, and support Global Opt-Out workflows across devices and services.
  • Consent SDK APIs for Web SDKs
    Added Web SDK support across CMP APIs to provide a shared foundation for delivering consent experiences across platforms. This enhancement helps customers maintain more consistent consent behavior, scale Web SDK deployments across large website portfolios, adapt to changing privacy requirements, and support contextual and custom consent experiences.
  • Web SDK Support for the Log Consent API
    Updated the Log Consent API to support OT-Device-Type: web, enabling Web SDK implementations to save and log consent through CMP APIs. This enhancement enables web consent receipts to capture web-specific interactions and consent signals, including banner actions, GPC and DNT changes, and consent experience dismissals.
    • Added support for web-specific interactionType values, including API_ALLOW_ALL, API_REJECT_ALL, API_UPDATE_CONSENT, GPC_VALUE_CHANGED, DNT_VALUE_CHANGED, ANONYMOUS_LOGGED_OUT_CONSENT, CROSS_DEVICE_SYNC_LOCAL, and NO_INTERACTION.
    • Added the canGenerateNotGivenReceipts and authenticatedLoggedOutConsent response fields under appConfig to indicate whether not-given and anonymous logged-out consent receipts are supported.
    • Added the NO_OPT_OUT transaction type for eligible opt-out purposes when a web user dismisses the banner.
    • Updated PurposeNote to return noteType and noteText in addition to noteId.
    • Added web-specific handling for GPC and DNT signals, consent experience dismissals, vendor services, empty receipts, and Advanced Analytics privacy data.
  • Web SDK Support for the Get IAB and Google Vendors API
    Updated the Get IAB and Google Vendors API to support OT-Device-Type: web, enabling Web SDK implementations to retrieve vendor data and configuration through CMP APIs. This enhancement enables web consent experiences to display and manage IAB, Google, and general vendor information using the shared CMP API.
    • Added support for IAB TCF v2.4, Google, and general vendor data, including applicable consent and legitimate interest statuses.
    • Added web-specific vendor list and vendor details UI data, including localized labels, titles, search and filter controls, accessibility attributes, and vendor detail information. This includes the vendorListDescription, filterAriaLabel, searchPlaceholderText, and searchAriaLabel fields.
    • Added support for filtering newly added IAB and Google vendors when configured to remain inactive.
    • Added web-specific layouts for displaying vendor information within preference center experiences.
  • Web SDK Support for the Get Banner Data API
    Updated the Get Banner Data API to support OT-Device-Type: web, enabling Web SDK implementations to retrieve the configuration and consent data needed to display web banner experiences through CMP APIs. This enhancement enables web implementations to retrieve banner presentation, interaction, accessibility, and consent configuration through the shared CMP API.
    • Added web-specific bannerUIData for layouts, positioning, accessibility, focus management, branding, custom styling, and interaction behavior.
    • Added configuration for banner actions and controls, including accept all, reject all, show preferences, save preferences, and close or continue actions.
    • Added support for choices banner content, purpose categories, privacy policy and imprint links, and web-specific accessibility labels.
    • Added web-specific configuration under appConfig, including banner display behavior, geolocation handling, Google Consent Mode, Additional Consent Mode, Multi-Cookie Management, global opt-out configuration, and other settings required for web consent experiences.
    • Added support for web consent storage data while maintaining consent string and storage key behavior across web, mobile, and CTV experiences.
  • Web SDK Support for the Get Preference Center Data API
    Updated the Get Preference Center Data API to support OT-Device-Type: web, enabling Web SDK implementations to retrieve the configuration and consent data needed to render preference center experiences through CMP APIs. This enhancement enables web implementations to retrieve preference center presentation, interaction, accessibility, and consent configuration through the shared CMP API.
    • Added web-specific pcUIData for preference center layouts, positioning, styling, branding, accordion behavior, accessibility, and other display configurations.
    • Added support for purpose hierarchies, consent and legitimate interest statuses, consent models, and GPC and DNT privacy signals.
    • Added configuration for preference center actions, including allow all, reject all, confirm choices, and close actions with corresponding interactionType values.
    • Added support for tracking technology and cookie disclosures, including cookies, local storage, and session storage.
    • Added web-specific search and filtering capabilities for cookies, vendors, and tracking technologies.
  • A/B Test Variant Details
    Updated the CMP APIs to include a variant response object under appConfig when an A/B test variant is resolved. The object returns the variant id and name, enabling you to identify which banner variant was delivered and confirm that users are assigned to the expected test group. This enhancement also helps troubleshoot geolocation-, audience-, and rule-based variant selection and validate banner behavior against the configured OneTrust experience across environments.
  • Granular Geo-Level Reconsent
    Added support for location-specific reconsent dates across CMP APIs and the Web SDK. When granular geo-level reconsent is enabled, the reconsent date is determined based on the visitor's matched state or region, then country, with the geolocation rule used as a fallback. This enhancement enables customers to apply reconsent requirements more precisely based on visitor location while preserving existing reconsent behavior when granular configuration is not enabled.
  • Cross-Platform Operating System Detection for CMP APIs
    Added the optional OT-OS request header across CMP APIs to enable cross-platform SDKs, such as .NET MAUI, to identify the underlying operating system independently of OT-Platform. The header supports Apple and Android values and takes precedence over OT-Platform when provided, enabling the appropriate OS-specific behavior for features such as App Tracking Transparency (ATT) and Google advertising identifiers.
  • Enhanced Error Response Headers for CMP APIs
    Added the OT-Error-Code response header to CMP API error responses. The header returns the unique error codes associated with the response as comma-separated values, enabling integrations and monitoring systems to identify and troubleshoot API failures without parsing the JSON response body.
  • Enhanced Consent Audit Data for Anonymous Receipts
    Updated anonymous consent receipts to always include consent audit information, regardless of whether Advanced Analytics is enabled. Anonymous consent receipts now return consent model and interaction type data in dsDataElements, ensuring key consent evidence is available for auditing and compliance investigations.