Google Ad Manager integration guide

Follow these instructions to set Google Ad Manager live as an ad network on the ironSource mediation platform.

Before you start Make sure you have correctly integrated ironSource’s interstitial, rewarded video or banner mediation in your application.

Google Ad Manager ads are served using the AdMob SDK.


Step 1. Create a Google Ad Manager account

To access Google Ad Manager ad inventory through ironSource‘s mediation platform, create an Ad Manager account.

Step 2. Create an application and ad units in Google Ad Manager

Add your app and set up Ad units in your Ad Manager account. You can find all the information you need here.

Step 3. Activate Google Ad Manager in your ironSource account

Sign in to your Google account when setting up Ad Manager on the ironSource SDK Networks Setup page. This will ensure that all of the necessary parameters to run Ad Manager’s interstitials, rewarded videos, and banners will be automatically retrieved.

  1. In your Google Ad Manager account, obtain the following information
App ID The unique ID assigned to your app on the Ad Manager dashboard
API Key The unique identifier for your Ad Manager account. This allows the ironSource Mediation Platform to import performance data from your Ad Manager account to use in reporting and optimization
Ad Unit ID The unique ID assigned to your app’s ad unit on the Ad Manager dashboard
Client ID The unique identifier that specifies the relationship between your account and the ad unit
Client Secret The unique identifier that specifies the relationship between your account and the ad unit
Refresh Token The refresh token the client application already received

     2. Configure Google Ad Manager’s parameters in your ironSource account.

  • Log in to your ironSource account and go to ‘Monetize‘ ➣ ‘SETUP‘ ➣ ‘SDK Networks‘.

  • Select Google Ad Manager from the list of Available Networks and enter the Ad Manager’s API Key, Client ID, Client Secret, and Refresh Token; or click the Login with Google option.

     Login with Google

  Click Save. Ad Manager will be enabled and listed in the Available Ad Networks table.

  • Select the app on which you’d like to run ironSource’s Mediation with Ad Manager.
  • Select Ad Manager from the setup list of ad networks and click on the tool Define button. Insert the App ID and Ad Unit ID  under interstitial, rewarded video or banner settings.

           

  • Verify your integration with the Reporting API. This column will check your integration through the Reporting API and return three possible responses: Verified, Failed, and No Response. If you do not see Verified, double check your integration and the information you entered, then click Retry until you see Verified.

Step 4. Add the Admob Adapter to Your Build

Important!

As of V17.0.0 (Adapter version 4.3.1 onwards), AdMob’s SDK requires publishers to add their AdMob App ID to the app’s AndroidManifest as a child of the <application/>tag:

<meta-data android:name="com.google.android.gms.ads.APPLICATION_ID" 
           android:value="[ADMOB_APP_ID]"/>

Replace the “[ADMOB_APP_ID]” with the APP ID value you retrieve in step 3.

  1. Make sure you have the following lines inside  allprojects->repositories block
    allprojects {
        repositories {
           flatDir {
               dirs 'libs'
           }
           google()
        }
    }
  2. Add the following dependency into the dependencies block
    dependencies {
        implementation fileTree(dir: 'libs', include: ['*.jar'])
    }

ironSource supports both Gradle dependencies and manual download mechanisms.

To integrate the Admob Adapter with Gradle:

      1. Make sure the following Maven URL exist in your build.gradle script of your app module (should appear only once for all the adapters).
        repositories {
            google()
            maven {
                url "https://android-sdk.is.com/"
            }
        }
        
      2. Add the adapter’s Maven name to your build.gradle script of your app module:
        implementation 'com.google.android.gms:play-services-ads:20.2.0'
        implementation (project(':admobadapter-4.3.22'))

To integrate the Admob Adapter through Manual Download:

      1. Download the Admob Adapter:
        Add the Admob Adapter to your build. You can find the latest Admob Adapter here.
        Important! The Admob Adapter Does not contain the Admob SDK. You need to additionally add the Admob SDK directly.
      2. Add the Admob Adapter to your Project:
        After you download the Adapter; drop the Admob Adapter jar into the libs folder in your Android Project.
        Supersonic Mediation Drop Libs
      3. Make sure you add the following to your Gradle build file under the dependencies section:
        implementation 'com.google.android.gms:play-services-ads:20.2.0'
        implementation (project(':admobadapter-4.3.22'))

Step 5. Update AndroidManifest.xml

As of ironSource Android SDK Version 6.17.0 (AdMov Android adapter version 4.3.10+), AdMob adapter will be released as AAR. Only if you intend to keep your Jar integration, please add the manifest.

Manifest Permissions:

<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>

Manifest Activities:
Add the following activities inside the <application> tag on your manifestAdditions:

<activity android:name="com.google.android.gms.ads.AdActivity"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize" android:theme="@android:style/Theme.Translucent" />

As of V17.0.0 (Adapter version 4.3.1 onwards), AdMob’s SDK requires publishers to add their AdMob App ID to the app’s AndroidManifest as a child of the <application></application> tag:

<meta-data android:name="com.google.android.gms.ads.APPLICATION_ID"
           android:value="[ADMOB_APP_ID]"/>

Replace the “[ADMOB_APP_ID]” with the APP ID value you retrieved in step 3.
Not doing so results in crashes originated with AdMob’s SDK. For more information please refer to AdMob’s guide.

Step 6. Additional Steps

Child-directed setting – COPPA

ironSource’s mediation platform lets publishers communicate AdMob Child-directed settings directly to the AdMob network.
This feature is enabled using ironSource SDK 6.14.0+, AdMob Android Adapter 4.3.9+.

Use the following syntax, to set AdMob setTagForChildDirectedTreatment with the parameter TAG_FOR_CHILD_DIRECTED_TREATMENT_TRUE:

 IronSource.setMetaData("AdMob_TFCD","true");

Use the following syntax, to set AdMob setTagForChildDirectedTreatment with the parameter TAG_FOR_CHILD_DIRECTED_TREATMENT_FALSE:

 IronSource.setMetaData("AdMob_TFCD","false");

To learn more about Child-directed settings Under AdMob network visit here.
here.

ironSource’s mediation platform lets publishers communicate with AdMob network, a Tag For Users under the Age of Consent in Europe (TFUA) request.
This feature is enabled using ironSource SDK 6.14.0+, AdMob Android Adapter 4.3.9+.

Use the following syntax, to set setTagForUnderAgeOfConsent with TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE:

 IronSource.setMetaData("AdMob_TFUA","true");

Use the following syntax, to set setTagForUnderAgeOfConsent with TAG_FOR_UNDER_AGE_OF_CONSENT_FALSE:

 IronSource.setMetaData("AdMob_TFUA","false");

To learn more about Child-directed settings Under AdMob network visit here.
here.

Note:

Verify Your Ad Network Integration

The ironSource SDK provides an easy way to verify that your mediation integration was completed successfully. To verify your ironSource and additional Ad Networks’ integration, follow this document.

Done!
You are now all set to deliver Admob Ads within your application!


What’s Next?

To leverage additional mediation ad networks, integrate the adapters and follow our integration guides.