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 Android app.
Supported integrations and ad formats
The mediation adapter for Mintegral has the following capabilities:
Integration | |
---|---|
Bidding | 1 |
Waterfall | 2 |
Formats | |
App Open | |
Banner | |
Interstitial | |
Rewarded | |
Rewarded Interstitial | |
Native |
2 Waterfall integration is in closed beta.
Requirements
- Android API level 21 or higher
Latest Google Mobile Ads SDK
Complete the mediation Get started guide
Step 1: Set up configurations in Mintegral UI
查找应用密钥
前往应用设置标签页,然后记下应用密钥。
添加新应用
在应用设置标签页中,点击添加应用按钮。
选择平台,然后填写表单的其余部分。然后,点击保存。
![](https://developers.google.cn/admob/images/mediation/mintegral/new_application_Android.png?authuser=7&hl=nb)
记下您应用的应用 ID。
![](https://developers.google.cn/admob/images/mediation/mintegral/app_id_Android.png?authuser=7&hl=nb)
创建广告展示位置
创建应用后,转到展示位置和单元标签页,然后点击添加展示位置按钮(如下所示),即可创建广告展示位置。
![](https://developers.google.cn/admob/images/mediation/mintegral/create_placement_Android.png?authuser=7&hl=nb)
输入展示位置名称和广告格式。
选择标头出价作为出价类型。填写表单的其余部分,然后点击保存。
创建广告展示位置后,请记下展示位置 ID。
![](https://developers.google.cn/admob/images/mediation/mintegral/ad_placement_id_Android.png?authuser=7&hl=nb)
点击 1 个广告单元下拉菜单,并记下 AD Unit ID(广告单元 ID)。
![](https://developers.google.cn/admob/images/mediation/mintegral/add_ad_unit_id_Android.png?authuser=7&hl=nb)
找到您的 Mintegral Reporting API 密钥
出价
出价集成不需要执行此步骤。
瀑布
您需要使用 Mintegral Reporting API 密钥来设置Ad Manager 广告单元 ID。前往帐号 > API 工具。记下您的 Skey 和 Secret。
Step 2: Set up Mintegral demand in Ad Manager UI
登录您的 Ad Manager 帐号。
添加 Mintegral 公司
出价
出价集成不需要执行此步骤。
瀑布
依次前往管理 > 公司,然后点击所有公司标签页中的新公司按钮。选择广告联盟。
选择 Mintegral 作为广告联盟,输入一个唯一的名称并启用中介。
您无需输入用户名或密码。完成后,点击保存。
启用安全信号共享
出价
依次前往管理 > 全局设置。前往 Ad Exchange 帐号设置标签页,然后查看并开启安全信号共享。点击保存。
瀑布
广告瀑布流集成不需要执行此步骤。
配置 Mintegral 出价
出价
依次前往投放 > 出价方,然后点击 SDK 出价标签页下的新出价方。
选择Mintegral作为出价方。
开启将此出价方的信号库添加到允许的信号列表中和允许与此出价方共享信号。然后,点击继续。
点击继续。
点击完成。
瀑布
广告瀑布流集成不需要执行此步骤。
配置广告单元映射
出价
依次前往投放 > 出价方,然后在 SDK 出价标签页下,为Mintegral 选择公司。
转到广告单元映射标签页,然后点击新建广告单元映射。
选择特定广告单元。选择一种广告单元和格式,选择移动应用作为广告资源类型,然后选择移动应用。然后,输入在上一部分中获得的App Key, App ID, Placement ID, and Ad Unit ID 。最后,点击保存。
瀑布
依次转到投放 > 收益组,然后点击新建收益组按钮。选择您的移动应用。
向下滚动,然后点击添加收益合作伙伴。
选择您在上一部分中为 Mintegral创建的公司。选择移动 SDK 中介作为集成类型,选择 Android 作为平台,选择活跃作为状态。
输入在上一部分获得的 App Key, App ID, Placement ID, and Ad Unit ID,以及默认 CPM 值。点击保存。
Add Mintegral to GDPR and US state regulations ad partners list
按照 GDPR 设置 和 美国州级法规设置 中的步骤,将 Mintegral 添加到 Ad Manager 界面中的 GDPR 和美国州级法规广告合作伙伴列表中。
Step 3: Import the Mintegral SDK and adapter
Android Studio integration (recommended)
In your project-level settings.gradle.kts
file, add the following
repositories:
dependencyResolutionManagement {
repositories {
google()
mavenCentral()
maven {
url = uri("https://dl-maven-android.mintegral.com/repository/mbridge_android_sdk_oversea")
}
}
}
Then, in your app-level build.gradle.kts
file, add the following
implementation dependencies and configurations. Use the latest versions of the
Mintegral SDK and adapter:
dependencies {
implementation("com.google.android.gms:play-services-ads:23.3.0")
implementation("com.google.ads.mediation:mintegral:16.8.31.0")
}
Manual integration
To include the Mintegral SDK, go to Mintegral SDK for Android.
Navigate to the Mintegral adapter artifacts on Google's Maven Repository. Select the latest version, download the Mintegral adapter's
.aar
file, and add it to your project.
Step 4: Implement privacy settings on Mintegral SDK
EU consent and GDPR
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.
Java
import com.mbridge.msdk.out.MBridgeSDKFactory
// ...
MBridgeSDK sdk = MBridgeSDKFactory.getMBridgeSDK();
sdk.setConsentStatus(context, MBridgeConstans.IS_SWITCH_ON);
Kotlin
import com.mbridge.msdk.out.MBridgeSDKFactory
// ...
var sdk = MBridgeSDKFactory.getMBridgeSDK()
sdk.setConsentStatus(context, MBridgeConstans.IS_SWITCH_ON)
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 after initializing the Google Mobile Ads SDK but before requesting ads through the Google Mobile Ads SDK.
Java
import com.mbridge.msdk.out.MBridgeSDKFactory
// ...
MBridgeSDK mBridgeSDK = MBridgeSDKFactory.getMBridgeSDK();
mBridgeSDK.setDoNotTrackStatus(false);
Kotlin
import com.mbridge.msdk.out.MBridgeSDKFactory
// ...
var mBridgeSDK = MBridgeSDKFactory.getMBridgeSDK()
mBridgeSDK.setDoNotTrackStatus(false)
See Mintegral's privacy documentation for more information.
Step 5: Add required code
No additional code is required for Mintegral integration.
Step 6: Test your implementation
启用测试广告
请务必为 Ad Manager。
要获取适用于横幅广告、插页式广告、激励广告和原生广告格式的 Mintegral 测试广告,Mintegral 建议您使用 Mintegral Test ID 页面中提供的应用密钥、应用 ID、展示位置 ID 和广告单元 ID。
验证测试广告
如需验证您收到的是来自Mintegral的测试广告,请使用相应广告来源在广告检查器中启用单一广告来源测试。 Mintegral (Bidding) and Mintegral (Waterfall)
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 Ad Manager UI.
Native ads
Ad rendering
The Mintegral adapter returns its native ads as
NativeAd
objects. It populates the following
fields
for a
NativeAd
.
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
MediaView
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
ResponseInfo.getAdapterResponses()
under the following classes:
com.mbridge.msdk
com.google.ads.mediation.mintegral.MintegralMediationAdapter
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.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. |
Mintegral Android Mediation Adapter Changelog
Version 16.8.31.0
- Verified compatibility with Mintegral SDK 16.8.31.
Built and tested with:
- Google Mobile Ads SDK version 23.2.0.
- Mintegral SDK version 16.8.31.
Version 16.8.11.0
- Verified compatibility with Mintegral SDK 16.8.11.
Built and tested with:
- Google Mobile Ads SDK version 23.2.0.
- Mintegral SDK version 16.8.11.
Version 16.7.91.0
- Verified compatibility with Mintegral SDK 16.7.91.
Built and tested with:
- Google Mobile Ads SDK version 23.2.0.
- Mintegral SDK version 16.7.91.
Version 16.7.81.0
- Verified compatibility with Mintegral SDK 16.7.81.
Built and tested with:
- Google Mobile Ads SDK version 23.2.0.
- Mintegral SDK version 16.7.81.
Version 16.7.71.0
- Verified compatibility with Mintegral SDK 16.7.71.
Built and tested with:
- Google Mobile Ads SDK version 23.1.0.
- Mintegral SDK version 16.7.71.
Version 16.7.61.0
- Verified compatibility with Mintegral SDK 16.7.61.
Built and tested with:
- Google Mobile Ads SDK version 23.1.0.
- Mintegral SDK version 16.7.61.
Version 16.7.51.0
- Verified compatibility with Mintegral SDK 16.7.51.
Built and tested with:
- Google Mobile Ads SDK version 23.1.0.
- Mintegral SDK version 16.7.51.
Version 16.7.41.0
- Verified compatibility with Mintegral SDK 16.7.41.
Built and tested with:
- Google Mobile Ads SDK version 23.1.0.
- Mintegral SDK version 16.7.41.
Version 16.7.31.0
- Verified compatibility with Mintegral SDK 16.7.31.
Built and tested with:
- Google Mobile Ads SDK version 23.1.0.
- Mintegral SDK version 16.7.31.
Version 16.7.21.0
- Verified compatibility with Mintegral SDK 16.7.21.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- Mintegral SDK version 16.7.21.
Version 16.7.11.0
- Verified compatibility with Mintegral SDK 16.7.11.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- Mintegral SDK version 16.7.11.
Version 16.6.71.0
- Verified compatibility with Mintegral SDK 16.6.71.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- Mintegral SDK version 16.6.71.
Version 16.6.61.0
- Updated the minimum required Google Mobile Ads SDK version to 23.0.0.
- Verified compatibility with Mintegral SDK 16.6.61.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- Mintegral SDK version 16.6.61.
Version 16.6.51.0
- Verified compatibility with Mintegral SDK 16.6.51.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- Mintegral SDK version 16.6.51.
Version 16.6.41.0
- Verified compatibility with Mintegral SDK 16.6.41.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- Mintegral SDK version 16.6.41.
Version 16.6.34.0
- Verified compatibility with Mintegral SDK 16.6.34.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- Mintegral SDK version 16.6.34.
Version 16.6.21.0
- Verified compatibility with Mintegral SDK 16.6.21.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- Mintegral SDK version 16.6.21.
Version 16.5.91.1
- Added bidding support for app open ad format.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- Mintegral SDK version 16.5.91.
Version 16.5.91.0
- Verified compatibility with Mintegral SDK 16.5.91.
- Updated the minimum required Google Mobile Ads SDK version to 22.6.0.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- Mintegral SDK version 16.5.91.
Version 16.5.51.0
- Verified compatibility with Mintegral SDK 16.5.51.
Built and tested with:
- Google Mobile Ads SDK version 22.3.0.
- Mintegral SDK version 16.5.51.
Version 16.5.41.0
- Verified compatibility with Mintegral SDK 16.5.41.
Built and tested with:
- Google Mobile Ads SDK version 22.3.0.
- Mintegral SDK version 16.5.41.
Version 16.5.31.0
- Verified compatibility with Mintegral SDK 16.5.31.
- Reverted the adapter to depend on Google Mobile Ads SDK version 22.3.0.
- Added waterfall support for app open ad format.
Built and tested with:
- Google Mobile Ads SDK version 22.3.0.
- Mintegral SDK version 16.5.31.
Version 16.5.21.0
- Verified compatibility with Mintegral SDK 16.5.21.
- Updated the minimum required Google Mobile Ads SDK version to 22.4.0.
Built and tested with:
- Google Mobile Ads SDK version 22.4.0.
- Mintegral SDK version 16.5.21.
Version 16.5.11.0
- Added watermark support for bidding ads.
- Verified compatibility with Mintegral SDK 16.5.11.
Built and tested with:
- Google Mobile Ads SDK version 22.2.0.
- Mintegral SDK version 16.5.11.
Version 16.4.91.0
- Verified compatibility with Mintegral SDK 16.4.91.
Built and tested with:
- Google Mobile Ads SDK version 22.2.0.
- Mintegral SDK version 16.4.91.
Version 16.4.81.0
- Verified compatibility with Mintegral SDK 16.4.81.
Built and tested with:
- Google Mobile Ads SDK version 22.2.0.
- Mintegral SDK version 16.4.81.
Version 16.4.71.0
- Verified compatibility with Mintegral SDK 16.4.71.
Built and tested with:
- Google Mobile Ads SDK version 22.2.0.
- Mintegral SDK version 16.4.71.
Version 16.4.61.0
- Verified compatibility with Mintegral SDK 16.4.61.
Built and tested with:
- Google Mobile Ads SDK version 22.1.0.
- Mintegral SDK version 16.4.61.
Version 16.4.51.0
- Verified compatibility with Mintegral SDK 16.4.51.
Built and tested with:
- Google Mobile Ads SDK version 22.1.0.
- Mintegral SDK version 16.4.51.
Version 16.4.41.0
- Fixed an issue where banner ads were rendered with incorrect sizes.
- Verified compatibility with Mintegral SDK 16.4.41.
Built and tested with:
- Google Mobile Ads SDK version 22.0.0.
- Mintegral SDK version 16.4.41.
Version 16.4.31.0
- Verified compatibility with Mintegral SDK 16.4.31.
Built and tested with:
- Google Mobile Ads SDK version 22.0.0.
- Mintegral SDK version 16.4.31.
Version 16.4.21.0
- Updated adapter to use new
VersionInfo
class. - Updated the minimum required Google Mobile Ads SDK version to 22.0.0.
- Verified compatibility with Mintegral SDK 16.4.21.
Built and tested with:
- Google Mobile Ads SDK version 22.0.0.
- Mintegral SDK version 16.4.21.
Version 16.3.91.0
- Verified compatibility with Mintegral SDK 16.3.91.
Built and tested with:
- Google Mobile Ads SDK version 21.5.0.
- Mintegral SDK version 16.3.91.
Version 16.3.81.0
- Verified compatibility with Mintegral SDK 16.3.81.
Built and tested with:
- Google Mobile Ads SDK version 21.5.0.
- Mintegral SDK version 16.3.81.
Version 16.3.71.0
- Verified compatibility with Mintegral SDK 16.3.71.
Built and tested with:
- Google Mobile Ads SDK version 21.5.0.
- Mintegral SDK version 16.3.71.
Version 16.3.61.0
- Verified compatibility with Mintegral SDK 16.3.61.
Built and tested with:
- Google Mobile Ads SDK version 21.5.0.
- Mintegral SDK version 16.3.61.
Version 16.3.51.1
- Added waterfall support for banner (includes MREC), interstitial, rewarded and native ad formats.
- Updated the minimum required Google Mobile Ads SDK version to 21.5.0.
Built and tested with:
- Google Mobile Ads SDK version 21.5.0.
- Mintegral SDK version 16.3.51.
Version 16.3.51.0
- Verified compatibility with Mintegral SDK 16.3.51.
Built and tested with:
- Google Mobile Ads SDK version 21.4.0.
- Mintegral SDK version 16.3.51.
Version 16.3.41.0
- Verified compatibility with Mintegral SDK 16.3.41.
- Updated the minimum required Google Mobile Ads SDK version to 21.4.0.
Built and tested with:
- Google Mobile Ads SDK version 21.4.0.
- Mintegral SDK version 16.3.41.
Version 16.3.11.0
- Verified compatibility with Mintegral SDK 16.3.11.
- Updated the adapter to forward
onUserEarnedReward()
beforeonAdClosed()
when showing rewarded ads.
Built and tested with:
- Google Mobile Ads SDK version 21.3.0.
- Mintegral SDK version 16.3.11.
Version 16.2.61.0
- Initial release!
- Added bidding support for banner (includes MREC), interstitial, rewarded and native ad formats.
Built and tested with:
- Google Mobile Ads SDK version 21.3.0.
- Mintegral SDK version 16.2.61.