Using burl to request billing notifications

DSPs can use the OpenRTB 2.5 burl (billing notify URL) field in bid responses to request billing notifications and reduce reporting discrepancies.

The following steps describe how burl works in an OpenRTB interaction between a publisher, Index Exchange (IX), and a DSP.

How it works

Image illustrating how burl works in an OpenRTB interaction between a publisher, IX, and a DSP. The steps are detailed in the text below.

Step 1

The mobile app SDK generates an ad request and sends it to the publisher's ad server. The publisher's ad server then makes a request to IX.

Step 2

IX sends a bid request to the DSP.

Step 3

The DSP sends a bid response to IX that includes the following fields in the bid response object:

  • adm: The creative markup to render on the user device.

  • burl: The DSP billing notice, if the DSP wins the bid.

Note:

burl TTL and expiry time:

  • IX holds the auction data for 3 hours (TTL). If a burl is called after this time, it is considered invalid. Consequently, IX does not fire the DSP burl either.
  • The TTL is separate from the expiry time set by the DSP. A DSP burl call that is received 3 hours before TTL is sent to the publisher regardless of the DSP expiry time.

Step 4

IX stores the DSP's burl which contains the DSP billing notice.

Step 5

IX sends a bid response to the publisher that includes the following fields in the bid response object:

  • adm: The creative markup from the DSP that includes the IX ad load notice which notifies IX when the ad begins to render on the device.
  • burl: The IX billing notice which is different from the DSP's billing notice burl (stored in step 4). It is called by the user's device and notifies IX when the impression has become billable.

Note: If a publisher does not support burl, IX appends the DSP and burl to the creative markup (adm).

Step 6

The user's device fetches and renders the ad.

Step 7

The device calls the IX ad load notice and IX is notified that the ad has begun to render.

Step 8

The ad is visible to the user and the device calls the IX burl when the impression is billable based on the publisher's billing logic.

Step 9

IX considers the impression biddable.

Step 10

IX calls the DSP burl (stored in step 4) and notifies the DSP that the impression is billable.

Note: Currently, the DSP burl is sent as an HTTP 302 redirect from the user's device. In the future, IX will be offering a service to call the DSP burl server-side.