Ketch and The Trade Desk - Unified ID 2.0

Generate a cookieless ad identifier only for people who've actually consented, not by default the moment a page loads.

The Trade Desk - Unified ID 2.0

About The Trade Desk - Unified ID 2.0

Unified ID 2.0 (UID2) is a privacy-focused framework built to replace third-party cookies, using anonymized email-based identifiers to enable targeted advertising while aiming to preserve user consent and transparency. UID2's own governance guidelines are explicit on this point: if a consumer opts out, participants are required to stop using that consumer's information to create or generate a UID2 token going forward. That requirement only means something if token generation is actually gated on a real consent check.

Ketch connects to UID2 to enforce exactly that gate.

Capabilities

How Ketch works with The Trade Desk - Unified ID 2.0

The Ketch UID2 integration covers Consent Orchestration.This is a client-side, per-purpose gate rather than a platform-wide toggle, which means it can be tied to whichever specific Ketch purpose actually governs targeted advertising for that property.

Consent Orchestration

The core mechanism is a conditional script: Ketch listens for consent events and only triggers UID2 token initialization when the `targeted_advertising` purpose (or whichever purpose an organization maps to this) has been granted. If consent for that purpose isn't present, the token initialization function simply doesn't run, so no UID2 token gets generated for that visitor.

With Ketch, teams can

  • Gate UID2 token generation behind a specific, mapped consent purpose rather than generating tokens by default
  • Avoid creating a UID2 identifier at all for someone who hasn't consented to targeted advertising, rather than generating one and trying to suppress it afterward
  • Point opted-out users to UID2's own global opt-out mechanism at transparentadvertising.com as an additional, platform-level control

The gap

The problem this integration solves

An identifier framework built around consent only works if consent is actually checked before the identifier gets created, not after:

01. Generating a UID2 token by default and only suppressing it later means the identifier existed at least momentarily, which isn't the same as never creating it

02. UID2's own compliance guidance requires stopping token generation on opt-out, which needs an actual code-level gate to enforce, not just a policy statement

03. Without a real-time consent check tied to page load, there's no reliable way to guarantee token generation only happens for genuinely opted-in visitors

Ketch resolves this with a conditional script tied directly to Ketch's consent event system, so token generation is gated before it happens rather than cleaned up afterward.

Why Ketch

Why teams choose Ketch for Unified ID 2.0 privacy compliance

Permissioning infrastructure that governs The Trade Desk - Unified ID 2.0 the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.

  • Gates generation before it happens, not after

    The conditional script means a UID2 token is never created for someone who hasn't consented, rather than being created and suppressed retroactively.

  • Tied to a specific, mappable purpose

    The gate can be configured against whichever Ketch purpose actually governs targeted advertising for a given property, rather than a one-size-fits-all toggle.

  • Backed by enforcement precedent

    The California Privacy Protection Agency fined Honda $632,000 over improperly configured data sharing with ad-tech partners, a reminder that identity frameworks built for advertising carry real exposure if consent isn't enforced before, not after, identifier creation.

Questions about the The Trade Desk - Unified ID 2.0 integration

Integrations

Pre-built APIs with 1,000+ systems, apps, and models

Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.

Browse All Integrations

See The Trade Desk - Unified ID 2.0 permissioning running end to end

Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect The Trade Desk - Unified ID 2.0 yourself.

Get Started Free

Get started in less than 5 min