OpenRTB Integration

Please fill out the application form: it helps us understand your capabilities and get back to you with an answer.

Here is the standard integration flow for your reference:

As an exchange focused on in-app inventory, the Bidease Ad Exchange has expertise in working with all the popular in-app formats. The in-app inventory can be divided into several groups, each with its own advantages. This short guide provides an overview of the formats available on the Bidease Ad Exchange. For more information on each format, see the sections below.

The popular sizes are:

Supported formats: PNG, JPG/JPEG, GIF.

The Bidease Ad Exchange supports both MRAID playable and MRAID video. When bidding with a creative, best practice is to keep the HTML itself smaller than 15 KB and the files it loads no bigger than 2–3 MB; we consider these sizes optimal.

For MRAID, the Bidease Ad Exchange has inventory supporting static, HTML and IFrameResource end cards.

The Bidease Ad Exchange supports both MRAID playable and MRAID video. The custom close option is supported on most of the inventory.

To bid on rewarded inventory, make sure you target requests with the rewarded flag. The general requirements for the creatives are similar to those for non-rewarded VAST.

Native assets have the following restrictions:

Native video requires additional assets.

For requests from Russia (RUS geo), Bidease passes an additional object in BidRequest.regs.ext:

{
   "regs":{
      "ext":{
         "nroa":{
            "version":"2",
            "mandatory":1
         }
      }
   }
}

To pass ERID data in BidResponse.seatbid.bid.ext, use this specification:

{
    "nroa":{
       "erid":"uhk90ol"
    }
}