Integrating IronSource Mediation

This guide is intended for publishers who want to use the Google Mobile Ads SDK
to load and display ads from IronSource through
mediation.
It covers how to add IronSource to an ad unit's mediation configuration, how to
set up ad network optimization, and how to integrate the IronSource SDK and
adapter into your Android app.

Supported formats and features

The AdMob mediation adapter for IronSource has the
following capabilities:

Enter app details

If your app is not available, select
App Not Live in the Application Store and provide a
Temporary Name for your app. Select Android
as platform and click Add App.

Take note of your new App Key, which is displayed after the app has been
added. You will need this value for setting up your
AdMob ad unit ID. Select the ad formats your app
supports in the appropriate Live tabs. Then click Done.

Add IronSource as an ad source

Next, enable the Optimize feature, then enter the User Name and
Secret Key obtained in previous section to set up ANO for IronSource.
Then enter an eCPM value and click Continue.

Enter the App Key and Instance ID obtained in the previous
section.

Note: Ad network optimization takes a few days to gather data to accurately
calculate eCPM for a mediation network. In the meantime, the ANO status will be
PENDING, so you must manually set an eCPM value for the network. Once the eCPM
can be calculated, ANO will automatically start updating the eCPM on your
behalf.

Using rewarded video ads

In the settings for your rewarded video ad unit, provide values for the reward
amount and reward type. Then, to ensure you provide the same reward to the user
no matter which ad network is served, check the
Apply to all networks in Mediation
groups box.

If you don't apply this setting, the IronSource adapter passes back the reward
specified in the IronSource dashboard when creating the placement.

For more information on setting reward values for AdMob ad units, see
Create an ad unit.

Step 3: Import the IronSource SDK and adapter

Android Studio Integration (recommended)

Add the following IronSource Maven repository and implementation dependency with
the latest version of the IronSource SDK and adapter in the app-level
build.gradle file:

Step 5: Test your implementation

Navigate to the MONETIZE tab and click the Testing button. Next, click
the New Test Device button.

Enter the Device Name and Advertising ID (from the previous step).
Then click Save.

The newly added test device is listed under TEST DEVICES. You can activate
or deactivate Test Ads in this module as required.

Optional steps

EU consent and GDPR

Under the Google EU User Consent
Policy, you must ensure that certain disclosures are given to, and
consents obtained from, users in the European Economic Area (EEA) regarding
the use of device identifiers and personal data. This policy reflects the
requirements of the EU ePrivacy Directive and the General Data Protection
Regulation (GDPR). When seeking consent, you must identify each ad network
in your mediation chain that may collect, receive, or use personal data and
provide information about each network's use. Google currently is unable to
pass the user's consent choice to such networks automatically.

The section below shows you how to enable or disable personalized ads for
IronSource.

In SDK version 6.7.9, IronSource
added
a consent API. The following sample code sets consent to
true
on the IronSource SDK. If you choose to call this method, it is recommended
that you do so prior to requesting ads via the Google Mobile Ads SDK.