Getting started
This documentation will go through all the steps required to display Ogury ads through IronSource mediation on iOS 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 ASSET_KEY.

Step 2: Import the Ogury SDK

To import the latest version of the Ogury SDK into your project, Ogury provides two methods:
  • Automated integration using Ogury's CocoaPods repository (recommended).
  • Manual integration of the Ogury SDK Frameworks.
Manual integration

Configure your Podfile

Open the podfile of your application and add the following lines into your target:
pod 'OgurySdk'
pod 'OguryMediationIronSource'
To know more about the latest release of the Ogury SDK, you can check the release notes.

Download the Ogury SDK

To download the SDK, please check the release notes.

Configure your IDE

Drag the following Frameworks into your Xcode project:
  • OguryAds.xcframework
  • OguryChoiceManager.xcframework
  • OMSDK_Ogury.xcframework
Check if the frameworks are added to Linked Frameworks and Libraries on Target properties under General Tab of your project

Step 3: Configure your application

In your project Build Settings, do the following changes:
  • add the -ObjC flag to Other Linker Flags.

Step 4: Collect the user consent and initialize Ogury Ads

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.
In order to integrate the Ogury Choice Manager, you must (i) first collect the user consent and (ii) then initialize Ogury Ads with the setup method.

[Optional] Initialize Ogury Ads

The setup method will initialize Ogury Ads. It fastens the preloading of the first ad.
OguryAds.shared().setup(withAssetKey: "ASSET_KEY")
[[OguryAds shared] setupWithAssetKey:@"ASSET_KEY"];
The setup method takes the following parameter:
  • the Asset Key of your application. If you do not have one yet, you can refer to the first step to create it.
A complete integration example with consent collection is available within Ogury Choice Manager section.

Step 5: Integrate Ogury ad formats

Congratulations, the Ogury SDK is now initialized! You are now ready to integrate your first ad. Ogury provides three different ad formats, (i) Interstitial Ads, (ii) Opt-in Video Ads, (iii) Banner Ads and (iv) Thumbnail Ads. You can refer to the following sections to proceed with the integration:
We suggest you setup a test device before you start integrating so that the device configuration has time to propagate while you perform your 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 modified 7mo ago