Starting today, Google’s OpenRTB implementation will be updated to only include fields and messages for the latest supported version, OpenRTB 2.5 . This will affect the OpenRTB protocol and any APIs or tools used to configure bidder endpoints.
OpenRTB protocol changes
As a result of supporting only the latest version, the following fields are deprecated and will no longer be populated:
BidRequest.imp[].banner.hmax
BidRequest.imp[].banner.hmin
BidRequest.imp[].banner.wmax
BidRequest.imp[].banner.wmin
Additionally, the following fields may now be populated for all bidders:
BidRequest.device.ext.user_agent_data
BidRequest.device.geo.accuracy
BidRequest.device.geo.utcoffset
BidRequest.imp[].banner.api
: This will support the value MRAID_3
.
BidRequest.imp[].banner.format
BidRequest.imp[].banner.vcm
BidRequest.imp[].metric
BidRequest.imp[].native.api
: This will support the value MRAID_3
.
BidRequest.imp[].video.api
: This will support the value MRAID_3
.
BidRequest.imp[].video.companionad.api
BidRequest.imp[].video.companionad.format
BidRequest.imp[].video.companionad.vcm
BidRequest.imp[].video.linearity
BidRequest.imp[].video.maxduration
BidRequest.imp[].video.placement
BidRequest.imp[].video.playbackend
BidRequest.imp[].video.skip
BidRequest.site.mobile
BidRequest.test
BidRequest.wlang
If a newer OpenRTB specification is published, Google may upgrade the current supported version to match it. Previously deprecated fields that are removed from the specification will also be removed from the protocol. Non-deprecated fields that are removed will be marked as deprecated in the protocol, and eventually removed following a brief deprecation period.
Authorized Buyers Real-time Bidding API changes
The behavior of the bidders.endpoints
resource will change. The following enum values for bidProtocol
will be deprecated:
OPENRTB_2_2
OPENRTB_2_3
OPENRTB_PROTOBUF_2_3
OPENRTB_2_4
OPENRTB_PROTOBUF_2_4
OPENRTB_2_5
OPENRTB_PROTOBUF_2_5
New enum values for bidProtocol
will be added to represent the latest supported OpenRTB version in either JSON or Protobuf formats:
OPENRTB_JSON
OPENRTB_PROTOBUF
If you have existing endpoints with their bidProtocol
set to any of the deprecated values above, they will automatically be migrated to either OPENRTB_JSON
or OPENRTB_PROTOBUF
depending on the format specified by the original value. Additionally, any modifications to your endpoints that would set bidProtocol to the deprecated values will instead set it to OPENRTB_JSON
or OPENRTB_PROTOBUF
.
Feel free to reach out to us via the Authorized Buyers API support forum with any feedback or questions you may have related to these changes.
- Mark Saniscalchi, Authorized Buyers Developer Relations