OpenRTB: Getting Started for App

Note

Contact us at contact@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.

Note

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 demand partners.
3. Winning Bid is returned as a BidResponse (JSON, gzip-compressed).
4. You render the winning creative in your app.

Integration Steps

Declare your inventory

Refer to declare-your-websites-apps.md

Update app-ads.txt lines

Refer to update-your-app-ads.txt-file.md

Use OpenRTB Version 2.5 and/or 2.6

Refer to supported-openrtb-versions.md

Setup your endpoints

Refer to endpoints-integrations.md

Ensure Supported Formats

Formats supported by Adagio on its OpenRTB integration.

Note

We support multi imps and multi formats.

Platform	Format	Supported
App	Banner	✅
App	Native	✅
App	Video (Instream & Outstream)	✅

Ensure Supported Sizes

Refer to monetizable-ad-sizes.md.

Ensure Supported Currencies

Adagio uses exchange rates from the European Central Bank to perform currency conversions. Refer to supported-currencies.md

Guarantee Data compression (gzip)

Refer to data-compression-gzip.md

Confirm GDPR/CCPA/TCF compliance

For European and UK traffic, GDPR compliance is mandatory.

Refer to gdpr-ccpa-tcf-compliance.md

Ensure configure parameters

Refer to Bid Request Fields for App Inventory

Restrict Number of TagIDs per app

Don’t exceed 100 TagIDs in total (across all requests) and keep each TagID under 150 characters to ensure optimal performance and monetization

Review tagid-limits-and-guidelines.md to understand these limits and best practices.

Ensure you respect the minimum timeout (tmax)

Danger

Any tmax < 470ms has very little chance to monetize properly (due to competition reduction, given bidders specific Time to Respond), please make sure to not send traffic with values lower than this limit.

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

Verify Bid Request and Bid Response Requirements

Refer to bid-request-fields-for-app-inventory.md and bid-response-fields-for-app-inventory.md

Improve your monetization performance

To maximize revenue and ensure optimal ad delivery, we recommend:

1. Review the supply chain status of your inventory to identify and fix any issues. See review-inventory-supply-chain-status.md
2. Ensure that you comply with Amazon DSP’s requirements for monetisation. See amazon-dsp-contenturl-and-amazonadbot.md
3. Enhance your ad requests by adding parameters through extensions. Explore supported-extensions on App, including EIDs, OMID and SkadNetworkID.