Android SDK Integration

Before you start We support Android Operating Systems Version 4.1 (API level 16) and up.

As of ironSource SDK 7.3.0, the supported Kotlin version is 1.5.0+.

The download, use and access to the SDK is subject to the ironSource Platform Online Terms and Conditions. If you do not agree to the terms of ironSource Mobile SDK Publisher Online Terms & Conditions, do not download, access, or use the SDK, or the underlying services.

Step 1. Add the ironSource SDK to Your Project

Important! If you’re building your app using Target SDK Level 30, make sure to use ironSource SDK Version 6.18.0+.

As of ironSource SDK Version 6.16.0, ironSource SDK will be released as AAR.
Please make sure that you update the dependency section according to the information below.
Please note that Manifest Activities are included in the AAR. 

ironSource SDK supports both Gradle dependencies and manual download mechanisms to integrate our SDK:


  1. Add the following to your app’s build.gradle file inside repositories section:
    repositories {
        maven {
            url ''
  2. Then add the following to the dependencies section:
    Please note that as of ironSource SDK Version 6.16.0 ironSource SDK will be released as AAR.
    dependencies {
        implementation 'com.ironsource.sdk:mediationsdk:' 

    Gradle version 7+

    If you’re using Gradle version 7+, update your repository section on your settings.gradle file, instead of build.gradle. Please note the repository section should be included as part of the dependencyResolutionManagement section:

    dependencyResolutionManagement {
        repositories {
            maven {
                url '' 

    Manual Download

    1. Download Android SDK Version
    2. Import the .AAR file as a library project.
    3. If using Android Studio, download the ironSource .AAR file and add as a dependency to your own module.
    4. Go to FileNewNew ModuleImport .AAR and navigate to the location where the ironSource .AAR file has been downloaded.
    5. Note: ironSource Manifest Activities are included in the AAR.
    6. Make sure you add the following to your build.gradle file under the dependencies section:
      implementation(name: 'mediationsdk-', ext:'aar')

    7. As of ironSource SDK 7.0.4+ you are required to add the Kotlin JARs to your project. You can read more about Kotlin support here.

    Optional: Manual JAR Integration

    If you are using mediationsdk_xxx.jar in your project, you can still use the same configuration.  

    1. Rename the new mediationsdk-xxx.aar to 
    2. Extract the classes.jar
    3. rename it to mediationsdk_xxx.jar. 
    4. Update AndroidManifext.xml

    Update AndroidManifest.xml for Manual JAR Integration 

    To update your AndroidManifest.xml, please complete the following steps:

      1. Manifest Permissions
        Add the following permissions to your AndroidManifest.xml file inside the manifest tag but outside the <application> tag:
        <uses-permission android:name="android.permission.INTERNET" />
        <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
      2. Manifest Activities and Provider
        Add this section inside the <application> tag in your AndroidManifest:
                    android:hardwareAccelerated="true" />
                    android:theme="@android:style/Theme.Translucent" />
                    android:theme="@android:style/Theme.Translucent" />
                    android:name="com.ironsource.lifecycle.IronsourceLifecycleProvider" />

    Demo Application

    The Integration Demo application demonstrate how to integrate the LevelPlay Mediation in your app.

    Download Android Demo Application

    Step 2. Google identifier permissions

    1. Add the Play Services dependencies into the dependencies block, to allow GAID and APP Set ID information to be retrieved.
      dependencies { 
          implementation fileTree(dir: 'libs', include: ['*.jar']) 
          implementation '' 
          implementation '' 
          implementation '' 
      Learn more about Google’s app set id

    2. Apps updating their target API level to 31 (Android 12) will need to declare a Google Play services normal permission in the manifest file as follows:
      <uses-permission android:name=""/>

      Read more about Google Advertising ID changes here.

    Amazon devices do not utilize Google Play Services. If you are building for the Amazon platform, skip the above step.

    Step 3. Override Your Activity Lifecycle Methods

    Application Lifecycle
    Override the onPause(), onResume() methods in each of your activities to call the corresponding ironSource methods as follows:

    protected void onResume() {
    protected void onPause() {

    Step 4. Set the Listeners

    The ironSource SDK fires several events to inform you of your ad unit activity. To receive these events, register to the listener of the ad units you set up on the LevelPlay platform.

    Make sure you set the listeners before initializing the SDK, to avoid any loss of information.

    • For Rewarded Video
    • For Interstitial
    • For Offerwall

    Step 5. Initialize the SDK

    Important! ironSource  SDK supports optional SDK settings such as UserID and Segments that must be configured before you initialize the SDK. See our guide on Advanced SDK Settings for setup instructions.
    If you’re serving the Offerwall ad unit or using server-to-server callbacks to reward your users with our rewarded ad units, you must set the UserID.

    Init the SDK

    The SDK can be initialized in two ways:

    1. We recommend this approach as it will fetch the specific ad units you define in the adUnits parameter. Ad unit is a string array.
      *Ad Units should be in the type of IronSource.Ad_Unit.AdUnitName, example 
      IronSource.init(this, appKey, IronSource.AD_UNIT.OFFERWALL, IronSource.AD_UNIT.INTERSTITIAL, IronSource.AD_UNIT.REWARDED_VIDEO, IronSource.AD_UNIT.BANNER);

      When using this init approach, you can now initialize each ad unit separately at different touchpoints in your app flow in one session.

      //Rewarded Video
      IronSource.init(this, appKey, IronSource.AD_UNIT.REWARDED_VIDEO);
      //Init Interstitial 
      IronSource.init(this, appKey, IronSource.AD_UNIT.INTERSTITIAL); 
      //Init Offerwall
      IronSource.init(this, appKey, IronSource.AD_UNIT.OFFERWALL) 
      //Init Banner
      IronSource.init(this, appKey, IronSource.AD_UNIT.BANNER);
    2. Alternatively, you can init the SDK as detailed below and the SDK will init the ad units you’ve configured on the LevelPlay platform:
      IronSource.init(this, appKey);

    Init Complete Callback           

    The ironSource SDK fires callback to inform you that the ironSource SDK was initialized successfully, for ironSource SDK 7.2.1+ . This listener will provide you an indication that the initialization process was completed, and you can start loading ads. The callback will be sent once per session, and will indicate the first initialization of the SDK. 

    IronSource.init(this, appKey,new InitializationListener) { 
    @Override public void onInitializationComplete() {
     // ironSource SDK is initialized 

    For ProGuard Users Only

    If you are using ProGuard with the ironSource SDK, you must add the following code to your ProGuard file (Android Studio: or Eclipse: proguard-project.txt):

    -keepclassmembers class * implements android.os.Parcelable {
        public static final android.os.Parcelable$Creator *;
    #noinspection ShrinkerUnresolvedReference
    -keep class com.ironsource.unity.androidbridge.** { *;}
    -keep class** {public *;}
    -keep class** { *; }
    -keep class** { *; }
    -keep class com.ironsource.adapters.** { *; }
    -dontwarn com.ironsource.**
    -dontwarn com.ironsource.adapters.**
    -keepclassmembers class com.ironsource.** { public *; }
    -keep public class com.ironsource.**
    -keep class com.ironsource.adapters.** { *;
    -dontwarn com.iab.omid.**
    -keep class com.iab.omid.** {*;}
    -keepattributes JavascriptInterface
    -keepclassmembers class * { @android.webkit.JavascriptInterface <methods>; }

    Step 6. Verify Your Integration

    The ironSource SDK provides an easy way to verify that your Rewarded Video Mediation integration was completed successfully. To verify your ironSource SDK integration as well as any additional Ad Networks you have implemented, simply add this method to your project:


    For more details on the Integration Verification tool navigate to this article.

    Done! You just integrated the ironSource SDK in your app. 
    You are now ready to start working with Ad Units and Mediation Tools.

    What’s Next?
    1. Follow our integration guides and implement our Ad Units:
      Rewarded Video
      Banner Mediation
    2. Interested in Mediation? Integrate our Rewarded Video, Interstitial or Banner Ads in your app and follow our Mediation articles.
    3. Verify your integration with the Integration Helper.
    You can read this article in: