Mobile & OTT/CTV App Consent - November 13, 2026 - 202611.1.0 (Fall Release)

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. Specific details are captured within the following updates:

  • Web SDK Support for the Log Consent API

  • Web SDK Support for the Get IAB and Google Vendors API

  • Web SDK Support for the Get Banner Data API

  • Web SDK Support for the Get Preference Center Data API

For more information, refer to the cmpapi-202611.1.0 Release Notes and Changelog. This feature is related to the following ideas:

OT-I-9796, OT-I-10670, OT-I-16661.

Fixed Admin

  • Resolved an issue that prevented purposes from populating on the Template details screen when using the search bar in the template's Universal consent purposes tab to find and add purposes.

Fixed iOS

  • Resolved an issue that caused stale consent data from a previous profile to be incorrectly copied to the active profile during SDK initialization when multi-profile consent was disabled.

  • Resolved an issue that prevented the banner from being suppressed in web views when using authenticated consent on iOS devices.

Fixed Android TV

  • Resolved an issue that caused applications to become unresponsive on Android TV when viewing the vendor list on the preference center.

Fixed Apple TV

  • Resolved an issue that caused stale consent data from a previous profile to be incorrectly copied to the active profile during SDK initialization when multi-profile consent was disabled.

Fixed Roku

  • The Animation.optional field and rohttpagent.InitClientCertificates() function have been deprecated for Roku OS 16.

Existing Public Preview Features

Roku Support for Unified Consent Profile for Known Users

Leverage the new Unified Consent Profile for Known Users functionality to connect data subjects' CMP preferences with Universal Consent & Preference Management profiles by enabling the Create data subject profiles for known users setting on the Geolocation Rules tab. You can also easily trigger integration workflows to send CMP preferences to downstream systems, and efficiently manage your preferences in a unique Preference Center, centralizing all of them in one single profile.

This enhancement provides a comprehensive view of data subjects empowering you with more control over the data captured across both modules, resulting in a more streamlined and tailored user experience.

For more information, see Connecting CMP preferences with Universal Consent & Preference Management Profiles.

Configure Button Layout for the Banner

Configure the positioning of buttons on your mobile and CTV banners within the Button Sets section of the Template Details screen. This enhancement allows you to specify the positioning of buttons on your banners for a more customized experience.

  • iOS

  • Android

For more information, see Customizing the Mobile App Consent Banner Template and Customizing the Mobile App Consent Preference Center Template.

Enhanced Branding Settings for Mobile and CTV SDKs

Configure detailed branding settings for your mobile SDKs on the Branding tab of the Mobile App Details and CTV App Details screen, respectively. This enhancement enables you to configure more specific branding settings for each of your mobile and CTV applications.

For more information, see Configuring Mobile and CTV App Branding.

Validation for Cross-Device Consent Receipts | Available with Solution Packaging Only

Enable the Require Authentication for known users setting when leveraging Cross-Device Consent to require validation on your consent receipts. This enhancement allows you to more reliably collect consent from known users.

For more information, see Configuring Geolocation Rules.

Note:

This enhancement is only available to users with the Consent Rate Optimization (CRO) add-on package. Contact OneTrust Support or your account representative to enable this functionality.

To learn more, see Maximize Opt-Ins with Consent Rate Optimization.

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.

This feature is available for the following platforms:

  • iOS

  • Android

  • Apple TV

  • Android TV

Enable Global Privacy Protocol on TCF 2.4 Templates

Enable the Global Privacy Protocol setting on TCF 2.4 templates. This setting allows you to enable the IAB Tech Lab - Global Privacy Protocol (GPP) and populate the IAB TCF EU section of the GPP string.

This feature is available for the following platforms:

  • Android

  • Android TV

  • Apple TV

  • HTML5

  • iOS

  • Roku

  • Unity

  • Xamarin

For more information, see Configuring the Global Privacy Protocol Settings.

New Reject All Button Configuration

Enable the updated Reject All button configuration on the Preference Center template. This new configuration ensures that legitimate interest is not impacted for customers using Google Ads.

For more information, see Customizing the Mobile App Consent Preference Center Template.

Accessibility Conformance

  • The banner landing description is now announced first when the banner loads for the first time with screen readers enabled on iOS and Android. Additionally, the Close button spacing has been aligned across both platforms to ensure layout consistency (WCAG‑A 1.3.1: Info and Relationships).

  • Resolved an issue that prevented users from exiting the preference center using the device's back button or back gesture on Android devices (WCAG-AA 3.2.3: Consistent Navigation).

Things to Know

OneTrust iOS SDK CocoaPods Deprecation

OneTrust iOS SDK version 202611.1.0 will be the final version published through CocoaPods. This change aligns with the announcement that CocoaPods Trunk will become read-only on December 2, 2026. After this date, new pods and pod versions can no longer be published.

For more information, see CocoaPods Deprecation.

Consent Receipt Source Field and CTV Support

Consent receipts now store the Source field when the purpose IDs are empty or missing. Additionally, CTV is now supported as a valid source type for consent receipts.

Global Opt-Out Confirmation Modal on Roku

A global opt-out confirmation modal now displays on the SDK list in the preference center when an end user disables consent for an SDK linked to a parent purpose on Roku devices.

SingleSelectAriaLabel Accessibility Key

A new SingleSelectAriaLabel key has been added to application data to improve accessibility for single-choice configurations.

Improved Metadata Coverage for iOS SDKs

Metadata, including vendor, and description, is now available for over 200k iOS SDKs in the mobile app scan results.

Mobile Application Scan Timeout

Mobile application scans now automatically time out and are marked as interrupted if they remain in progress for more than 10 minutes.

Firebase SDK Detection Coverage

Android application scans now include detection coverage for Firebase SDKs.

Amplitude SDK Detection Coverage

Android application scans now include detection coverage for Amplitude SDKs.

WonderPush SDK Detection Coverage

Android application scans now include detection coverage for the WonderPush SDK.

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.