UID.atype

The type of agent the ID comes from, as an integer from the AdCOM Agent Types list. 1 means an ID tied to one browser or device, such as a cookie, 2 an in-app device ID, and 3 a person-based ID shared across devices.

CurrentintegerOptionalSince 2.6-202204

Field facts

Path: user.eids.uids.atype
Object: UID
Type: integer
Requirement: Optional
Added: OpenRTB 2.6-202204
Values: AdCOM list Agent Types
Spec section: 3.2.28

How it is used

Optional in the table but strongly advised: many DSPs keep app IDs and browser IDs in separate graphs and cannot resolve an ID without knowing which kind it is. Values 500 and above are vendor-specific.

Allowed values

Value	Meaning
`1`	Browser or device: An ID tied to one browser or device, whether cookie-based, probabilistic or otherwise.
`2`	In-app: An ID from app traffic, usually a privacy-compliant form of the device advertising ID.
`3`	Person-based: An ID meant to identify the same person across devices.
`500+`	Vendor-specific codes: Vendor-specific agent types agreed between the parties.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "user": {
    "eids": [
      {
        "uids": [
          {
            "atype": 1
          }
        ]
      }
    ]
  }
}

Common mistakes

Omitting atype, which leaves some DSPs unable to use an otherwise valid ID.
Sending it as a string such as "1".

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	integer	No	No

Related fields

Other UID fields

For a walkthrough of the whole object, read User identity and EIDs.