Mobile & OTT/CTV App Consent - August 7, 2026 - 202608.1.0 (Summer Release)

General Availability

Link Age Ranges to Purposes

Link age ranges to categories and purposes for enhanced compliance with Age Gate requirements. This enhancement allows you to configure your SDK to hide specific categories or purposes to prevent users from consenting to those specified categories or purposes.

This feature is available for the following platforms:

  • Android

  • iOS

  • Roku

  • Maui

  • HTML5

  • Unity

For more information, see Configuring Age Gate Prompts for Mobile Apps,

New Applications APIs

|Available with Solution Packaging Only

Added APIs to retrieve application scan results, detected SDKs, permissions, and iOS privacy manifest analysis data. These APIs help developers programmatically analyze mobile applications, monitor scan results, identify detected SDKs and permissions, and review iOS privacy manifest compliance data.

Fixed Admin

  • Resolved an issue that prevented the Identifier column from populating on mobile app exports.

Fixed Android

  • Resolved an issue that prevented text configured in right-to-left languages from displaying with the correct formatting on the banner and preference center.

Fixed iOS

  • Resolved an issue that recategorized apps to their default category and overwrote previous manual categorization upon scan completion.

  • Resolved an issue that prevented text configured in right-to-left languages from displaying with the correct formatting on the banner and preference center.

Fixed Android TV

  • Resolved an issue that prevented hyperlinks in the banner description from responding when selected.

Fixed Apple TV

  • Resolved an issue that caused tvOS apps to quit unexpectedly when scrolling through parent category details for bundle groups and IAB stacks on the preference center.

Fixed API

  • Resolved an issue that caused restricted linked categories to be included in IAB legitimate interest (LI) consent processing when the App Tracking Transparency (ATT) permission was not granted. Restricted linked categories are now excluded from LI consent calculations and their LI status is returned as inactive (groupLIConsent = 0).

  • Resolved an issue that caused DSAR requests to fail when using unsupported language codes. The language is now hardcoded to en-us to prevent empty translations when a language is not enabled in the web form.

  • Resolved an issue that caused the CMP APIs to create separate cache entries for requests that differed only by query parameters. Cache keys now use only the URL origin and pathname while preserving the full URL for request processing, improving cache efficiency and ensuring consistent cache hits across requests with different query parameter values.

  • Resolved an issue that caused the Get List of Applications API to return an error when valid requests were submitted.

  • Resolved an issue that skipped CCPA consent processing for Age Gate and App Tracking Transparency (ATT) interaction types. Consent processing is now applied consistently for these interaction scenarios.

    addendum: This release note was added on August 14, 2026.

  • Resolved an issue in Age Gate consent processing where an undefined upper age bound could result in incorrect consent range evaluation. Age ranges without a specified upper bound are now treated as open-ended to ensure accurate age eligibility calculations.

    addendum: This release note was added on August 14, 2026.

New Public Preview Features

New Submit Global Opt-Out Request API

Added the Submit Global Opt-Out Request API as part of the CMP APIs to allow applications to submit a Global Opt-Out Data Subject Access Request (DSAR) on behalf of a data subject. This API enables organizations to support global opt-out workflows and honor data subject opt-out preferences across devices and services.

addendum: This release note was added on August 14, 2026.
Enhancements to Consent Management Platform (CMP) APIs

The following enhancements have been made to the CMP APIs:

  • Added the GlobalOptOutMobileSectionHeader and GlobalOptOutEmailFieldPlaceholderText keys and removed the GlobalOptOutDescription key. These changes enable correct display of the mobile section header and email placeholder text in Global Opt-Out implementations.

  • Updated the Global Opt-Out implementation to use customCategoryId for a group instead of groupId when determining the associated purpose. This enhancement ensures purpose values are resolved consistently across languages when new languages are added to the Global Opt-Out configuration.

  • Enhanced Age Gate consent string generation to represent hidden, non-actionable purposes as not applicable (0) instead of opted out (1). When a purpose is hidden because a user is below the permitted age range, generated consent strings now reflect that consent could not be provided, aligning privacy string output with Age Gate behavior.

  • Applied performance optimizations to CMP APIs, reducing response processing times for the Get Banner Data API, Get Preference Center Data API, and Get IAB and Google Vendors API.

  • Added the OT-Cache-Status response header to provide cache hit and miss visibility for CMP API requests. The header returns cache status information for individual fetch operations, helping developers troubleshoot caching behavior and monitor API performance.

    addendum: This release note was added on August 14, 2026.

  • Added support for the globalOptOutData response object in the following APIs to return Global Opt-Out configuration data and UI elements, including linked categories, confirmation messages, instructional content, communication preferences, and display text:

    addendum: This release note was added on August 14, 2026.

  • Added support for the ERROR_CODE_GLOBAL_OPT_OUT_NOT_CONFIGURED, ERROR_CODE_GLOBAL_OPT_OUT_DISABLED, and ERROR_CODE_DSAR error codes to provide more detailed error handling and troubleshooting for Global Opt-Out and DSAR-related scenarios.

    addendum: This release note was added on August 14, 2026.

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.