What are the immediate next steps?

All customers:

  • Identify whether you use standard OneTrust TCF content or custom TCF text.
  • Confirm whether choices remain within one device or persist across multiple devices.
  • Confirm whether choices apply to one digital property or a defined group of properties.
  • Review how account-level and device-level preference conflicts are resolved.
  • Plan testing before the applicable web or native deadline.

Web customers:

  • Test and republish using an applicable version after OneTrust 202609.2.0 becomes available.
  • Complete validation before October 23, 2026.

Mobile and CTV customers

  • Test the updated native implementation and framework content.
  • Complete validation before February 23, 2027.

Customers using custom TCF text

  • Ensure the consent scope and, where applicable, device scope are clearly explained.
  • Identify the websites, applications, or services included in a group-specific consent scope.
  • Confirm that the wording reflects the actual implementation.
  • Do not imply that choices apply across websites, applications, browsers, or devices if that behavior is not implemented.