To discuss and provide feedback on our products, join the official Ad Manager Discord channel in the Google Advertising and Measurement Community server.

Integrate Mintegral with bidding (Beta)

This guide shows you how to use 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 mediation adapter for Mintegral has the following capabilities:

Integration

Bidding

Waterfall

Formats

App Open

Banner

Interstitial

Rewarded

Rewarded Interstitial

Native

¹ Bidding integration is in open beta.

Requirements

iOS deployment target of 11.0 or higher
[For bidding]: To integrate all supported ad formats in bidding, use Mintegral adapter 7.5.3.0 or higher ( latest version recommended )

Latest Google Mobile Ads SDK.
Complete the mediation Get started guide .

Step 1: Set up configurations in Mintegral UI

Locate the App Key

Navigate to the APP Settingtab and take note of the APP Key.

Add a new application

From the APP Settingtab, click the Add APPbutton.

Select the Platformand 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 & Unitstab and click on the Add Placementbutton as shown below to create your ad placement.

Enter a Placement Nameand AD Format.

Select Header Biddingas 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 Unitsdrop 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 Ad Manager ad unit ID. Navigate to Account> API Tools. Take note of your Skeyand 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, create an app-ads.txt file for Ad Manager .

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

Step 2: Set up Mintegral demand in Ad Manager UI

Add Mintegral in Companies

Bidding

This step isn't required for bidding integrations.

Waterfall

Navigate to Admin> Companies, then click the New companybutton in the All companiestab. Select Ad network.

Select Mintegralas the Ad network, enter a unique Nameand enable Mediation.

You don't need to enter a Usernameor Password. Click Savewhen done.

Enable secure signal sharing

Bidding

Navigate to Admin> Global settings. Go to the Ad Exchange account settingstab and review and toggle on Secure signal sharing. Click Save.

Waterfall

This step isn't required for waterfall integrations.

Share secure signal on bid requests

Bidding

Navigate to Inventory> Secure Signals. Under Secure signals, search for Mobvista/Mintegral and toggle on Enable app integration.

Click Save.

Waterfall

This step isn't required for waterfall integrations.

Allow secure signal sharing for SDK Bidding

Bidding

Navigate to Delivery> Demand channel settings. In the Default settingstab, toggle on Allow secure signal sharingfor SDK Bidding.

Click Save.

Waterfall

This step isn't required for waterfall integrations.

Configure Mintegral bidding

Bidding

Navigate to Delivery> Bidders, and click Go to SDK Bidding.

Click New bidder.

Select Mintegralas the bidder.

Click Continueto enable SDK Bidding for this bidder.

Click Done.

Waterfall

This step isn't required for waterfall integrations.

Configure ad unit mapping

Bidding

Navigate to Delivery> Bidders, and click Go to SDK Bidding.

Select the company for Mintegral.

Go to the Ad unit mappingtab and click New ad unit mapping.

Choose Specific ad unit. Select an ad unit and format, Mobile appas the Inventory type, and your Mobile application. Then, enter App Key , App ID , Placement ID , and Ad Unit ID obtained in the previous section. Finally, click Save.

Waterfall

Navigate to Delivery> Yield groupsand click the New yield groupbutton. Select your Mobile application.

Scroll down and click Add yield partner.

Select the company you created for Mintegral in the previous section. Choose Mobile SDK mediationas the Integration type, iOSas the Platform, and Activeas the Status.

Enter the App Key , App ID , Placement ID , and Ad Unit ID obtained in the previous section, and the Default CPMvalue. Click Save.

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/Mintegralto the European and US state regulations ad partners list in the Ad Manager UI.

Step 3: Import the Mintegral SDK and adapter

Using CocoaPods (recommended)

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

EU consent and GDPR

To comply with 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 consent is propagated to each ad source in your mediation chain. Google 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 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

US 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 through a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The US 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 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 Ad Manager.

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 Mintegralto the CCPA ad partners list in the Ad Manager 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

¹ 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

Removed size check from the adapter for banner RTB ads.

Version 7.7.9.0

Verified compatibility with Mintegral SDK version 7.7.9.

Built and tested with:

Google Mobile Ads SDK version 12.8.0.
Mintegral SDK version 7.7.9.

Version 7.7.8.0

Added support for COPPA. The adapter now forwards the GADRequestConfiguration.tagForChildDirectedTreatment flag to the Mintegral SDK.
Verified compatibility with Mintegral SDK version 7.7.8.

Built and tested with:

Google Mobile Ads SDK version 12.4.0.
Mintegral SDK version 7.7.8.

Version 7.7.7.0

Verified compatibility with Mintegral SDK version 7.7.7.

Built and tested with:

Google Mobile Ads SDK version 12.0.0.
Mintegral SDK version 7.7.7.

Version 7.7.6.0

Verified compatibility with Mintegral SDK version 7.7.6.

Built and tested with:

Google Mobile Ads SDK version 12.0.0.
Mintegral SDK version 7.7.6.

Version 7.7.5.1

Now requires Google Mobile Ads SDK version 12.0.0 or higher.

Built and tested with:

Google Mobile Ads SDK version 12.0.0.
Mintegral SDK version 7.7.5.

Version 7.7.5.0

Verified compatibility with Mintegral SDK version 7.7.5.

Built and tested with:

Google Mobile Ads SDK version 11.13.0.
Mintegral SDK version 7.7.5.

Version 7.7.4.0

