BidSwitch OpenRTB Differences¶
Even though the BidSwitch Real-time Bidding Protocol v5.3 is based on the latest OpenRTB Protocol Specification V2.5, differences exist between the two. Those differences are outlined in this section.
Bid Request Differences¶
The BidSwitch protocol differs in the following ways.
bcataccepts additional non-IAB Blocked Advertiser Categories.native.requestis an object. The OpenRTB version uses a string and passes a serialized object.user.buyeruiduses a lowercase IDFA, or Android ID for in-app traffic, if the user cookie ID is not known.
Bid Response Differences¶
The BidSwitch protocol differs in the following ways.
ext.protocolis required.seatbid.bidarray can have a maximum of two elements.seatbid.seatis required ifwseatis present in the bid request.seatbid.bid.admmay or may not contain the win price macro depending on the protocol version, bid request parameters, andnurlfield usage. See the 5.x Updating Overview section for details. The field may not be used for submitting VAST or DAAST documents.seatbid.bid.iurlis required for banner bids.seatbid.bid.priceis required.One of either
seatbid.bid.adidorseatbid.bid.cridis required.seatbid.bid.adomainis required.seatbid.bid.cidis required for a number of Suppliers.seatbid.bid.catis required for a number of Suppliers.seatbid.bid.ext.advertiser_nameis required for a number of Suppliers.seatbid.bid.ext.agency_nameis required for a number of Suppliers.seatbid.bid.ext.durationis required for a number of Suppliers.seatbid.bid.ext.vast_urlmay be used to supply the VAST document in any video bid. It is required to be used for video bids if thevideo.ext.vast_url_rqbid request field is set to1. The VAST document should not contain win price macrosseatbid.bid.nurlShould NOT be used for submitting creative markup, and it cannot contain a win price macro if
seatbid.bid.admcontains one.May be used to supply the VAST document if the
video.ext.vast_url_rqbid request field is set to1. The VAST document should NOT contain win price macros.