Integrate i-mobile with mediation

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from i-mobile using mediation, covering waterfall integrations. It covers how to add i-mobile to an ad unit's mediation configuration, and how to integrate the i-mobile SDK and adapter into a Unity app.

The dashboard interface for i-mobile uses Japanese text for its labels, buttons, and descriptions. The screenshots in this guide have not been translated. In this guide's descriptions and instructions however, labels and buttons are translated with their English language equivalents in parentheses.

Supported integrations and ad formats

The AdMob mediation adapter for i-mobile has the following capabilities:

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded

Requirements

  • Unity 5.6 or higher
  • Latest Google Mobile Ads SDK
  • To deploy on Android
    • Android API level 21 or higher
  • To deploy on iOS
    • iOS deployment target of 12.0 or higher
  • A working Unity project configured with Google Mobile Ads SDK. See Get Started for details.
  • Complete the mediation Get started guide

Step 1: Set up configurations in i-mobile UI

Sign up or log in to your i-mobile account.

Add your app to the i-mobile dashboard by clicking the サイト／アプリ管理 (Site/Application Management) tab and the button for your app's platform.

Android

iOS

Fill out the form and click the 新規登録 (Sign up) button.

Android

iOS

To create a new Advertising Spot, select your app under the サイト／アプリ管理 (Site/Application Management) tab.

Android

iOS

Navigate to the 広告スポット管理 (Ad Spot Management) tab and click the 新規広告スポット (New Ad Spot) button.

create_ad_spot

Next, fill out the form by providing the 広告スポット名 (Ad Spot name), 広告スポットサイズ (Ad Spot size) and other details. Then, click the 新規登録 (Sign up) button.

new_ad_spot_form

Your new Ad spot is ready. To view its integration details, click the アプリ設定取得 (Get App settings) button.

ad_spot_list

Take note of the パブリッシャーID (Publisher ID), メディアID (Media ID), and スポットID (Spot ID). You'll need these parameters later when configuring i-mobile for mediation in the AdMob UI.

Android

iOS

Step 2: Set up i-mobile demand in AdMob UI

Configure mediation settings for your ad unit

Android

For instructions, see step 2 in the guide for Android.

iOS

For instructions, see step 2 in the guide for iOS.

Step 3: Import the i-mobile SDK and adapter

OpenUPM-CLI

If you have OpenUPM-CLI installed, you can install the Google Mobile Ads i-mobile Mediation Plugin for Unity to your project by running the following command from your project's root directory:

openupm add com.google.ads.mobile.mediation.imobile

OpenUPM

In your Unity project editor, select Edit > Project Settings > Package Manager to open the Unity Package Manager Settings.

Under the Scoped Registries tab, add OpenUPM as a scoped registry with the following details:

  • Name: OpenUPM
  • URL: https://package.openupm.com
  • Scope(s): com.google

OpenUPM Details

Then, navigate to Window > Package Manager to open the Unity Package Manager and select My Registries from the drop-down menu.

Unity Registries

Select the Google Mobile Ads i-mobile Mediation package and click Install.

Install from OpenUPM

Unity Package

Download the latest version of Google Mobile Ads mediation plugin for i-mobile from the download link in the Changelog and extract the GoogleMobileAdsIMobileMediation.unitypackage from the zip file.

In your Unity project editor, select Assets > Import Package > Custom Package and find the GoogleMobileAdsIMobileMediation.unitypackage file you downloaded. Make sure that all the files are selected and click Import.

Import from Unity

Then, select Assets > External Dependency Manager > Android Resolver > Force Resolve. The External Dependency Manager library will perform dependency resolution from scratch and copy the declared dependencies into the Assets/Plugins/Android directory of your Unity app.

Force Resolve

Step 4: Additional code required

Android

No additional code is required i-mobile integration.

iOS

SKAdNetwork integration

Follow i-mobile's documentation to add the SKAdNetwork identifiers to your project's Info.plist file.

Step 5: Test your implementation

Enable test ads

Make sure you register your test device for AdMob. i-mobile provides test Spot ID, Media ID, and Publisher ID for testing, you can find them here.

Verify test ads

To verify that you are receiving test ads from i-mobile, enable single ad source testing in ad inspector using the i-mobile (Waterfall) ad source(s).

Error codes

If the adapter fails to receive an ad from i-mobile, publishers can check the underlying error from the ad response using ResponseInfo under the following classes:

Android

Format Class name
Banner com.google.ads.mediation.imobile.IMobileAdapter
Interstitial com.google.ads.mediation.imobile.IMobileAdapter
Native com.google.ads.mediation.imobile.IMobileMediationAdapter

iOS

Format Class name
Banner IMobileAdapter
Interstitial IMobileAdapter
Native GADMediationAdapterIMobile

Here are the codes and accompanying messages thrown by the i-mobile adapter when an ad fails to load:

Android

Error code Reason
0-99 i-mobile SDK returned an error. See code for more details.
101 i-mobile requires an Activity context to load ads.
102 i-mobile server parameters configured in the AdMob UI are missing or invalid.
103 The requested ad size does not match an i-mobile supported banner size.
104 i-mobile's native ad load success callback returned an empty native ads list.

iOS

Error code Reason
0-10 i-mobile SDK returned an error. See code for more details.
101 i-mobile server parameters configured in the AdMob UI are missing or invalid.
102 The requested ad size does not match an i-mobile supported banner size.
103 i-mobile failed to present an ad.
104 i-mobile returned an empty native ad array.
105 i-mobile failed to download native ad assets.
106 i-mobile does not support requesting for multiple interstitial ads using the same Spot ID.

i-mobile Unity Mediation Plugin Changelog

Version 1.3.6

Version 1.3.5

Version 1.3.4

Version 1.3.3

Version 1.3.2

Version 1.3.1

Version 1.3.0

Version 1.2.2

Version 1.2.1

Version 1.2.0

Version 1.1.0

Version 1.0.2

Version 1.0.1

Version 1.0.0