Getting started

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

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

The Ogury custom events are distributed via the Cocoapods repository

The Ogury SDK will be automatically imported into your project as a dependency

Configure your Podfile

Open the podfile of your application and add the following lines into your target:

pod 'OguryMediationXandr'

If you are using Xcode 12+, please use CocoaPods 1.10+ to avoid build errors due to the migration of our SDK to XCFramework.

To know more about the latest release of the Ogury SDK, you can check the release notes.

Step 3: Configure your application

In your project Build Settings, do the following changes:

  • add the -ObjC flag to Other Linker Flags.

Step 4: Initialize the Ogury SDK

The start method will initialize Ogury SDK:

let configuration = OguryConfigurationBuilder(assetKey: "OGY-XXXXXXXXXXXX").build()

Ogury.start(with: configuration)

The start method takes the following parameter:

  • a configuration object initialized with 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.

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. By default, the consent collection is operated by the Ogury Choice Manager. This turnkey solution streamlines the consent management for Ogury and any other of your partner, helping you to be fully compliant with the regulation.

All you need to do is to integrate the Ogury Choice Manager, and everything is then managed on your behalf, from the consent notice disclosure to the ongoing GDPR compliance.

In order to collect user consent, follow the Ogury Choice Manager guide.

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.

If you already have your own consent notice to collect user consent, we provide a procedure to transmit the consent to us.

Step 6: Integrate Ogury ad formats

Congratulations, the Ogury SDK is now initialized! You are now ready to integrate your first ad. Ogury provides two different ad formats, (i) Interstitial Ads and (ii) Banner Ads. You can refer to the following sections to proceed with the integration:

Before going live

Last updated