Integrate maio with mediation

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

The dashboard interface for maio uses Japanese text for its labels, buttons, and descriptions, and the screenshots in this guide have not been translated. In this guide's descriptions and instructions however, labels and buttons are referenced with their English language equivalents. "URL スキーム," for example, is "URL Scheme".

Supported integrations and ad formats

The mediation adapter for maio has the following capabilities:

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded
Native

Requirements

• Android API level 21 or higher

• maio SDK 1.0.7 or higher

• Latest Google Mobile Ads SDK

• Complete the mediation Get started guide

Step 1: Set up configurations in maio UI

First, sign up or log in to your maio account. Click the Application management button on the left sidebar and click on New app.

Select the tab corresponding to your preferred Ad Type.

Interstitial

Enter the Name of your app, select the platform and provide your App URL. Select Video interstitial as the Ad Type, and then click Update.

Note: Interstitial ads from maio are skippable by default.

Rewarded

Enter the Name of your app, select the platform and provide your App URL. Select Video Rewards as the Ad Type, and then click Update.

Note: Rewarded Video ads from maio are NOT skippable by default.

In the Application Management page, make a note of the Media ID. It's needed to set up your AdMob ad unit in the next section.

In the Zone Management page, make a note of the Zone ID. It will also be needed to set up your AdMob ad unit in the next section.

In addition to Media ID and Zone ID, you will need API ID and API KEY to set up your ad unit ID for mediation. In Reporting API page, make a note of API ID and API KEY.

Note: If this is your first time setting up your maio account, you may need to contact maio's support team in order for your API ID and API KEY to be issued to you.

Step 2: Set up maio demand in AdMob UI

Configure mediation settings for your ad unit

You need to add maio to the mediation configuration for your ad unit.

First, sign in to your AdMob account. Next, navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add maio as an ad source.

To create a new mediation group, select Create Mediation Group.

Enter your ad format and platform, then click Continue.

Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled, and then click Add Ad Units.

Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.

You should now see the ad units card populated with the ad units you selected:

Add maio as an ad source

Under the Waterfall card in the Ad Sources section, select Add Ad Source. Then select maio.

Select maio and enable the Optimize switch. Enter the API ID and API KEY obtained in the previous section to set up ad source optimization for maio. Then enter an eCPM value for maio and click Continue.

Note: You only need to set up ad source optimization once per network.

If you already have a mapping for maio, you can select it. Otherwise, click Add mapping.

Next, enter the Media ID and Zone ID obtained in the previous section. Then click Done.

Important: The Media ID must be associated with the targeted app as in the maio UI.

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

Step 3: Import the maio SDK and adapter

Note: Failure to integrate the compatible maio and Google Mobile Ads SDK versions might lead to build issues.

Android Studio integration (recommended)

In your project-level settings.gradle.kts file, add the following repositories:

dependencyResolutionManagement {
  repositories {
    google()
    mavenCentral()
    maven {
      url = uri("https://imobile-maio.github.io/maven")
    }
  }
}

Then, in your app-level build.gradle.kts file, add the following implementation dependencies and configurations. Use the latest versions of the maio SDK and adapter:

dependencies {
    implementation("com.google.android.gms:play-services-ads:23.5.0")
    implementation("com.google.ads.mediation:maio:1.1.16.3")
}

Manual integration

