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 an iOS 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
Native  1  2
1 Waterfall integration for this format is in closed beta.

2 Bidding integration for this format is in closed beta.

Requirements

  • iOS deployment target of 11.0 or higher

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.

Take note of your application's APP ID.

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.

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.

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

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

You need to add Mintegral 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 Mintegral 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 Mintegral as an ad source

Bidding

Under the Bidding card in the Ad Sources section, select Add Ad Source. Then select Mintegral.

Click How to sign a partnership agreement and set up a bidding partnership with Mintegral.

Click Acknowledge & agree, then click Continue.

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

Next, enter the App Key, App ID, Placement ID, and Ad Unit ID obtained in the previous section. Then click Done.

Important: The App ID and App Key must be associated with the targeted app as in the Mintegral UI.

Waterfall

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

Select Mintegral. Then enter an eCPM value for Mintegral and click Continue.

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

Next, enter the App Key, App ID, Placement ID, and Ad Unit ID obtained in the previous section. Then click Done.

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

  • Add the following line to your project's Podfile:

    pod 'GoogleMobileAdsMediationMintegral'
    
  • From the command line run:

    pod install --repo-update

Manual integration

  • Download the latest version of the Mintegral SDK for iOS and link all the .framework files and bundles in your project.
  • Download the latest version of the Mintegral adapter from the download link in the Changelog and link MintegralAdapter.xcframework in your project.

Step 4: Implement privacy settings on Mintegral SDK

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 Mintegral SDK includes the setConsentStatus method to pass consent information to the Mintegral SDK.

The following sample code shows how to pass consent information to the Mintegral SDK. These options must be set before you initialize the Google Mobile Ads SDK to ensure they get forwarded properly to the Mintegral SDK.

Swift

import MTGSDK
// ...

MTGSDK.sharedInstance().setConsentStatus(true)

Objective-C

#import <MTGSDK/MTGSDK.h>
// ...

[[MTGSDK sharedInstance] setConsentStatus:YES];

See Mintegral's privacy documentation for more information.

US states privacy laws

U.S. states privacy laws require giving users the right to opt out of the "sale" of their "personal information" (as the law defines those terms), with the opt-out offered via a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The U.S. states privacy laws compliance guide offers the ability to enable restricted data processing for Google ad serving, but Google is unable to apply this setting to each ad network in your mediation chain. Therefore, you must identify each ad network in your mediation chain that may participate in the sale of personal information and follow guidance from each of those networks to ensure compliance.

The Mintegral SDK includes setDoNotTrackStatus method to pass consent information to the Mintegral SDK.

The following sample code shows how to pass consent information to the Mintegral SDK. If you need to call this method, call it before initializing the Google Mobile Ads SDK to ensure they get forwarded properly to the Mintegral SDK.

Swift

import MTGSDK
// ...

MTGSDK.sharedInstance().setDoNotTrackStatus(false)

Objective-C

#import <MTGSDK/MTGSDK.h>
// ...

[[MTGSDK sharedInstance] setDoNotTrackStatus:NO];

See Mintegral's Privacy documentation for more information.

Step 5: Add required code

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

Optional steps

Add Mintegral to CCPA ad partners list

Follow the steps in CCPA settings to add Mintegral to the CCPA ad partners list in the AdMob UI.

Native ads

Ad rendering

The Mintegral adapter returns its native ads as GADNativeAd objects. It populates the following fields for a GADNativeAd.

Field Assets always included by Mintegral adapter
Headline
Image 1
Body
Icon
Call to action
Star rating
Store
Price
Advertiser

1 The Mintegral adapter does not provide direct access to the main image asset for its native ads. Instead, the adapter populates the GADMediaView with a video or an image.

Error codes

If the adapter fails to receive an ad from Mintegral, you can check the underlying error from the ad response using GADResponseInfo.adNetworkInfoArray under the following classes:

GADMediationAdapterMintegral

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

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 iOS Mediation Adapter Changelog

Next version

  • Included Info.plist in the frameworks in MintegralAdapter.xcframework.

Version 7.5.6.0

  • Verified compatibility with Mintegral SDK version 7.5.6.
  • Made GADMediationAdapterMintegral.h a public header.

Built and tested with:

  • Google Mobile Ads SDK version 11.0.0.
  • Mintegral SDK version 7.5.6.

