Bid.mtype
The type of markup in this bid, so the exchange can match it to the right media object on the impression: 1 banner, 2 video, 3 audio, 4 native. Added in 2.6.
Field facts
- Path
seatbid.bid.mtype- Object
- Bid
- Type
- integer
- Requirement
- Optional
- Added
- OpenRTB 2.6-202204
- Spec section
- 4.2.3
How it is used
Impressions often offer more than one format, such as banner and video together. Without mtype the exchange has to inspect the markup to guess the format. The value must name a media object the impression actually offered.
Allowed values
1, 2, 3, 4.
Example
Where the field sits in a payload, with everything else left out:
{
"seatbid": [
{
"bid": [
{
"mtype": 2
}
]
}
]
}Common mistakes
- Leaving it out on a 2.6 bid that carries
adm(openrtb.bid.mtype_missing). - A banner bid on a video-only impression (
openrtb.bid.mtype_not_offered). - A constant
mtypein a bidder that serves several formats, so native JSON goes out labeled as a banner.
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 Bid fields
adidadmadomainapiapisattrbundleburlcatcattaxcidcriddealiddurexpexthhratioidimpidiurllangblanguagelurlnurlpriceprotocolqagmediaratingslotinpodtacticwwratio
For a walkthrough of the whole object, read Bid response anatomy.