Integrate Mintegral with AdMob Mediation

This guide shows you how to use Google Mobile Ads SDK for React Native 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 React Native app.

Supported integrations and ad formats

The AdMob mediation adapter for Mintegral has the following capabilities:

Integration
Bidding
Waterfall
Formats
App Open
Banner
Interstitial
Rewarded
Rewarded Interstitial
Native

Prerequisites

Before you continue, verify the following:

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 Waterfall 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.

Update your app-ads.txt

Authorized Sellers for Apps app-ads.txt is an IAB Tech Lab initiative that helps ensure your app ad inventory is only sold through channels you've identified as authorized. To prevent a significant loss in ad revenue, you'll need to implement an app-ads.txt file. If you haven't done so already, set up an app-ads.txt file for your app.

To implement app-ads.txt for Mintegral, see How app-Ads.txt Can Help Fight Ad Fraud.

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 Mobvista/Mintegral to GDPR and US state regulations ad partners list

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

Step 3: Import the Mintegral SDK and adapter

In your project's root directory, install the Google Mobile Ads SDK for React Native mediation adapter for Mintegral. Complete the following:

  1. Copy the Google Mobile Ads SDK for React Native adapter tar file from the gma-sdk-react-native/adapters/mintegral/ directory into your project's local_packages/ directory. If you don't have the adapters folder, see Prerequisites.

    mkdir -p local_packages
cp EXTRACT_DIR/gma-sdk-react-native/adapters/mintegral/gma-mediation-mintegral-0.1.0.tgz local_packages/

    Replace EXTRACT_DIR with the path to the directory where you extracted the archive.

  2. Install the adapter package using your preferred package manager:

    npm

    npm install ./local_packages/gma-mediation-mintegral-0.1.0.tgz

    yarn

    yarn add ./local_packages/gma-mediation-mintegral-0.1.0.tgz

  3. If you're building for Android, add the following repository to the build.gradle file in your project's android directory:

    repositories {
    google()
    mavenCentral()
    maven {
        url = uri("https://dl-maven-android.mintegral.com/repository/mbridge_android_sdk_oversea")
    }
}

Step 4: Implement privacy settings on Mintegral SDK

To comply with the Google EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA), the UK, and Switzerland, and obtain their consent for the use of cookies or other local storage where legally required, and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). You are responsible for verifying that consent is propagated to each ad source in your mediation chain.

Mintegral React Native adapter version 0.1.0 and later supports passing GDPR consent signals from consent management platforms that integrate with IAB's Transparency and Consent Framework (TCF) to Mintegral SDK. For more information, see Mintegral's Android and iOS SDK Privacy Compliance Statement documentation.

Step 5: 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 6: 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, you 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
100 com.mbridge.msdk The Mintegral SDK returned a failure callback.
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.
105 com.mbridge.msdk Mintegral SDK failed to initialize.
106 com.google.ads.mediation.mintegral An ad for the Mintegral slot is already loaded and is yet to be shown.

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.

Version 0.1.0

  • Initial release.