Protocol Release Notes¶
24 January, 2024¶
Added support for multiple fields as part of supporting Protected Audience API:
Response Ext Object, new fields added:
ext.igbid
ext.igbid.id
ext.igbid.igbuyer
ext.igbid.ig_nurl
ext.igbid.igbuyer.origin
ext.igbid.igbuyer.buyerdata
ext.igbid.igbuyer.seat
8 November, 2023¶
Added support for the device.ext.cdep
field, see the Device Object Properties section for details
13 July, 2023¶
Added support for the seatbid.bid.lurl
field, see the Response Bid Object section for details
22nd May 2023¶
Changed supported values for the video.plcmt
field, see the Video Object section for details
26 April 2023¶
Added support for the data.ext.segtax
bid request field, see the
Ext Object for more details.
18th April 2023¶
Important
BidSwitch is in the process of adding support for the following fields during Q2 2023. The IAB is actively making changes to the Open RTB 2.6 specification and supporting these keeps BidSwitch’s support of Open RTB 2.6 current.
You can follow the IAB changes here, and if any new changes are made BidSwitch will also support those. https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md
You can find an overview of all changes in the 5.7 Upgrade Guide section.
Regulation Object new fields added:
regs.gpp
regs.gpp_sid
Impression Object new fields added:
imp.qty
imp.dt
imp.refresh
imp.qty.multiplier
imp.qty.sourcetype
imp.qty.vendor
imp.refresh.refsettings
imp.refresh.count
’imp.refresh.refsettings.reftype
imp.refresh.refsettings.minint
site.inventorypartnername
moved fromsite.ext
to the root Site object
app.inventorypartnername
moved to the root App object
device.ppi
field added
DOOH Object moved to the Bid Request 5.7 object root with the following fields:
dooh.id
dooh.name
dooh.venuetype
dooh.venuetypetax
dooh.publisher
dooh.domain
dooh.keywords
dooh.content
video.placement
is deprecated and replaced withvideo.plcmt
11th April 2023¶
Added support for the imp.ext.gpid
field, see the Impression Object section for details
15th March 2023¶
Added support for the imp.ext.skadn.productpage
bid request field and:
- seatbid.bid.ext.skadn.productpageid
- seatbid.bid.ext.skadn.sourceidentifier
bid response fields, see SkAdNetwork Extension and SkAdNetwork Extension sections for more details
28th September 2022¶
Added the Google DV360 specific request field ext.purch
, see the Ext Object section for more details
19th September 2022¶
Initial release BidSwitch Protocol 1.1 to support Open RTB 2.6.
An overview of changes can be found in the 5.7 Upgrade Guide section.
For release notes for all previous versions, see the Protocol Release Notes section
Important
Two new fields in this version of the Open RTB protocol require BidSwitch and its partners to align on their understanding of how they should work when used in real trading.
The
video.mincpmpersec
, this sets the minimum CPM per second as the price floor for the “dynamic” portion of a video ad pod, relative to the duration of bids an advertiser may submit. We need to come to a common understanding of how this should be calculated so that bid and bidfloor processing expectations are the same for all partners. See the Video Object section for details.The format object introduces ratios with
hration
andwratio
, see the Format Object section for full details. BidSwitch offers size targeting as part of BidSwitch Targeting Groups but ratios are not accounted for this in this yet. If you intend to use ratios, please speak with you Technical Account Manager so we can align on expected usage of this field.