OpenRTB for Apps

Contact us at support@adagio.io beforehand for this type of integration.

Adagio offers real-time access to demand on various mediatypes (banner, video & native). Integrating Adagio to your demand partners helps you enrich your demand sources, expand globally and monetise different mediatypes through a single unified system.

Check our Bid Request and Bid Response examples specific to each mediatype.

How It Works

The monetization flow through Adagio’s OpenRTB endpoint:

  1. Your Server sends a BidRequest (JSON, gzip-compressed) to Adagio’s regional endpoint.

  2. Adagio runs a real-time auction across multiple DSP partners.

  3. Winning Bid is returned as a BidResponse (JSON, gzip-compressed).

  4. You render the winning creative in your app.

Integration step

1

Declare your inventory

Refer to Declare your websites/apps

2

Update app-ads.txt lines

Refer to Update your (app-)ads.txt file

3

Use OpenRTB Version 2.5 and 2.6

Refer to OpenRTB Version

4

Setup your endpoints

Refer to Endpoints integration

5

Ensure Supported Formats

Here is the list of the different formats that Adagio supports on it's OpenRTB integration.

Platform
Format
Supported

App

Banner

App

Native

App

Video (Instream & Outstream)

6

Ensure Supported Currencies

Adagio uses exchange rates from the European Central Bank to perform currency conversions. Refer to the list of supported currency symbols.

7

Ensure Data compression (gzip)

Refer to Data compression (Gzip)

8

Ensure GDPR/CCPA/TCF compliance

For European and UK traffic, GDPR compliance is mandatory. Refer to our list of vendor IDs, hereunder, to be added in your CMP in order to properly monetize.

Our list of vendor IDs
9

Limit number of tagid per app

  • Each app can declare a maximum of 100 tagid in total (across all requests) of 150 characters at most.

  • If more than 100 tagid are configured for the same app, the extra tagid will be ignored and not monetized.

  • Too many tagid per app prevents our algorithms from learning efficiently.

Placements Naming Suggestions / Examples
  • Banner

    • banner_top

    • banner_middle

    • banner_bottom

    • banner_left

    • banner_right

    • banner_sticky_top

    • banner_sticky_bottom

  • Interstitial

    • interstitial_page_load

    • interstitial_exit

    • interstitial_pause

  • Video

    • video_instream

    • video_outstream

    • video_rewarded

    • video_midroll

  • Native

    • native_feed

    • native_article

    • native_recommendation

  • Special Formats

    • sticky_footer

    • sticky_header

    • companion_banner

10

Timeout requirement (tmax)

We recommend the highest tmax you can set to maximise monetization performance (maximises fill rate and CPM) while maintaining an acceptable user experience.

Last updated

Was this helpful?