• Download the latest version of maio Android SDK and add it to your project.
• Navigate to the maio adapter artifacts on Google's Maven Repository. Select the latest version, download the maio adapter's `.aar' file, and add it to your project.

Step 4: Add required code

No additional code is required for maio Android integration.

Step 5: Test your implementation

Enable test ads

Make sure you register your test device for AdMob.

Publishers using version 11.6.0 or higher of the Google Mobile Ads SDK will automatically receive test ads from maio on phones and tablets registered as test devices when making requests.

Important: Disable test mode for AdMob and maio before releasing your app.

Verify test ads

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

Error codes

If the adapter fails to receive an ad from maio, publishers can check the underlying error from the ad response using ResponseInfo.getAdapterResponses() under the following classes:

Format	Class name
Interstitial	jp.maio.sdk.android.mediation.admob.adapter.Interstitial
Rewarded	jp.maio.sdk.android.mediation.admob.adapter.Rewarded

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

Error code	Reason
0-10	maio returned an SDK-specific error. See code and maio's documentation for more details.
101	Maio does not have an ad available.
102	Invalid server parameters (e.g. missing Placement ID).
103	Context used to load an ad was not an `Activity` instance.

maio Android Mediation Adapter Changelog

Version 1.1.16.3

• Updated the minimum required Google Mobile Ads SDK version to 23.0.0.
• Verified compatibility with maio SDK version 1.1.16.

Built and tested with:

• Google Mobile Ads SDK version 23.0.0.
• Maio SDK version 1.1.16.

Version 1.1.16.2

• Updated adapter to use new VersionInfo class.
• Updated the minimum required Google Mobile Ads SDK version to 22.0.0.

Built and tested with:

• Google Mobile Ads SDK version 22.0.0.
• Maio SDK version 1.1.16.

Version 1.1.16.1

• Updated compileSdkVersion and targetSdkVersion to API 31.
• Updated the minimum required Google Mobile Ads SDK version to 21.0.0.
• Updated the minimum required Android API level to 19.

Built and tested with:

• Google Mobile Ads SDK version 21.0.0.
• Maio SDK version 1.1.16.

Version 1.1.16.0

• Updated error codes to capture additional maio errors.
• Verified compatibility with maio SDK version 1.1.16.
• Updated the minimum required Google Mobile Ads SDK version to 20.4.0.

Built and tested with:

• Google Mobile Ads SDK version 20.4.0.
• Maio SDK version 1.1.16.

Version 1.1.15.0

• Verified compatibility with maio SDK version 1.1.15.
• Updated the minimum required Google Mobile Ads SDK version to 20.0.0.

Built and tested with:

• Google Mobile Ads SDK version 20.0.0.
• Maio SDK version 1.1.15.

Version 1.1.14.0

• Added standardized adapter error codes and messages.
• Verified compatibility with maio SDK version 1.1.14.
• Updated the minimum required Google Mobile Ads SDK version to 19.8.0.

Built and tested with:

• Google Mobile Ads SDK version 19.8.0.
• Maio SDK version 1.1.14.

Version 1.1.13.0

• Verified compatibility with maio SDK version 1.1.13.
• Updated the minimum required Google Mobile Ads SDK version to 19.5.0.

Built and tested with:

• Google Mobile Ads SDK version 19.5.0.
• Maio SDK version 1.1.13.

Version 1.1.12.0

• Updated the minimum required Google Mobile Ads SDK version to 19.4.0.

Built and tested with:

• Google Mobile Ads SDK version 19.4.0.
• Maio SDK version 1.1.12.

Version 1.1.11.1

• To limit timouts, ad requests will now immediately fail if maio does not have an ad ready to be shown.
• Updated the minimum required Google Mobile Ads SDK version to 19.1.0.

Built and tested with:

• Google Mobile Ads SDK version 19.1.0.
• Maio SDK version 1.1.11.

Version 1.1.11.0

• Verified compatibility with maio SDK version 1.1.11.
• Updated the minimum required Google Mobile Ads SDK version to 18.3.0.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Maio SDK version 1.1.11.

Version 1.1.10.0

• Verified compatibility with maio SDK version 1.1.10.
• Updated the minimum required Google Mobile Ads SDK version to 18.2.0.

Version 1.1.8.0

• Verified compatibility with maio SDK version 1.1.8.
• Updated the minimum required Google Mobile Ads SDK version to 18.1.0.

Version 1.1.7.0

• Bug Fixes.
• Verified compatibility with maio SDK version 1.1.7.

Version 1.1.6.1

• Updated adapter to support new Rewarded API.
• Updated the minimum required Google Mobile Ads SDK version to 17.2.0.

Version 1.1.6.0

• Verified compatibility with maio SDK version 1.1.6.

Version 1.1.5.0

• Verified compatibility with maio SDK version 1.1.5.

Version 1.1.4.0

• Verified compatibility with maio SDK version 1.1.4.

Version 1.1.3.1

• Updated the adapter to work with instance class instead of singleton.

Version 1.1.3.0

• Verified compatibility with maio SDK version 1.1.3.

Version 1.1.2.1

• Updated the adapter with updated initialize functions.

Version 1.1.2.0

• Verified compatibility with maio SDK version 1.1.2.

Version 1.1.1.1

• Updated the adapter to invoke the onRewardedVideoComplete() ad event.

Version 1.1.1.0

• Verified compatibility with maio SDK version 1.1.1.

Version 1.1.0.0

• Verified compatibility with maio SDK version 1.1.0.

Version 1.0.8.0

• Verified compatibility with maio SDK version 1.0.8.

Version 1.0.7.1

• Fixed an issue that could cause NullPointerExceptions to occur when ads fail to load.

Version 1.0.7.0

• Added ability to enable test mode by adding test device id to AdRequest.
• Verified compatibility with maio SDK version 1.0.7.

Version 1.0.6.0

• First release!
• Added support for interstitials and rewarded video ads.