ironSource

If you plan to use the MoPub SDK to load and display ads from ironSource via mediation, use this article for integration instructions and information unique to the ad network. To learn more about how MoPub mediation works, refer to our MoPub Network Mediation article.

Supported Ad Formats

ironSource currently supports the following ad formats. For support information, visit the ironSource homepage.

MoPub Formats ironSource Ad Formats
Interstitial Interstitial
Rewarded Video Rewarded Video

Download and Integrate

To download the Ad Network Name adapters, navigate to the Mediation Integration Tool. You must also download the ironSource SDK:

  • Download ironSource SDK for iOS

  • Download ironSource SDK for Android

    • IronSource adapters are released as an Android Archive (AAR) file starting with version 6.8.2.1. The AAR includes the required Manifest data for IronSource. As a result, you no longer need to update your AndroidManifest manually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by ironSource must be manually entered into the AndroidManifest.

    • For users leveraging ProGuard, be sure to add the following code to your ProGuard profile:

       -keepclassmembers class com.ironsource.sdk.controller.IronSourceWebView$JSInterface {
           public *;
       }
      
       -keepclassmembers class * implements android.os.Parcelable {
           public static final android.os.Parcelable$Creator *;
       }
      
       -keep public class com.google.android.gms.ads.** {
           public *;
       }
      
       -keep class com.ironsource.adapters.** { *;
       }
      
       -dontwarn com.ironsource.mediationsdk.**
       -dontwarn com.ironsource.adapters.**
       -keepattributes JavascriptInterface
      
       -keepclassmembers class * {
           @android.webkit.JavascriptInterface <methods>;
       }
      

For the latest download and integration instructions, consult ironSource’s tutorials before you integrate the SDK and adapters.

Initialize the ironSource SDK

Initialize the ironSource SDK at app launch as shown. Doing so helps maximize fill rate for the initial ad request to ironSource.

// Android
IronSource.initISDemandOnly(Activity activity, String appKey, AD_UNIT.REWARDED_VIDEO, AD_UNIT.INTERSTITIAL);

// iOS
[IronSource initISDemandOnly:appKey ];

// Unity
IronSource.Agent.initISDemandOnly (appKey, IronSourceAdUnits.REWARDED_VIDEO, IronSourceAdUnits.INTERSTITIAL);

Update Network Configuration Settings

Make sure to pass the ironSource-Appkey as part of the ironSource configuration.

Android

// declare your ironSource App Id and Ad Units
Map<String, String> ironSourceSettings = new HashMap<>(); ironSourceSettings.put("​applicationKey​","YOUR_IRONSOURCE_APPKEY");

SdkConfiguration sdkConfiguration =
new SdkConfiguration.Builder(isCredentials)
    .withMediatedNetworkConfiguration(IronSourceAdapterConfiguration.class.getName(), ironSourceSettings)
    .build();

// Initialize MoPub

iOS

// declare your ironSource App Id and Ad Units
NSDictionary * ironSourceConfig = @{@“applicationKey”: @“YOUR_IRONSOURCE_APPKEY”};

NSMutableDictionary * config = [@{@"IronSourceAdapterConfiguration" : ironSourceConfig} mutableCopy];

sdkConfig.mediatedNetworkConfigurations = config;

// Initialize MoPub

Unity

Set the appkey and ad units as part of the developer settings integration.

Update Additional Settings: CCPA Compliance

ironSource network supports publishers’ ability to restrict the sale of end users’ personal information under the California Consumer Privacy Act (CCPA). Handle the notification about personal information of specific users located in California based on a “do not sell” setting. For more information, refer to the ironSource CCPA documentation for ​iOS​ and ​Android​.

Set Up ironSource on the MoPub Dashboard

App Key and Instance ID are required fields.

Network Reporting and Auto CPM

The following setup is required to take advantage of Auto CPM. To enable ironSource network reporting and Auto CPM:

  1. Navigate to the MoPub UI’s Networks tab. (Refer to these additional instructions that provide more detail for the remaining steps.)

  2. In the Network settings page for ironSource:

    • enable reporting access

    • provide the Username and Secret Key

      To find the Username and Secret Key, navigate to My Account within ironSource, and then to the API tab:

      ironSource reporting 1

  3. Navigate to the Auto CPM preferences page and turn on Auto CPM.

Set Up Reporting

The username is the login or e-mail that is used to login to the ironSource UI. The Secret Key parameter is unique for your ironSource account. To retrieve it, click on your user profile in the top right corner of the screen, and select My Account. You will find the Secret Key in the Reporting API section.

Test an Ad

As you test your SDK integrations and network setups, we recommend that you leverage test ad placements to ensure a consistent fill rate.

With test mode enabled, you can request ads using the ad unit ID you created earlier for this purpose and receive an ironSource test ad. Be sure to disable test mode after testing!

Additional Support

For inquiries and support, contact ironSource.

Last updated December 03, 2020

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2020 MoPub (a division of Twitter, Inc.)