Version 7.5.3.0

  • Verified compatibility with Mintegral SDK version 7.5.3.

Built and tested with:

  • Google Mobile Ads SDK version 10.14.0.
  • Mintegral SDK version 7.5.3.

Version 7.4.8.0

  • Verified compatibility with Mintegral SDK version 7.4.8.

Built and tested with:

  • Google Mobile Ads SDK version 10.13.0.
  • Mintegral SDK version 7.4.8.

Version 7.4.7.0

  • Updated the podspec file to depend on MintegralAdSDK/All instead of MintegralAdSDK.
  • Verified compatibility with Mintegral SDK version 7.4.7.
  • Added waterfall support for app open ad format.

Built and tested with:

  • Google Mobile Ads SDK version 10.12.0.
  • Mintegral SDK version 7.4.7.

Version 7.4.4.0

  • Added watermark support for bidding ads.
  • Verified compatibility with Mintegral SDK version 7.4.4.

Built and tested with:

  • Google Mobile Ads SDK version 10.10.0.
  • Mintegral SDK version 7.4.4.

Version 7.4.3.0

  • Verified compatibility with Mintegral SDK version 7.4.3.

Built and tested with:

  • Google Mobile Ads SDK version 10.9.0.
  • Mintegral SDK version 7.4.3.

Version 7.4.1.0

  • Verified compatibility with Mintegral SDK version 7.4.1.

Built and tested with:

  • Google Mobile Ads SDK version 10.7.0.
  • Mintegral SDK version 7.4.1.

Version 7.3.9.0

  • Verified compatibility with Mintegral SDK version 7.3.9.

Built and tested with:

  • Google Mobile Ads SDK version 10.7.0.
  • Mintegral SDK version 7.3.9.

Version 7.3.8.0

  • Verified compatibility with Mintegral SDK version 7.3.8.

Built and tested with:

  • Google Mobile Ads SDK version 10.6.0.
  • Mintegral SDK version 7.3.8.

Version 7.3.7.0

  • Verified compatibility with Mintegral SDK version 7.3.7.

Built and tested with:

  • Google Mobile Ads SDK version 10.5.0.
  • Mintegral SDK version 7.3.7.

Version 7.3.6.0

  • Verified compatibility with Mintegral SDK version 7.3.6.
  • Removed support of the armv7 architecture.
  • Now requires minimum iOS version 11.0.
  • Now requires Google Mobile Ads SDK version 10.4.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 10.5.0.
  • Mintegral SDK version 7.3.6.

Version 7.3.4.0

  • Verified compatibility with Mintegral SDK version 7.3.4.

Built and tested with:

  • Google Mobile Ads SDK version 10.2.0.
  • Mintegral SDK version 7.3.4.

Version 7.3.3.0

  • Verified compatibility with Mintegral SDK version 7.3.3.

Built and tested with:

  • Google Mobile Ads SDK version 10.2.0.
  • Mintegral SDK version 7.3.3.

Version 7.3.0.0

  • Verified compatibility with Mintegral SDK version 7.3.0.

Built and tested with:

  • Google Mobile Ads SDK version 10.1.0.
  • Mintegral SDK version 7.3.0.

Version 7.2.9.1

  • Added waterfall support for banner (includes MREC), interstitial, rewarded and native ad formats.
  • Requires Google Mobile Ads SDK version 10.0.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 10.0.0.
  • Mintegral SDK version 7.2.9.

Version 7.2.9.0

  • Verified compatibility with Mintegral SDK version 7.2.9.

Built and tested with:

  • Google Mobile Ads SDK version 9.14.0.
  • Mintegral SDK version 7.2.9.

Version 7.2.8.0

  • Verified compatibility with Mintegral SDK version 7.2.8.

Built and tested with:

  • Google Mobile Ads SDK version 9.14.0.
  • Mintegral SDK version 7.2.8.

Version 7.2.6.0

  • Initial release!
  • Added bidding support for banner (includes MREC), interstitial, rewarded and native ad formats.
  • Verified compatibility with Mintegral SDK version 7.2.6.
  • Requires Google Mobile Ads SDK version 9.8.0 or higher.

Built and tested with:

  • Google Mobile Ads SDK version 9.13.0.
  • Mintegral SDK version 7.2.6.