On this page
Unified ID 2.0 (UID2)
Unified ID 2.0 (UID2)
UID2 is an open-source identity framework for deterministic advertising on the open internet. It builds a pseudonymous, cookieless, cross-device identifier from a hashed and salted email address or phone number, enabling publishers and advertisers to target and measure audiences without third-party cookies.
What it is
The official UID2 documentation describes it as "an open-source identity solution built for the open internet" — a pseudonymous, deterministic, cookieless identity standard for digital advertising (unifiedid.com, last updated 2026-10-13). The framework was originally created by The Trade Desk and contributed to the IAB Tech Lab for independent governance; documentation is licensed Apache 2.0 and maintained at IABTechLab/uid2docs on GitHub (unifiedid.com/docs/intro, 2026-10-13).
A raw UID2 is a SHA-256 hash of a normalised email address or phone number. The framework uses salt-bucket rotation (roughly annually) so that even the raw hash changes over time — advertisers should check refresh timestamps daily (unifiedid.com FAQs, undated). The framework does not maintain a central store of personal data (DII) mappings (unifiedid.com/docs/intro, 2026-10-13).
Technical flow
The official documentation describes a five-step token-generation flow for publishers (unifiedid.com/docs/overviews/overview-publishers, 2026-10-13):
- User provides email or phone number to publisher
- Publisher sends directly identifying information (DII) to a UID2 Operator via SDK or API
- Operator salts, hashes, and encrypts → returns a UID2 token
- Publisher stores token and transmits to SSP
- SSP includes encrypted token in OpenRTB bid request
user.eidsarray
On the buy side, a DSP receives the bid request, decrypts the UID2 token into a raw UID2 using synced decryption keys, checks for opt-out, and if no opt-out, matches the raw UID2 to an audience segment before bidding (unifiedid.com/docs/overviews/overview-dsps, 2026-10-13). SDKs for DSP-side decryption are available in Java, Python, C#/.NET, and C++ (unifiedid.com/docs/overviews/overview-dsps, 2026-10-13). RTBlint notes that UID2, ID5, and RampID all travel in the OpenRTB 2.6 user.eids field — not user.ext.eids — each identified by its own source domain (rtblint.org, 2026-09-27).
Publisher integration paths include web (Prebid.js, JavaScript SDK, server-side), mobile (Android/iOS SDKs), CTV, and Google Ad Manager via Secure Signals (unifiedid.com/docs/overviews/overview-publishers, 2026-10-13).
[!stale-risk] As of 2026-10-09, iOS 27 and macOS 27 WebKit blocks browser requests to
uidapi.com, preventing JavaScript SDK CDN loading and client-side token generation/refresh in affected browsers. The official UID2 documentation recommends a server-side integration as the workaround (unifiedid.com/docs/ref-info/updates-doc, 2026-10-09). (as-of 2026-10-09)
Governance
The Trade Desk "currently serves as a Public Operator" and Core Administrator for the UID2 framework (unifiedid.com, undated; gsdsi.com, 2026-10-01). The handover to fully independent organisations is not yet complete as of October 2026 (gsdsi.com, 2026-10-01).
Prebid.org initially agreed to serve as a UID2 operator in February 2021 but paused that arrangement; Prebid chair Garett McGrath publicly called TTD's dual role as DSP and UID2 administrator "grading your own homework," and Prebid declined an operator role unless TTD ceded administration (gsdsi.com, 2026-10-01; ppc.land/universal-id/, 2026).
All participants who execute an appropriate participation agreement can access UID2; roles include publishers, advertisers, data providers, DSPs, and Operators (Public or Private) (unifiedid.com/docs/intro, 2026-10-13). Any company can also run a Private Operator — for example, a guide exists for running the UID2 Operator Service on Azure Kubernetes Service (AKS) backed by Azure Container Instances (unifiedid.com/docs/ref-info/updates-doc, 2025-03-19).
Governance status: Smart Marketer (published 2026-08-31) states that "Prebid.org now governs UID2." GSDSI (published 2026-10-01) states The Trade Desk remains Core Administrator and that Prebid paused its operator role. The GSDSI source is more recent and more detailed, and aligns with the official UID2 documentation (unifiedid.com), which still lists The Trade Desk as Public Operator.
Adoption
Over 300 companies have implemented UID2, according to Landbase tracking data cited by Smart Marketer (smartmarketer.net, 2026-08-31). (as-of 2026-08-31) The Trade Desk CEO Jeff Green stated that UID2 has reached "critical mass" (smartmarketer.net, 2026-08-31).
Named publisher adopters include The Washington Post, New York Post, Dotdash Meredith, and The Hollywood Reporter; streaming and CTV adopters include Roku, Fox, DirecTV, Spotify, and Pandora (smartmarketer.net, 2026-08-31). Named partner logos on the official UID2 site include Acxiom, Adobe, LiveRamp, Nielsen, Salesforce, and Snowflake (unifiedid.com, as-of 2026). Recent integration announcements include Perion (March 2025), AppsFlyer (May 2025), Treasure Data (September 2025), Hightouch (October–November 2025), and Databricks (November 2025) (unifiedid.com, 2025 press releases).
In 2025, unified IDs and Data Clean Rooms led companies' investment in cookie alternatives; data clean rooms and unified IDs were each cited by 51% of respondents as commonly used addressability solutions in IAB Europe's 2025 survey (spyro-soft-adtech.com citing IAB Europe, 2026-01-27). (as-of 2025)
UID2 and RampID are described as having the strongest US demand-side adoption, while ID5 has a larger footprint in Europe (newormedia.com, 2026-09-25). (as-of 2026-09-25)
Market consolidation: Newor Media (2026-09-25) reports that the universal ID market "fragmented instead of consolidating," with no single ID matching third-party cookie coverage. FlexyConsent (2026-05-19) describes the category as having "consolidated meaningfully" from its 2021 peak with many early identifiers exiting. These may describe different dimensions — the number of active providers (fragmented) versus concentration of volume among survivors (consolidated).
Retail media and ecommerce applications
UID2 enables retail advertisers to activate first-party CRM audiences (hashed customer emails) for off-site targeting through DSPs that read UID2 tokens. The following figures come from vendor case studies and represent self-reported outcomes:
- Target Australia paired UID2 lookalike audiences with first-party CRM seeds, reporting 66% higher conversion rate and 36% lower cost per action versus third-party targeting (thetradedesk.com case study, date unknown). (as-of unknown) OMD Australia stated: "Leveraging UID2 allows us to stop an over-reliance on third-party data and focus on utilizing Target's first-party data."
- The Washington Post reportedly saw CPMs 3–4 times higher for authenticated users carrying UID2 tokens; Dotdash Meredith reported similar early A/B test results (smartmarketer.net, 2026-08-31). (as-of 2026-08-31)
Earlier APAC case studies from 2024 (The Current, 2024-06-25 — a Trade Desk–owned outlet):
- FairPrice Group (Singapore): 33% lower CPA, 23% lower CPM, 1M more potential consumers reached vs device-ID audiences.
- Luxury Escapes (Australia): 276% higher conversion rate, 4.75× ROAS, 78.3% lower CPA vs pixel-based audience.
- Unilever Thailand: 30% lower CPCV, 1.9× CTR of second-party data targeting.
Competitive landscape
UID2's principal competitors in the universal identity space are RampID (LiveRamp), ID5, Google PAIR, and Amazon Publisher Direct.
FlexyConsent (2026-05-19) describes RampID as "the most widely deployed universal ID across the major programmatic supply ecosystem," using a persistent graph linking devices, sessions, and cross-platform exposure. A key structural difference: each RampID is encoded per partner, so two companies cannot join on it directly — LiveRamp's translation endpoint converts between encodings. UID2, by contrast, is a consistent raw value across participants (encrypted into a rotating token for the bidstream), meaning participants who both read UID2 share the same underlying identifier (gsdsi.com, 2026-10-01).
ID5 can operate without a direct hashed-email input, which gives it different consent characteristics; it is widely integrated across European SSPs, DSPs, and measurement vendors (flexyconsent.com, 2026-05-19).
A Prebid user-id module writing user.eids does not carry those IDs to Google's TAM or Open Bidding paths (rtblint.org, 2026-09-27). Many 2026 advertising programmes use a hybrid of universal IDs and Data Clean Rooms; clean rooms are increasingly better fits for sensitive-audience or regulated-vertical campaigns (flexyconsent.com, 2026-05-19).
RampID deployment leadership: FlexyConsent (May 2026) calls RampID "the most widely deployed" universal ID in the programmatic supply ecosystem. Smart Marketer and Newor Media (both 2026) treat UID2 and RampID as co-equal in US demand-side adoption, without crowning either as dominant. Both frames may be true simultaneously — RampID may lead in SSP/supply breadth while UID2 leads in DSP (Trade Desk ecosystem) demand concentration.
Cookie deprecation context
Google reversed its plan to remove third-party cookies from Chrome in April 2025 (smartmarketer.net, 2026-08-31), while Safari and Firefox have blocked third-party cookies for years. Chrome holds roughly 65% global browser share (smartmarketer.net, 2026-08-31). (as-of 2026-08-31) Apple continued to restrict device fingerprinting with Safari 26 and iOS 26 (spyro-soft-adtech.com, 2026-01-27). The iOS 27 Safari block on uidapi.com (see Technical flow above) is the most significant 2026 development affecting UID2 specifically.
Privacy and regulatory
Users can opt out of UID2-based targeted advertising at any time through the Transparency and Control Portal (transparentadvertising.com). After opt-out, UID2 stores only a hashed, opaque value (not reversible to DII); UID2 components otherwise do not store any DII (unifiedid.com FAQs, undated). DSPs must configure a webhook for opt-out traffic and are advised to store opt-out signals indefinitely (unifiedid.com FAQs, undated). UID2 operates a single global consumer opt-out; by contrast, RampID runs separate opt-out mechanisms for email, mobile ID, third-party cookie, and cross-screen measurement (gsdsi.com, 2026-10-01).
Processing Protected Health Information (PHI, as defined under HIPAA) to generate UID2s is prohibited, even with marketing consent (unifiedid.com FAQs, undated).
The European Data Protection Board found that hashed emails are pseudonymised personal data under GDPR; the FTC issued 2024 guidance stating that hashing does not make data anonymous (emparrot.com, 2026-06-24 — an email-privacy vendor with a commercial interest in this framing).
Two class action lawsuits were filed in California in March 2025 (Central District and Northern District) alleging UID2 collects PII without adequate consent to build cross-site user profiles; cases were still untested as of mid-2026 (captaincompliance.com, 2026).
The Electronic Frontier Foundation (EFF) characterised UID2 as "a step backward for user privacy," arguing it tracks real people (not browsers) across devices and could push sites toward demanding email logins as a condition of access ("trackerwalls") (EFF, 2021).
EUID (European Unified ID) is the GDPR-compliant European variant. It uses the same open-source codebase as UID2 but operates under a separate namespace requiring separate contracts, and mandates explicit opt-in consent at each publisher (unifiedid.com FAQs, undated; emparrot.com, 2026-06-24). Access to EUID does not grant UID2 access.
Key terms
| Term | Meaning |
|---|---|
| DII | Directly identifying information — hashed email or phone number that seeds the UID2 |
| Raw UID2 | The persistent hashed identifier; rotates ~annually via salt bucket changes |
| UID2 Token | The encrypted, short-lived form of a raw UID2 that travels in the ad bidstream |
| Public Operator | An organisation (currently The Trade Desk) that runs the UID2 Operator Service on behalf of participants |
| Private Operator | A participant that runs the UID2 Operator Service within its own infrastructure |
| EUID | European Unified ID — European variant; mandatory opt-in, separate namespace |
| Salt bucket | A grouping of raw UID2s; rotated periodically to prevent fingerprinting via the raw hash |
Benchmarks and adoption figures (as-of 2026-10-19)
| Metric | Figure | Source | Confidence |
|---|---|---|---|
| Companies implementing UID2 | 300+ (as-of 2026-08-31) | Smart Marketer (Landbase data) | Low — single vendor-cited source |
| Washington Post eCPM lift (authenticated) | 3–4× (as-of 2026-08-31) | Smart Marketer (self-reported) | Low — self-reported |
| Target Australia: CVR lift | +66% (date unknown) | TTD case study (self-reported) | Low — vendor case study |
| Target Australia: CPA reduction | -36% (date unknown) | TTD case study (self-reported) | Low — vendor case study |
| iOS 27 WebKit block date | 2026-10 | Official UID2 docs | High |
| IAB Europe: unified IDs adoption | 51% of respondents (as-of 2025) | IAB Europe 2025 survey via spyro-soft | Med |
| Chrome global browser share | ~65% (as-of 2026-08-31) | Smart Marketer | Med |
What practitioners report
Reddit signal was unavailable for this run (network access blocked in research environment). YouTube transcripts were not available (Apify not accessible). Primary web and registry sources provided the bulk of findings. Practitioner perspectives and Reddit debate to be added in future runs.