Getting started

This documentation will go through all the steps required to display Ogury ads through ironSource mediation on Unity 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 applications

In case you publish your application on both Android and iOS, you should do the following steps twice, once for the Android application and once for the iOS application. Otherwise just select the platform you publishes for.

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:

  • the Asset Key of the Android application by using the string ANDROID_ASSET_KEY.

  • the Asset Key of the iOS application by using the string IOS_ASSET_KEY.

Step 2: Import Ogury SDKs

The Ogury SDKs import is based on the dependency resolver used by ironSource: Google External Dependency Manager for Unity (formerly Play Services Resolver). It will enable you to download the latest versions of Ogury SDK and adapters directly from your Unity development platform.

To do this, first create an OguryDependencies.xml file in Assets/Editor directory with the following content:


<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<dependencies>
</dependencies>

Import the Android Ogury SDK and its adapter

Add the following lines to import the Android Ogury SDK (co.ogury:ogury-sdk) and its adapter (co.ogury:ogury-adapters-ironsource):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<dependencies>
    <androidPackages>
        <androidPackage spec="co.ogury:ogury-sdk:5.+">
            <repositories>
                <repository>https://maven.ogury.co</repository>
            </repositories>
        </androidPackage>
        <androidPackage spec="co.ogury:ogury-adapters-ironsource:5.+">
            <repositories>
                <repository>https://maven.ogury.co</repository>
            </repositories>
        </androidPackage>
    </androidPackages>
</dependencies>

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 5.0.9.0.

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 5.0.9.0 will be released in version 5.0.9.1.

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

Import the iOS Ogury SDK and its adapter

Add the following lines to import the iOS Ogury SDK (OgurySdk) and its adapter (OguryMediationIronSource):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<dependencies>
    <iosPods>
        <iosPod name="OguryMediationIronSource" version="~> 2.1.0.0" />
    </iosPods>
</dependencies>

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

Step 3: 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

Ogury is part of the IAB Authorized Sellers for Apps initiative to fight inventory fraud for applications. It is recommended to update your app-ads.txt to include Ogury as described in the app-ads.txt section.

Last updated