BidRequest.dooh

A DOOH object describing a digital out-of-home screen or group of screens. Added in 2.6-202211; a request that carries it must not also carry BidRequest.site or BidRequest.app.

CurrentobjectOptionalSince 2.6-202211

Field facts

Path: dooh
Object: BidRequest
Type: object
Requirement: Optional
Added: OpenRTB 2.6-202211
Spec section: 3.2.1

How it is used

Out-of-home inventory is often sold per play to an audience of many viewers, so these requests usually pair dooh with Imp.qty to state how many impressions one play counts as. The venue type fields on the DOOH object tell buyers what kind of location the screen is in.

Example

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

{
  "id": "req-1",
  "dooh": {
    "id": "screens-airport-east",
    "name": "Airport arrivals hall",
    "publisher": {
      "id": "pub-88"
    }
  }
}

Common mistakes

Describing a screen network with site or app because an older pipeline had no dooh. From 2.6-202211, use the dedicated object.
Sending dooh alongside site or app (openrtb.fields.mutually_exclusive).

Version history

Added in OpenRTB 2.6-202211, 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-202211 to 2.6-202606	object	No	No

Related fields

Other BidRequest fields

For a walkthrough of the whole object, read Bid request anatomy.