DV360 OpenRTB Specification

Page Summary

outlined_flag

• Display & Video 360 (DV360) implements the OpenRTB 2.6 specification with specific nuances and requires bid requests to comply with its unique OpenRTB specification.

• Bid requests are HTTP POST requests containing a bid request object, with responses being either HTTP 200 for a successful bid or HTTP 204 for a no-bid.

• The DV360 OpenRTB specification details numerous objects like Bid Request, Imp, Banner, Video, Audio, Native, PMP, Site, App, Device, User, and Supply Chain, specifying supported and unsupported fields for each.

• Best practices include using the DV360 Partner ID as the seat ID, having publishers list you in ads.txt/app-ads.txt, and providing consistent app information.

• DV360 supports both markup on win notice and markup in the bid for serving options and encourages using OMID for Active View measurement by including specific fields and extensions.

Have the OpenRTB 2.6 Specification available while consulting this page.

Display and Video 360 does not support every field in the OpenRTB specification, and nuances can apply. Sections of this document contain information and recommendations specific to the Display and Video 360 implementation. You should also follow the guidelines presented in the OpenRTB specification unless instructed otherwise.

Some fields are not supported, but are still parsed. These fields must be formatted correctly but won't affect the bidding outcome.

Bid request specification

A bid request is an HTTP Post request with a body of a bid request object . The format of the body is defined in the Content-Type header.

The corresponding response is either an HTTP 204 with no body for a no-bid, or an HTTP 200 with a body of a bid response .

If a bid request is malformed, an HTTP 200 with a body of a bid response with the nbr field populated may be returned.

The response format is controlled by the Accept header.

JSON Format

The default format is used when no accepted MIME type is provided.

JSON requests and responses follow the IAB OpenRTB 2.6 Specification . The following documentation describes extensions and field support.

The header Content-Type : application/json indicates a JSON bid request, Accept : application/json indicates the bid responses should be in JSON format.

Protobuf Format

NOTE: Protobuf support is in beta, please contact DV360 if you are interested.

JSON requests and responses follow the IAB OpenRTB 2.6 Protobuf Specification .

Extensions have limited support, contact DV360 if you are interested.

Send the header Content-Type : application/x-protobuf to indicate a Protobuf bid request, and set Accept : application/x-protobuf to receive Protobuf bid responses.

Bid request object

Bid request extensions object

Source object

Source extensions object

This extension is highly recommended since it impacts how viewability measurements are reported in DV3 to the customer. If the OMID partner name is NOT on the IAB certification list, we are required by MRC to report the viewability metrics separately from the MRC certified metrics. Learn more .

Regs object

Regs extensions object

Imp object

Imp extension object

Banner object

Format object

Video object

We strongly recommend specifying video placement in the bid request. A missing placement field is classified as an unknown placement. See the article on position targeting for more detail.

Supported extension for video object

Audio object

Native object

See the DV360 native ads specifications for more detail.

PMP object

Deal object

Supported extension for deal object

Site object

Site extension object

App object

App extension object

Content object

We recommend passing these attributes where available.

Producer object

Data object

Supported extensions for data object

Segment object

Publisher object

Device object

Supported extension for device object

If ip is changed or truncated, we strongly recommend sending the following extensions to prevent traffic being declared as invalid traffic.

UserAgent object

BrandVersion object

Geo object

User object

Supported extensions for user object

Extended ID object

Extended ID UID object

Supply chain object

Supply chain node object

Bid response specification

BidResponse object

{
  "id": "0",
  "nbr": 2,
  "ext": {
    "err": "Bid request body was empty.",
    "errHelp": "https://.../ortb-spec"
  }
}

Supported extensions for BidResponse object

Seatbid object

Bid object

Supported extensions for bid object

Ad serve options

In section 4.3 of the OpenRTB specification , there are two different serving options:

• Markup served on the win notice
• Markup served in the bid

DV360 supports both options.

• For Banner ad, DV360 always returns markup in the adm field. Markup served on win notice is optional.
• For Video/Audio ad using VAST protocol, DV360 supports returning VAST XML in the adm field or in the response of win notice based on requirements from exchange partners.

Refer to the OpenRTB specification to know the pros and cons of these two options.

Best practices

It is highly recommended to use the Partner ID of Display and Video 360 as the seat ID. The use of exchange-specific seat ID is not recommended.

Ensure your publishers have ads.txt files, or applications with app-ads.txt files associated, and they list you in the file as an authorized seller or reseller. Learn more .

Also ensure consistent information is passed in bid requests. For example, the app.bundle must be consistent with the mobile device information and app.storeurl .

