UID.id
The identifier itself, as a string in the format its source defines. The table does not mark it required, but a UID without an id carries nothing, and RTBlint reports it.
Field facts
- Path
user.eids.uids.id- Object
- UID
- Type
- string
- Requirement
- Optional
- Added
- OpenRTB 2.6-202204
- Spec section
- 3.2.28
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"user": {
"eids": [
{
"uids": [
{
"id": "XY1000000000000EXAMPLE"
}
]
}
]
}
}Common mistakes
- Sending a raw email address or phone number. Identity providers expect their own token or hash format, and raw personal data does not belong in a bid request.
- Sending an empty string as a placeholder.
Version history
Added in OpenRTB 2.6-202204, and present in the latest snapshot. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.6-202204 | Added in the first 2.6 release, published without a structured text archive; the 2.6-202210 republication is the first tagged text. | ||
| 2.6-202210 to 2.6-202606 | string | No | No |
Related fields
Other UID fields
For a walkthrough of the whole object, read User identity and EIDs.