For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content

Open RTB 2.5 Bid Response

The response for a bid request has the following structure:

Bid Response Object

Attribute
Required?
Description

id

Yes

ID of the bid request, must match id sent in the request (string)

seatbid

Yes

Collection of bids made by the bidder on behalf of a specific seat.

seatbid

Attribute
Required?
Description

bid

Yes

ID of the impression object to which this bid applies, must match id sent in the request (string)

seatbid.bid

Attribute
Required?
Description

id

Yes

ID for the bid object chosen by the bidder (string)

impid

Yes

ID of the impression object to which this bid applies (string)

price

Yes

Bid price in CPM or CPC (float)

adm

Yes

Ad markup (string)

nurl

No

Win notification URL, it is recommended to use HTTP over HTTPS for nurl (string) - not mandatory

burl

No

Billing notification URL, called by EXADS when the impression or click becomes billable (CPM or CPC, per the btype field), so it can be counted from the billable event instead of the pixel. Recommended to use HTTP over HTTPS for burl (string)

seatbid.bid.ext

Attribute
Required?
Description

btype

Recommended

Pricing Model. Values: 1 = CPM, 2 = CPC. Default = 1 (int). Note: When response is for an Email Clicks zone request, 1 = Smart CPC.


Note: Only Push Notification and Native ad formats may bid with the CPC pricing model.


JSON Examples

Email Clicks JSON

Fullpage Interstitial (Mobile and Desktop) JSON

Native: JSON

ADM Examples

The examples below shows examples of data used in this ADM parameter.

Popunder

Video: XML

Native Ads: JSON

For native ads the adm parameter should contain a JSON encoded string like this:

  • crop_anchor_point: MIDDLE_CENTER = 0, TOP_LEFT = 1, TOP_CENTER = 2, TOP_RIGHT = 3, MIDDLE_LEFT = 4, MIDDLE_RIGHT = 5, BOTTOM_LEFT = 6, BOTTOM_CENTER = 7, BOTTOM_RIGHT= 8 (integer) - not mandatory

crop anchor point

Which is based on the following JSON object:

Push Notification Ads: JSON

For Push Notification ads the adm parameter should contain a JSON encoded string like this (note that we use the 'native' object to implement push notification ads). Width and height depend on the width and height coming from request. Currently supported dimensions are 192x192 and 720x480. One image asset per notification.

Which is based on the following JSON object:

* Only one imptracker URL is allowed in the case of Push Notification ads * We use the 'native' object for push notification ads

No Bid Response

To answer a bid request without making an actual bid, an HTTP response code 204 "No Content" should be sent.

Billing Notification

If the parameter Bid Response Object -> Seat Bid Object -> Bid Object -> burl is in the bid response and is a valid URL, EXADS will send a GET request to it when the impression or click becomes billable (CPM or CPC, per the btype field). This allows the event to be counted from the billable server-to-server event rather than from pixel-based tracking.

If both nurl and burl are present, both will be called.

Last updated

Was this helpful?