OpenMediation offers diversified monetization features, currently supporting Native Ad, Interstitial Ad, Banner Ad, Rewarded Video Ad, Splash Ad and Promotion Ad. Access ads inventories from multiple mainstream Ad Networks through the OpenMediation SDK now.
The SDK supports both Android and iOS, with a Unity/Cocos Plugin to facilitate Unity/Cocos apps integration.
Android Operating Systems Version 4.1(API Level 16+) and above are supported. On the iOS side, version 9 and above are supported. As for the Unity Plugin, please use version 2019.4 and above. As for the Cocos Plugin, please use version 2.4.3.
The Unity Plugin and Cocos Plugin should not be used alone. Instead, it should work along with the OpenMediation SDK for either the Android or iOS platform. Import the plugin into your project in the Unity Editor or Cocos Creator, and target either an Android or iOS build to test the integration.
Smart Ad Inventory
The OpenMediation SDK equipped with smart ad inventory mechanism and optimized SDK initialization pre-loading mechanism, provides the best mediation solution for app developers. For Rewarded Video, Interstitial and Promotion Ad, the SDK will cache ads automatically and maintain ad inventory regularly, such as pre-loading after initialization, loading after ad served and timing loading etc. You have no need to invoke load method to cache ads by yourselves anymore.
Header bidding in compliance with IAB specifications has been supported to maximize revenue through realtime bidding. OpenMediation has built-in support for AdTiming, Mintegral, Helium, Vungle and PubNative bidding. The client-based bid auction solution brings flexibility and convenience by eliminating the need for an auction server. The Auction process works perfectly together with traditional waterfall. Before the waterfall starts, the auction returns a bid winner from AdNetworks that support header bidding. The waterfall winner, coming out of the waterfall process that is largely based on historical data, is compared with the bid winner to eventually determine the final winner.
Let's dive into how to integrate the OpenMediation SDK into your app. We'll first show you the 4 steps it takes to make your app work with OpenMediation as your sole inventory, then we'll tell you how to add more 3rd-party Ad Networks into the mediation mix.
The 4 steps are as follow. You can get the
Before starting integration OpenMediation SDK Into your APP, your need to obtain AppKey and PlacementID in OpenMediation platform first . In the OpenMediation UI, register an account, create an app, and setting your ad placement using the ad unit you want to use. You can follow guides here.
OpenMediation Supports Gradle dependencies mechanisms to integrate our SDK. You can find our latest SDK and demo program in this article.
The OpenMediation aggregation platform supports the display of advertisements from multiple advertising networks. By sending advertisement requests to multiple platforms, the best advertisements are screened for display, which helps maximize your advertising revenue.
The Network's Mediation Guides as follow:
4、Configure Ad Units
So far we are all set to get your app ready for its first Ad unit. In general, there are 4 necessary steps for all types of ads, although some may be optional on either Android or iOS.
Step 1: Init an Ad Object and register callbacks. The Exception is Rewarded Video and Interstitial Ads has no need to Init the Ad Object.
Step 2: Load Ads. You have no need to invoke load method for ad units such as Rewarded Video and Interstitial Ads manually as the SDK will cache ads automatically.
Step 3: Serve Ads. The recommend way to serve ads is to check the ad's availability first before you showing Ads to your users.
Step 4: Destroy an Ad. Only ad units like Banner and Native are need.
The guides for ad units as follow.
Here are some additional settings. Some of them are used to help your ads comply with the privacy regulations of GDPR and COPPA, some are used to report conversion and in-app purchase data with OpenMediation to help promote your advertising revenue. So please be sure to read it carefully.
OpenMediation fully complies with IAB Europe's Mobile In-App CMP API v1.0: Transparency & Consent Framework. Integrate a Consent Management Platform (CMP) in your app and store the collected end user's consent information in PreferenceManager.getDefaultSharedPreferences.
To protect children, OpenMediation does not advertise for users under the age of 13. You have to agree to the COPPA compliance option when you create your app.
OpenMediation’s mediation platform supports publishers to restrict the sale of end users personal information under the California Consumer Privacy Act (CCPA).
You can now easily tailor the way you serve your ads to fit a specific audience! You’ll need to inform our servers of the users’ details so the SDK will know to serve ads according to the segment the user belongs to.
If any exception or no_ads_fill was happened during the SDK Initing and loading or showing ads, SDK would return error code and cause with InitCallback and Listener callback of ad units. Follow our Error Code to check your error code.
Test your integration in 'Test Mode'
OpenMediation supports an advanced functionality that allows for ad content testing on specific devices to evaluate and check ad delivery without affecting your live app version or your earnings.
All right. Let's make sure the integration works. First, go to OpenMediation Dashboard and add your device as a Test Device:
Then turn on the Test Mode, which stays on for an hour before you turn it on again, to receive test campaigns.