DOOH.venuetypetax
Names the venue taxonomy that DOOH.venuetype values come from, using the AdCOM DOOH Venue Taxonomies list. Defaults to 1, OpenOOH Venue Taxonomy 1.0.
Field facts
- Path
dooh.venuetypetax- Object
- DOOH
- Type
- integer
- Default
1- Requirement
- Optional
- Added
- OpenRTB 2.6-202211
- Values
- AdCOM list DOOH Venue Taxonomies
- Spec section
- 3.2.32
How it is used
Other values are 0 for the deprecated AdCOM venue types, 2 for the DPAA device venue types, 3 for the DMI venue categories 1.1, 4 for the OMA taxonomy of January 2022, and 5 for OpenOOH 1.1. Send it explicitly when you use OpenOOH 1.1, because the default still means 1.0.
Allowed values
| Value | Meaning |
|---|---|
0 | AdCOM DOOH Venue Types (deprecated): The venue type list AdCOM used to define itself; deprecated, so avoid it in new integrations. |
1 | OpenOOH Venue Taxonomy 1.0: Version 1.0 of the OpenOOH venue taxonomy; the default when venuetypetax is absent. |
2 | DPAA Device Venue Types: The venue types of the Digital Place-based Advertising Association; confirm with the seller which version they use. |
3 | DMI Categorization of Venues 1.1: Version 1.1 of the DMI venue categorization for digital out-of-home. |
4 | OMA taxonomy, January 2022: The Outdoor Media Association venue taxonomy from January 2022, used in the Australian market. |
5 | OpenOOH Venue Taxonomy 1.1: Version 1.1 of the OpenOOH venue taxonomy. |
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"dooh": {
"venuetypetax": 1
}
}Common mistakes
- Omitting it while sending venue names from a taxonomy other than OpenOOH 1.0.
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 | integer, default 1 | No | No |
Related fields
Other DOOH fields
For a walkthrough of the whole object, read DOOH in OpenRTB.