OpenRTB Integration

Modified on Tue, 19 Sep, 2023 at 8:59 AM



Please, fill out the application form, it will help us to understand your capabilities and come back with an answer.


 

Here is the general information and advice on starting integration with Bidease Ad Exchange.


  • We support OpenRTB 2.5
  • Our servers are located in US East, US West, EMEA
  • The timeout is 100 milliseconds
  • We expect you to pass burl and nurl at all times
  • Pass valid ad domain at all times
  • Comply with the content policies

 


Integration flow

Here is the standard integration flow for your reference:

  1. Once the agreement is signed please provide us with an endpoint or multiple endpoints, whatever is more convenient for you. Please do not forget to tell us about QPS limitations for the endpoints if there are any.

  2. The tests are normally done on 320x50 banners; You will receive a small amount of QPS to test latency and request/response compatibility.

  3. If the test is successful, we will increase the number of QPS for discrepancy tests. Please make sure to bid as much as possible.

  4. We do not strictly require our partners to provide reports for discrepancy after the integration is finished, but you might want to consider it.  

  5. If the banner test goes well, we will move to testing other formats to complete  the integration.

Ad Formats - Supported Ad Formats overview


As an Exchange focused on in-app inventory, 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 of them has its own advantages. This short guide will provide an overview of the formats available on the Bidease Ad Exchange. For more information on each format, please refer to the specified sections.


Video


Rewarded and non-rewarded video placements are dominating in-app monetization and are in high demand for performance campaigns and brand awareness campaigns alike. 

Bidease Ad Exchange supports both rewarded and non-rewarded placement targeting, which offers a lot of flexibility in targeting the right users. 

As for the formats, video placements offer quite a variety of options. As far as formats go, with Bidease Ad Exchange you can run VAST campaigns, VAST wrapper campaigns, MRAID video campaigns (refer to MRAID section). 


Playable Interstitials


Playable ads are becoming increasingly popular in mobile advertising, as they give potential users an opportunity to interact with the product and see its advantages. Rewarded and non rewarded placements are available for playable creatives. 


Other Display


Static display creatives have been around for a long time now and they still do their job. There are various sizes of banners available in in-app, from smaller banners to static interstitial. 


Native and Native Video


Native ads are there to seamlessly fit into the user’s session and slyly draw attention to the product without being too forward.


HTML


The popular sizes are:

  • Banner Phone (320×50)

  • Banner Tablet (728×90)

  • Medium Rectangle (300×250)

  • Fullscreen Interstitial Portrait (320×480)

  • Fullscreen Interstitial Landscape (480×320)

  • Tablet Fullscreen Interstitial Portrait (768×1024)

  • Tablet Fullscreen Interstitial Portrait (1024×768)



Formats Supported

  • PNG

  • JPG/JPEG

  • GIF


MRAID

 

Bidease Ad Exchange supports both MRAID playable and MRAID video. When bidding with a creative, best practice is to make sure that the HTML itself is smaller than 15kb and the files it uploads are no bigger than 2-3MB. We consider these sizes as optimal.

For MRAID inventory on Bidease Ad Exchange we have inventory supporting static, HTML and IframeResource endcard.


  When bidding on MRAID video inventory, please make sure you are bidding on requests passing  "attr": [6] or [7] as per OpenRTB specifications.



Rewarded MRAID

Bidease Ad Exchange supports both MRAID playable and MRAID video. 

Custom close option is supported on most of the inventory.


Video VAST


Video file 

  • We recommend mp4 format

  • The video duration should ideally be 30 seconds or less

  • The ideal file size is around 2MB, the maximum size is about 5MB

  • 320×480, 480×320, 1024×768, 768×1024, 1280x720



Companion ad/end card

  • .png, .bmp, .jpeg, and .gif

  • 320x250, 320×480, 480×320, 1024×768, 768×1024



On video banner

  • 230х230

  • .png, .bmp, .jpeg


Playable end cards are supported via HTML and iframeResource.

Opt-In Rewarded VAST Video


To bid on rewarded inventory, make sure you are targeting requests with "rewarded" flag. General requirements for the creatives are similar to that of non rewarded VAST.

  Static end cards are preferred as they are supported on most of the rewarded video inventory.

Native Ads

There are the following restrictions for native assets:

  • The title should be no longer than 50 characters

  • The main text is limited to 150 characters

  • The icon should be 80 × 80 pixels or greater (with the same ratio) 

  • The main image should be 800×417, 1200x627, 1200x628 or 800x418 pixels 

  • The call-to-action is limited to 15 character


Native Video

There are additional assets required for native video.

Maximum video length accepted is 120s, but we recommend shorter videos.

Preferred format is mp4 and the preferred size is below 5mb.

Best practice is to submit both video and main image asset, as the image will be displayed if the video fails.


ERID Specifications


Bidease will pass additional objects in BidRequest.regs.ext if request coming from RUS geo.

AttributeTypeDescription
nroaobjectParent object.
nroa.versionstringCurrent version number. Please, do not pass prefix `v`.
nroa.mandatoryboolIf you received `true` in request - it's mandatory to pass ERID information in response. Overwise you will not be admitted to the auction.


Example of request:

{
   "regs":{
      "ext":{
         "nroa":{
            "version":”2”,
            "mandatory":true
         }
      }
   },
}

For passing ERID data in BidResponse.seatbid.bid.ext - please, use this specifications.

AttributeTypeDescription
nroaobjectParent object.
nroa.eridstringERID token.


Example of response:

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

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article