OpenRTB enumerated lists
The integer codes an OpenRTB bid request uses for device type, connection type, video placement, playback, API frameworks, creative attributes, protocols, position, and every other AdCOM list: 42 lists in all, each with its own page explaining the values.
Where the lists live now
As of OpenRTB 2.6, the request-side enumerated lists are kept in the AdCOM 1.0 specification (no-bid and loss reason codes live in the OpenRTB 3.0 document) so they can change without a new OpenRTB release. Field tables in 2.6 say things like "Refer to List: Device Types in AdCOM 1.0". In OpenRTB 2.5 and earlier the same lists sat in section 5 of the spec itself, so older integration docs cite section numbers (5.21 Device Types, 5.9 Video Placement Types) for values that are now AdCOM lists. The values below are the current AdCOM lists the RTBlint validator checks. See specification versions for what changed when.
Video and audio
Creative subtypes (audio and video)
Used by imp.audio.protocols, seatbid.bid.protocol, imp.video.protocols.
Playback methods
Used by imp.video.playbackmethod.
| Value | Name |
|---|---|
1 | Initiates without any specific user interaction with Sound On |
2 | Initiates without any specific user interaction Sound Off by Default |
3 | Initiates on Click with Sound On |
4 | Initiates on Mouse-Over or cursor over with Sound On |
5 | Initiates on Entering Viewport or scrolling into view with Sound On |
6 | Initiates on Entering Viewport or scrolling into view with Sound Off by Default |
7 | Continuous Playback |
8 | Initiated by user pausing content, Sound on |
9 | Initiated by user pausing content, Sound off |
10 | Initiated by idling |
11 | Initiated by idling |
Feed types
Used by imp.audio.feed.
Volume normalization modes
Used by imp.audio.nvol.
| Value | Name |
|---|---|
0 | None |
1 | Ad Volume Average Normalized to Content |
2 | Ad Volume Peak Normalized to Content |
3 | Ad Loudness Normalized to Content |
4 | Custom Volume Normalization |
Pod deduplication
Used by imp.video.poddedupe.
Pod sequence
Used by imp.audio.podseq.
| Value | Name |
|---|---|
-1 | Last pod in the content stream |
0 | Any pod in the content stream |
1 | First pod in the content stream |
Ad placement and creative
API frameworks
Used by imp.audio.api, imp.banner.api, seatbid.bid.apis, imp.native.api, imp.video.api.
Creative attributes
Used by imp.audio.battr, imp.banner.battr, seatbid.bid.attr, imp.native.battr, imp.video.battr.
| Value | Name |
|---|---|
1 | Audio Ad (Autoplay) |
2 | Audio Ad (User Initiated) |
3 | Expandable (Automatic) |
4 | Expandable (User Initiated - Click) |
5 | Expandable (User Initiated - Rollover) |
6 | In-Banner Video Ad (Autoplay) |
7 | In-Banner Video Ad (User Initiated) |
8 | Pop (e.g., Over, Under, or Upon Exit) |
9 | Provocative or Suggestive Imagery |
10 | Shaky, Flashing, Flickering, Extreme Animation, Smileys |
11 | Surveys |
12 | Text Only |
13 | User Interactive (e.g., Embedded Games) |
14 | Windows Dialog or Alert Style |
15 | Has Audio On/Off Button |
16 | Ad Provides Skip Button |
17 | Adobe Flash |
18 | Responsive, sizeless or fluid |
19 | Contains advertiser QR code |
20 | Supports alpha channel transparency |
21 | Static visual |
22 | Limited motion (cinemagraph) |
23 | Full-motion video |
500+ | Vendor-specific codes |
Expandable directions
Used by imp.banner.expdir.
| Value | Name |
|---|---|
1 | Left |
2 | Right |
3 | Up |
4 | Down |
5 | Full Screen |
6 | Resize or minimize |
Device, location, and connection
Device types
Used by device.devicetype.
Operating systems
| Value | Name |
|---|---|
0 | Other Not Listed |
1 | 3DS System Software |
2 | Android |
3 | Apple TV Software |
4 | Asha |
5 | Bada |
6 | BlackBerry |
7 | BREW |
8 | ChromeOS |
9 | Darwin |
10 | FireOS |
11 | FirefoxOS |
12 | HelenOS |
13 | iOS |
14 | Linux |
15 | MacOS |
16 | MeeGo |
17 | MorphOS |
18 | NetBSD |
19 | NucleusPLUS |
20 | PS Vita System Software |
21 | PS3 System Software |
22 | PS4 Software |
23 | PSP System Software |
24 | Symbian |
25 | Tizen |
26 | WatchOS |
27 | WebOS |
28 | Windows |
500+ | Vendor-specific codes |
Location types
Used by device.geo.type.
IP location services
Used by device.geo.ipservice.
| Value | Name |
|---|---|
1 | ip2location |
2 | Neustar (Quova) |
3 | MaxMind |
4 | NetAcuity (Digital Element) |
511 | 51Degrees (High Confidence) |
512 | 51Degrees (Medium Confidence) |
User-Agent source
Used by device.sua.source.
| Value | Name |
|---|---|
0 | Unspecified or unknown |
1 | Client Hints, low entropy only |
2 | Client Hints, with high entropy |
3 | Parsed from the User-Agent header |
Content and taxonomies
Content contexts
Used by app.content.context.
Media ratings
Used by seatbid.bid.qagmediarating, app.content.qagmediarating.
| Value | Name |
|---|---|
1 | All Audiences |
2 | Everyone Over Age 12 |
3 | Mature Audiences |
Category taxonomies
Used by app.cattax, seatbid.bid.cattax, cattax, app.content.cattax, app.content.gtax, app.content.producer.cattax, app.publisher.cattax, site.cattax.
| Value | Name |
|---|---|
1 | IAB Tech Lab Content Category Taxonomy 1.0 |
2 | IAB Tech Lab Content Category Taxonomy 2.0 |
3 | IAB Tech Lab Ad Product Taxonomy 1.0 |
4 | IAB Tech Lab Audience Taxonomy 1.1 |
5 | IAB Tech Lab Content Taxonomy 2.1 |
6 | IAB Tech Lab Content Taxonomy 2.2 |
7 | IAB Tech Lab Content Taxonomy 3.0 |
8 | IAB Tech Lab Ad Product Taxonomy 2.0 |
9 | IAB Tech Lab Content Taxonomy 3.1 |
500+ | Vendor-specific codes |
DOOH venue taxonomies
Used by dooh.venuetypetax.
| Value | Name |
|---|---|
0 | AdCOM DOOH Venue Types (deprecated) |
1 | OpenOOH Venue Taxonomy 1.0 |
2 | DPAA Device Venue Types |
3 | DMI Categorization of Venues 1.1 |
4 | OMA taxonomy, January 2022 |
5 | OpenOOH Venue Taxonomy 1.1 |
DOOH multiplier measurement source types
Used by imp.qty.sourcetype.
| Value | Name |
|---|---|
0 | Unknown |
1 | Measurement Vendor Provided |
2 | Publisher Provided |
3 | Exchange Provided |
Identity
ID match methods
Used by user.eids.mm.
Agent types
Used by user.eids.uids.atype.
| Value | Name |
|---|---|
1 | Browser or device |
2 | In-app |
3 | Person-based |
500+ | Vendor-specific codes |
Lists used by OpenRTB 3.0 and AdCOM objects
Display context types
| Value | Name |
|---|---|
10 | Content-centric |
11 | Article content |
12 | Video content |
13 | Audio content |
14 | Image content |
15 | User-generated content |
20 | Social-centric |
21 | |
22 | Chat or instant messaging |
30 | Product context |
31 | App store or marketplace |
32 | Product reviews |
500+ | Vendor-specific codes |
Display placement types
| Value | Name |
|---|---|
1 | In-feed |
2 | In the content unit |
3 | Outside the core content |
4 | Recommendation widget |
500+ | Vendor-specific codes |
Creative subtypes for display
| Value | Name |
|---|---|
1 | HTML |
2 | AMPHTML |
3 | Structured Image Object |
4 | Structured Native Object |
Native data asset types
| Value | Name |
|---|---|
1 | sponsored |
2 | desc |
3 | rating |
4 | likes |
5 | downloads |
6 | price |
7 | saleprice |
8 | phone |
9 | address |
10 | desc2 |
11 | displayurl |
12 | ctatext |
500+ | Vendor-specific codes |
Native image asset types
| Value | Name |
|---|---|
1 | Icon |
3 | Main |
500+ | Vendor-specific codes |
Event types
| Value | Name |
|---|---|
1 | loaded |
2 | impression |
3 | viewable-mrc50 |
4 | viewable-mrc100 |
5 | viewable-video50 |
500+ | Vendor-specific codes |
Event tracking methods
| Value | Name |
|---|---|
1 | Image-Pixel |
2 | JavaScript |
500+ | Vendor-specific codes |
Click types
| Value | Name |
|---|---|
0 | Non-Clickable |
1 | Clickable, details unknown |
2 | Clickable, embedded browser or webview |
3 | Clickable, native browser |
500+ | Vendor-specific codes |
Audit status codes
| Value | Name |
|---|---|
1 | Pending Audit |
2 | Pre-Approved |
3 | Approved |
4 | Denied |
5 | Changed; Resubmission Requested |
6 | Expired |
500+ | Vendor-specific codes |
Size units
| Value | Name |
|---|---|
1 | Device independent pixels (DIPS) |
2 | Inches |
3 | Centimeters |
Lists defined in OpenRTB itself
Auction type (at)
BidRequest.at, integer, default 2. Defined in the OpenRTB spec, not AdCOM.
| Value | Name | Meaning |
|---|---|---|
1 | First Price | Winner pays what they bid. |
2 | Second Price Plus | Winner pays just above the second-highest bid; the spec default. |
3 | Fixed price (deals only) | On Deal.at, the deal's bidfloor is the agreed price. |
500+ | Exchange-specific | Custom auction types agreed with buyers. |
Legacy video placement (placement)
Video.placement used OpenRTB 2.5 list 5.9. It is deprecated since 2.6-202303 in favor of Video.plcmt, whose list is on the plcmt page. The two lists do not map one to one; the placement versus plcmt guide explains the migration.
| Value | Name | Meaning |
|---|---|---|
1 | In-Stream | Pre-, mid-, post-roll against requested video content. |
2 | In-Banner | Video inside display banner inventory. |
3 | In-Article | Player loading between paragraphs of editorial content. |
4 | In-Feed | Inside content, social, or product feeds. |
5 | Interstitial/Slider/Floating | Always on screen while displayed. |
No-bid and loss reasons
BidResponse.nbr uses the no-bid reason codes, and the loss notice macro carries loss reason codes. Each code has its own page.
Questions people ask
Where are OpenRTB enum values defined?
Since OpenRTB 2.6, the request-side enumerated lists live in the AdCOM 1.0 specification, referenced from the 2.6 field tables as AdCOM lists; no-bid and loss reason codes live in the OpenRTB 3.0 document. In OpenRTB 2.5 and earlier the same lists were section 5 of the OpenRTB document itself. Most values match across the two homes; AdCOM has since added values the 2.5 lists never had.
What do enum values of 500 and above mean?
Where a list says so (auction type, API frameworks, creative attributes, no-bid reasons, and others), values 500 and greater are reserved for exchange-specific or vendor-specific use. They are only meaningful to partners who agreed on them beforehand, so a validator can accept them but cannot tell you what they mean.
Is video.placement still valid in OpenRTB 2.6?
It parses, but it was deprecated in the 2.6-202303 update in favor of video.plcmt, which uses a different list. Send plcmt; keep placement only for partners that have not migrated, and never assume the two lists share meanings.
Validate the enums you send
On OpenRTB 2.6 snapshots, RTBlint checks every integer field that points to an AdCOM list against the values above and reports anything else as openrtb.value.invalid. Paste a request into the tester to try it.