Data.cids

Field facts

Path

user.data.cids, app.content.data.cids, dooh.content.data.cids, site.content.data.cids

Object

Data

Type

string array

Requirement

Optional

Added

OpenRTB 2.6-202505

Spec section

3.2.21

How it is used

A content data platform assigns its own ID to each piece of content it catalogs. Passing that ID lets a buyer's contextual vendor look up its classification without the exchange relaying the metadata. Name the platform in name with a domain it owns, and use one Data entry per platform. The field replaces an earlier community extension. Keep the publisher's own content ID in Content.id.

Example

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

{
  "id": "req-1",
  "user": {
    "data": [
      {
        "cids": [
          "vendor-example_c73g5jq96mwso4d8"
        ]
      }
    ]
  }
}

Common mistakes

• Putting genre or category values here. Those belong in Content.genres and Content.cat.
• Putting a third-party content ID in Content.id, which is reserved for the publisher's own ID.

Version history

Added in OpenRTB 2.6-202505, and present in the latest snapshot. The table shows how each version's spec text types the field.

Related fields

• Data.name
• Content.id
• Content.data

Other Data fields

• ext
• id
• name
• segment