Mobile & OTT/CTV Consent - March 13, 2026 - 202603.1.0

Fixed Admin

  • Resolved an issue that prevented some text styling configurations on mobile app templates from matching their web version.

Fixed Android

  • Resolved an issue that prevented the startSDK call from correctly initializing and authenticating the user profile, and consent log requests made after the startSDK call were not sent as expected.

  • Resolved an issue that prevented users from customizing the Close button in the preference center using JSON theme configuration.

  • Resolved an issue that caused apps to quit unexpectedly if the preference center description was configured as empty.

Fixed iOS

  • Deprecated NSCoding functionalities have been fully removed from the SDK.

  • Resolved an issue that caused the scanner to recategorize SDKs to their default category.

  • Resolved an issue that prevented SDK descriptions from displaying in the preference center.

Fixed APIs

  • Resolved an issue that caused Always Active categories to display as rejected in the IABUSPrivacy_String parameter within the storageKeys object of the response if users set the interactionType request parameter to BANNER_REJECT_ALL when leveraging the Log Consent API.

Fixed HTML5

  • The SDK has been updated to remove localStorage.clear() and prevent the erasure of other variables.

New Public Preview Features

Enhancements to Consent Management Platform APIs

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

  • The Log Consent API now supports authentication when the Require authentication for known users setting is enabled in geolocation rules. This enhancement allows you to secure API calls when logging consent.

  • Updated the Log Consent API to return error codes and more detailed error messages when the body JSON is left empty.

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.

Accessibility Conformance

  • Screen readers now correctly announce checkbox list elements in the SDK and Vendor lists within the Preference Center as "checked" or "unchecked" on LG TV devices (WCAG-A 1.3.1: Info and Relationships).

Things to Know

HTML tags for line breaks within CMP templates are now supported for the Roku SDK.

Scan results for scans launched prior to 202602.1.0 will now display with the legacyScan resultsinterface.

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.