Getting started

This documentation will go through all the steps required to display Ogury ads through IronSource mediation on Android platform.

The Custom Adapter feature (closed Beta) will allow you to connect Ogury as a network on ironSource mediation. This feature needs to be activated first by your ironSource Account Manager. Please make sure it is done before following the integration guide below.

Step 1: Register your application

The Asset Key follows the pattern: OGY-XXXXXXXXXXXX, where X is an uppercase letter or digit. In all the following code samples, we will refer to this Asset Key by using the string OGY-XXXXXXXXXXXX.

Step 2: Import the Ogury SDK

To import the latest version of the Ogury SDK and the Ogury adapter for the IronSource mediation into your project:

  • Open the build.gradle of your application

  • Add the following lines:

repositories {
    maven { url '' }

dependencies {
    implementation 'co.ogury:ogury-sdk:5.+'
    implementation 'co.ogury:ogury-adapters-ironsource:5.+'

Note that the versioning scheme for the Ogury adapters is <Ogury SDK version>.<adapter patch version>. For example, if you are using the Ogury SDK version 5.0.9, the corresponding adapter version will be

If the adapter needs updating outside the lifecycle of the Ogury SDK release, the patch version will increase. For example, an update on the adapter version will be released in version

To know more about the latest releases, you can check the release notes for the Ogury SDK and for the Ogury Adapter for IronSource mediation.

As of November 13, 2023, both Ogury Choice Manager and the End User License Agreement (EULA) are deprecated.

Consequently, the EULA will cease to be presented, and the Choice Manager will no longer display consent notices. As a result, it is strongly advised to discontinue the use of Ogury Choice Manager in any new versions of applications. Developers are encouraged to explore alternative solutions in light of this deprecation.

The European GDPR regulation requires obtaining the users' consent in order to display them personalized ads, (i) when the company processing personal data is based in the EU, or (ii) when the users are EU citizens.

As a company based in the EU, Ogury accordingly requires an explicit consent from the users to collect their personal data and display them personalized ads. The consent collection can be operated:

Note that the Ogury SDK meets privacy requirements by design. Shall it not receive a valid consent status from the Ogury Choice Manager or from a validated third-party consent solution, it will display an End User License Agreement (EULA) before serving the first ad. Another way to put it: no targeted ad will be displayed to the users if they didn't give their consent first.

Step 4: Integrate Ogury ad formats

Currently, Ogury only provides adapter for the Interstitial Ad format. You can refer to the following sections to proceed with the integration:

Before going live

Last updated