Verified compatibility with Mintegral SDK version 7.7.4.
Updated the adapter to follow Google's Objective-C best practices.

Built and tested with:

Google Mobile Ads SDK version 11.13.0.
Mintegral SDK version 7.7.4.

Version 7.7.3.0

Verified compatibility with Mintegral SDK version 7.7.3.

Built and tested with:

Google Mobile Ads SDK version 11.10.0.
Mintegral SDK version 7.7.3.

Version 7.7.2.1

Adapter no longer checks if interstitial and rewarded ads are ready before they are shown.
Updated CFBundleShortVersionString to have three components instead of four.

Built and tested with:

Google Mobile Ads SDK version 11.10.0.
Mintegral SDK version 7.7.2.

Version 7.7.2.0

Verified compatibility with Mintegral SDK version 7.7.2.

Built and tested with:

Google Mobile Ads SDK version 11.9.0.
Mintegral SDK version 7.7.2.

Version 7.7.1.0

Verified compatibility with Mintegral SDK version 7.7.1.

Built and tested with:

Google Mobile Ads SDK version 11.8.0.
Mintegral SDK version 7.7.1.

Version 7.7.0.0

Verified compatibility with Mintegral SDK version 7.7.0.

Built and tested with:

Google Mobile Ads SDK version 11.8.0.
Mintegral SDK version 7.7.0.

Version 7.6.9.0

Verified compatibility with Mintegral SDK version 7.6.9.

Built and tested with:

Google Mobile Ads SDK version 11.7.0.
Mintegral SDK version 7.6.9.

Version 7.6.8.0

Verified compatibility with Mintegral SDK version 7.6.8.

Built and tested with:

Google Mobile Ads SDK version 11.7.0.
Mintegral SDK version 7.6.8.

Version 7.6.7.0

Verified compatibility with Mintegral SDK version 7.6.7.

Built and tested with:

Google Mobile Ads SDK version 11.6.0.
Mintegral SDK version 7.6.7.

Version 7.6.6.0

Verified compatibility with Mintegral SDK version 7.6.6.

Built and tested with:

Google Mobile Ads SDK version 11.5.0.
Mintegral SDK version 7.6.6.

Version 7.6.4.0

Verified compatibility with Mintegral SDK version 7.6.4.

Built and tested with:

Google Mobile Ads SDK version 11.4.0.
Mintegral SDK version 7.6.4.

Version 7.6.3.0

Verified compatibility with Mintegral SDK version 7.6.3.

Built and tested with:

Google Mobile Ads SDK version 11.3.0.
Mintegral SDK version 7.6.3.

Version 7.6.2.0

Verified compatibility with Mintegral SDK version 7.6.2.

Built and tested with:

Google Mobile Ads SDK version 11.3.0.
Mintegral SDK version 7.6.2.

Version 7.6.1.0

Verified compatibility with Mintegral SDK version 7.6.1.

Built and tested with:

Google Mobile Ads SDK version 11.3.0.
Mintegral SDK version 7.6.1.

Version 7.6.0.0

Verified compatibility with Mintegral SDK version 7.6.0.

Built and tested with:

Google Mobile Ads SDK version 11.2.0.
Mintegral SDK version 7.6.0.

Version 7.5.9.0

Verified compatibility with Mintegral SDK version 7.5.9.

Built and tested with:

Google Mobile Ads SDK version 11.2.0.
Mintegral SDK version 7.5.9.

Version 7.5.8.0

Verified compatibility with Mintegral SDK version 7.5.8.

Built and tested with:

Google Mobile Ads SDK version 11.1.0.
Mintegral SDK version 7.5.8.

Version 7.5.7.0

Verified compatibility with Mintegral SDK version 7.5.7.
Now requires minimum iOS version 12.0.
Now requires Google Mobile Ads SDK version 11.0 or higher.
Included Info.plist in the frameworks within MintegralAdapter.xcframework .

Built and tested with:

Google Mobile Ads SDK version 11.0.1.
Mintegral SDK version 7.5.7.

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.
Added bidding support for app open ad format.

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.

Integrate Mintegral with bidding (Beta) Stay organized with collections Save and categorize content based on your preferences.

Supported integrations and ad formats

Requirements

Step 1: Set up configurations in Mintegral UI

Locate the App Key

Add a new application

Create an ad placement

Locate your Mintegral Reporting API Key

Bidding

Waterfall

Update your app-ads.txt

Step 2: Set up Mintegral demand in Ad Manager UI

Add Mintegral in Companies

Bidding

Waterfall

Enable secure signal sharing

Bidding

Waterfall

Share secure signal on bid requests

Bidding

Waterfall

Allow secure signal sharing for SDK Bidding

Bidding

Waterfall

Configure Mintegral bidding

Bidding

Waterfall

Configure ad unit mapping

Bidding

Waterfall

Add Mobvista/Mintegral to GDPR and US state regulations ad partners list

Step 3: Import the Mintegral SDK and adapter

Using CocoaPods (recommended)

Manual integration

Step 4: Implement privacy settings on Mintegral SDK

EU consent and GDPR

Swift

Objective-C

US states privacy laws

Swift

Objective-C

Step 5: Add required code

SKAdNetwork integration

Step 6: Test your implementation

Enable test ads

Verify test ads

Optional steps

Add Mintegral to CCPA ad partners list

Native ads

Ad rendering

Error codes

Mintegral iOS Mediation Adapter Changelog

Next version

Integrate Mintegral with bidding (Beta)