Universal IDs: UID2, ID5, RampID
Shared advertising IDs derived from login email so ad partners can match people without cookies.
In one line
Can give you a shared ad ID based on your login email, with no cookie
Shared advertising IDs derived from login email so ad partners can match people without cookies.
A publisher sends a hashed or encrypted email at login; the ID vendor returns a token that ad platforms accept. UID2 (The Trade Desk, open source), ID5 and LiveRamp RampID let a person be recognised across sites and apps whenever they log in.
What it can and can't do
What the user does: You sign in or give your email on a site that joins the system
It can
- Turn your email into a shared ad ID
- Let many ad partners recognize you with the same ID
- Keep recognizing you after you clear cookies
It cannot
- Create an ID without you giving an email or logging in
- Reach you on sites that do not take part
- Stay the same if you use a different email
- Give out your plain email; it uses a scrambled version, and some systems let you opt out
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | Server and script based; independent of browser privacy features once the person signs in |
| Edge | Supported | 1 | Not listed | Server and script based; independent of browser privacy features once the person signs in |
| Firefox | Supported | 1 | 2004-11-09 | Server and script based; independent of browser privacy features once the person signs in |
| Safari | Supported | 1 | 2003-06-23 | Server and script based; independent of browser privacy features once the person signs in |
| Safari on iPhone | Supported | 1 | 2007-06-29 | Server and script based; independent of browser privacy features once the person signs in |
| Chrome on Android | Supported | 1 | Not listed | Server and script based; independent of browser privacy features once the person signs in |
| Samsung Internet | Supported | 1 | 2013-04-27 | Server and script based; independent of browser privacy features once the person signs in |
How a site asks for it
| API | Publisher JS SDK (UID2 SDK, ID5 API, LiveRamp ATS) and server APIs |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Tokens rotate; UID2 advertising tokens are short lived with refresh tokens valid for days to weeks (verify per vendor docs) |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Opaque token derived from email or phone
Shape: string
How often: refreshed on sign in and periodically
No individual data fields. The signal is the access itself.
Technical limits
- Requires a user supplied email or phone
- Opt-out portals exist (for example UID2 transparency and controls at transparentadvertising.org)
- Raw email is not in the token but hashing is reversible by dictionary attack on guessable emails
The story
What it is
Shared ad IDs built from your login email so ad partners can match you without cookies.
For you
You log in to a site with your email. The site may turn it into a token that ad partners accept. You do not see it, and it can follow you across sites and apps each time you log in.
For makers
Cookies are fading, so ad buyers want a stable login based ID. A publisher sends a hashed email, gets a token and sells it to ad buyers. Logged in audiences earn higher ad prices.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A news site shares a UID2 token at login so advertisers can find you again on a streaming service. | UID2, The Washington Post |
| media | A streaming service uses a login email token to match viewers to ads on TV and phones. | Hulu, Roku |
| games | A game portal with logins sends a token so ad buyers can reach the same player on web and mobile. | LiveRamp RampID |
| analytics | An advertiser measures reach across publishers using one ID, instead of counting the same person twice. | ID5, LiveRamp |
| shopping | A retailer matches its customer list to an ID graph, to find them on other sites. | Walmart Connect |
| security | People can opt out on the vendor site, but few know of it. | None named |
Risks
- Follows you across sites and apps
- Hard to opt out of
What the platform says
- The Trade Desk: Unified ID 2.0. UID2 is pitched as an open, email based ID for ad targeting after cookies, with opt out for people.
Good uses and abuse
Legitimate uses
- Publisher monetisation on cookieless traffic
- Cross device frequency control
Known abuse
- Stable lifetime identifier tied to a real email
- Matching offline data to online browsing
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025-04, Chrome 135: Google confirmed third-party cookies stay, so email based IDs complement rather than replace cookies
Related capabilities
Related
- Hashed email as identity. Can recognize you across sites by a scrambled version of your email
- Cross device identity linking. Can recognize you as one person across your phone, laptop and tablet when you sign in
Sources
How well checked: Based on official documentation.