Integrate Mintegral with mediation

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

Supported integrations and ad formats

The AdMob mediation adapter for Mintegral has the following capabilities:

Integration
Bidding
Waterfall
Formats
App Open  1  2
Banner
Interstitial
Rewarded
Rewarded Interstitial
1 Waterfall integration for this format is in closed beta.

2 Bidding integration for this format is in closed beta.

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 the Google Mobile Ads SDK. See Get Started for details.
  • Complete the mediation Get started guide

Step 1: Set up configurations in Mintegral UI

Sign up or Log in to your Mintegral account.

Locate the App Key

Navigate to the APP Setting tab and take note of the APP Key.

Add a new application

From the APP Setting tab, click the Add APP button.

Select the Platform and fill out the rest of the form. Then, click Save.

Android

iOS

Take note of your application's APP ID.

Android

iOS

Create an ad placement

Once your application has been created, navigate to the Placements & Units tab and click on the Add Placement button as shown below to create your ad placement.

Android

iOS

Enter a Placement Name and AD Format.

Bidding

Select Header Bidding as the Bidding Type. Fill out the rest of the form and click Save.

Waterfall

Select Traditional as the Bidding Type. Fill out the rest of the form and click Save.

Once your ad placement is created, take note of the Placement ID.

Android

iOS

Click the 1 AD Units drop down and take note of the AD Unit ID.

Android

iOS

Locate your Mintegral Reporting API Key

Bidding

This step isn't required for bidding integrations.

Waterfall

You will need your Mintegral Reporting API Key for setting up your AdMob ad unit ID. Navigate to Account > API Tools. Take note of your Skey and Secret.

Step 2: Set up Mintegral 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.

Add Mintegral to GDPR and US state regulations ad partners list

Follow the steps in GDPR settings and US state regulations settings to add Mintegral to the GDPR and US state regulations ad partners list in the AdMob UI.

Step 3: Import the Mintegral SDK and adapter

Download the latest version of Google Mobile Ads mediation plugin for Mintegral from the download link in the Changelog and extract the GoogleMobileAdsMintegralMediation.unitypackage from the zip file.

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

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

Step 4: Add required code

Android

No additional code is required for Mintegral integration.

iOS

SKAdNetwork integration

Follow Mintegral'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.

To get Mintegral test ads for banners, interstitials, rewarded and native ad formats, Mintegral recommends using the App Keys, App IDs, Placement IDs and Ad Unit IDs provided in the Mintegral Test ID page.

Verify test ads

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

Error codes

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

Android

com.mbridge.msdk
com.google.ads.mediation.mintegral.MintegralMediationAdapter

iOS

GADMediationAdapterMintegral

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

Android

Error code Domain Reason
101 com.google.ads.mediation.mintegral Invalid server parameters (e.g. Missing app ID or placement ID).
102 com.google.ads.mediation.mintegral The requested ad size does not match a Mintegral supported banner size.
103 com.google.ads.mediation.mintegral Missing or invalid bid response.
104 com.google.ads.mediation.mintegral Mintegral SDK returned a no fill error.

iOS

Error code Domain Reason
101 com.google.mediation.mintegral Invalid server parameters (e.g. Missing app ID or placement ID).
102 com.google.mediation.mintegral Mintegral SDK returned a no fill error.
103 com.google.mediation.mintegral Mintegral SDK failed to show an ad.
104 com.google.mediation.mintegral The requested ad size does not match a Mintegral supported banner size.

Mintegral Unity Mediation Plugin Changelog

Version 1.5.0

Version 1.4.0

Version 1.3.0

Version 1.2.1

Version 1.2.0

Version 1.1.0

Version 1.0.0