Connected TV

Adhere to the IAB OTT IFA guidelines in passing device.ifa and device.lmt . You should also implement device.ext.ifa_type to be compliant with the guidelines. All of our CTV frequency capping and audience targeting capabilities will require the presence of an IFA.

Also adhere to the recently published IAB OTT/CTV Store Assigned ID guidelines —this defines how app.bundle should be passed for CTV apps—largely using the app store defined ID.

Active View measurement

Active View is a Google technology used to measure if an impression was viewable and for how long. Active View uses OMID for both display and video ads. To enable measurement using OMID, exchanges must add the following fields in OpenRTB requests so that DV360 knows the client's support of OMID.

• Required: Add an API Framework ( Video.api=7 for OMSDK ) to bid requests. This is mandatoryfor Active View to enable measurement using OMID.
• Recommended: Adding omidpn and omidpv to Source.Ext is highly recommendedbecause it will impact how viewability measurements are reported in DV360 to the customer. If the OMID partner name is noton the IAB certification list, we are required by MRC to report the viewability metrics separately from the MRC certified metrics. Learn more .

FAQ

Does DV360 Support exchange custom extensions?

Yes, in addition to the extensions listed in this specification, Display and Video 360 may also support custom extensions on a case-by-case basis. It is recommended to specify and test the custom extension during the integration period.

Does DV360 support rewarded video?

Yes, send us the rewarded video extension .

A lot of my inventory is showing up as demographics unknown, how do I improve demographic coverage?

Populate user.yob and user.gender in bid requests to DV360 to increase coverage.

Does DV360 have endpoints for each region?

No, we use a single endpoint globally and we automatically route requests to the nearest data center, so there's no region-specific endpoint we can provide.

What are the requirements for server-to-server (s2s) requests?

Reach out to request addition to our allowlist. The client User Agent has to be forwarded, and ensure that cookies are disabled/ignored in the response to an s2s VAST fetch.

Does DV360 support OMID?

We are able to measure viewability using OMID as long as it is declared as OMID-enabled at bid request time. Details about this are summarized on pages 24-25 .

Which version of Native do you support? Do you have any Native requirements?

We only support Native Ver1.2. Native specification .

Does DV360 support bid requests sent as GZIP?

DV360 can receive gzip compressed bid requests, and will respond with gzip compressed responses if Accept-Encoding header indicates it's supported.

Does DV360 support DBURL?

Not at the moment.

Does DV360 support win loss notification?

Not at the moment. If you think it would be useful for us to support it please reach out with more details.

Does DV360 require App.name for targeting?

No, DV360 using App.name for reference but it is not required for targeting, App.bundle is used for targeting.

Can DV360 support multiple ad sizes sent in a single bid request?

Yes, we will consider all eligible creative sizes in banner.format.

Does DV360 support multiple formats in the same bid request?

We have limited support for multi-format bid requests, but are working on improving. We support display & video formats for interstitials, but do not currently support display & native. If you are sending multi-format bid requests, please reach out to request a test.

Does DV360 support mixed impression types in the same request?

Currently we only support video/banner interstitials. We are working on native/banner & video/banner. If there are other combinations please reach out to our team.

Can multiple seats each send multiple bids on one or more of such impression opportunities in the same request?

Yes.

Does DV360 have a solution or particular need regarding capping or displaying the same advertiser for multiple such impression opportunities in the same request?

DV360 places enforcement that one advertiser can only bid up to one imp opportunities for each request. We expect SSPs to group imp objects meaningfully; e.g., all on the same page, all in the same app, etc.

Does DV360 support multiple impressions in the same bid request?

DV360 currently supports multiple impression audio objects. However, we will need to test/enable each exchange that would like to use this feature. See bid request specification for more information. We are working on expanding this to other formats:

{
id: "2bbdc94f-7289-4fe2-9a5f-e2a530e06b38",
seatbid {
bid {
  id: "0",
  impid: "234232",
  price: 41.373926619828261,
  adid: "123",
  adm: "...",
  adomain: "xxx.com",
  cid: "0",
  crid: "123",
  dealid: "sample-deal-id-1",
  language: "xx",
},
bid {
  id: "1",
  impid: "234255",
  price: 2.34192037470726,
  adid: "234",
  adm: "...",
  adomain: "xyz.com",
  cid: "0",
  crid: "234",
  dealid: "sample-deal-id-2",
  language: "xx",
},
seat: "123456"
},
cur: "EUR"
}

Contact us

If you have any questions or issues, reach out to our exchange support team.