Mobile & OTT/CTV App Consent - June 5, 2026 - 202606.1.0

Fixed iOS

  • Resolved an issue that cleared and inconsistently rewrote IAB TCF consent strings during SDK initialization.

Fixed Apple TV

  • Resolved an issue that prevented focus from consistently applying to elements on the CMP when configured in a right-to-left language or layout.

New Public Preview Features

Enhancements to Consent Management Platform APIs

The following enhancements have been made to the Consent Management Platform (CMP) APIs:

  • Updated the Log Consent API to include the OT-Explicit-Consent header parameter to allow sending only explicit consent choices rather than consent to all purposes tied to the CMP collection point. When OT-Explicit-Consent: true, consent will be logged only for the purpose for which consent was updated. When OT-Explicit-Consent: false, consent will be logged for all purposes.

    Note:

    This parameter is currently supported only for the UC_PREFERENCE_CENTER_CONFIRM interaction type.

  • Updated the Get Universal Consent Purposes API to include the lastConsentedDate response parameter. The lastConsentedDate will be returned for each purpose for which consent was given.

  • Updated the Get Universal Consent Purposes API to include the following parameters within the storageKeys object of the response:

    • OT_GroupConsents

    • OT_GroupLIConsents

    • OT_SdkConsents

    • OT_GeneralVendorsConsents

    • OT_LastConsentedDate

  • Updated the Get Banner Data, Log Consent, and Get Preference Center Data APIs to include the OT_UCPConsents parameter within the storageKeys object of the response.

  • Updated the consent transaction types sent when logging Universal Consent preferences using the Log Consent API.

    • For first-time consent:

      • If consent is given for a purpose with or without options selected, the transaction type will be CONFIRMED.

      • If consent is not given for a purpose, the transaction type will be OPT_OUT.

    • If consent was previously given for a purpose and is given again, the transaction type will be CONFIRMED.

    • If consent was previously given for a purpose but is later removed, the transaction type will be WITHDRAWN.

    • If consent was previously given for a purpose and the user modifies topics or custom fields, the transaction type will be CHANGE_PREFERENCES.

Existing Public Preview Features

Consent Management Platform APIs

The following APIs are now available for use with retrieving interface attributes needed to display the Banner and Preference Center, retrieving a list of active IAB and Google Vendors to display on the Preference Center, and logging consent when an end user interacts with a Banner or Preference Center. These APIs enable you to easily access data for Banner and Preference Center implementations, disclose vendor information to end users, and capture end user consent.

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

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.2 Templates

Enable the Global Privacy Protocol setting on TCF 2.2 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.

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.