Skip to end of metadata
Go to start of metadata

Mobile OpenRTB Bid Response

In the OpenRTB 2.2 specification, you'll find required, recommended, and optional bid response fields. Xandr supports all required fields but only certain recommended and optional fields. This page clarifies which recommended and optional fields Xandr supports.

Xandr Support for OpenRTB 2.2 will be deprecated on May 21, 2018.

Xandr supports the OpenRTB 2.4 specification for receiving all media type impressions.

On This Page

Optional/Recommended Fields Supported By Xandr

Xandr supports the recommended and optional fields listed below. Any optional or recommended fields not listed below will not be populated in bid responses.

Seat Bid Object

Xandr supports the following optional field in the seatbid object.

Field

Type

Description

seat

string

The Xandr ID of the member on whose behalf the bid is made.

Bid Object

Xandr supports the following optional fields in the bid object.

Field

Type

Description

nurlstring

The win notice URL.

admstring

The actual ad markup. XHTML if a response to a banner object, or VAST XML if a response to a video object.

adomainstring OR
array of strings

The advertiser’s primary or top-level domain for advertiser checking. This can be one domain or an array of domains if there is a rotating creative.

lurlstring

The sample image URL (without cache busting) for content checking.

cidstring

The campaign ID or similar that appears within the ad markup.

cridstring

The creative ID for reporting content issues or defects.

dealidstringThe Xandr code for the deal. To retrieve deal codes, use the Deal Service.
  • No labels