Mintegral をメディエーションと統合する

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 AdMob mediation adapter for Mintegral has the following capabilities:

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

2 Waterfall integration for this format is in closed beta.

3 Waterfall integration for this format is in open beta.

Requirements

  • Android API level 21 or higher

Step 1: Set up configurations in Mintegral UI

注册登录您的 Mintegral 帐号。

查找应用密钥

前往应用设置标签页,然后记下应用密钥

添加新应用

应用设置标签页中,点击添加应用按钮。

选择平台,然后填写表单的其余部分。然后,点击保存

记下您应用的应用 ID

创建广告展示位置

创建应用后,转到展示位置和单元标签页,然后点击添加展示位置按钮(如下所示),即可创建广告展示位置。

输入展示位置名称广告格式

出价

选择标头出价作为出价类型。填写表单的其余部分,然后点击保存

瀑布

选择传统作为出价类型。填写表单的其余部分,然后点击保存

创建广告展示位置后,请记下展示位置 ID

点击 1 个广告单元下拉菜单,并记下 AD Unit ID(广告单元 ID)。

找到您的 Mintegral Reporting API 密钥

出价

出价集成不需要执行此步骤。

瀑布

您需要使用 Mintegral Reporting API 密钥来设置AdMob 广告单元 ID。前往帐号 > API 工具。记下您的 SkeySecret

Step 2: Set up Mintegral demand in AdMob UI

広告ユニットのメディエーション設定を行う

広告ユニットのメディエーション設定に Mintegral を追加する必要があります。

AdMob アカウントにログインします。次に、[メディエーション] タブに移動します。既存のメディエーション グループを編集する場合は、そのメディエーション グループの名前をクリックして編集し、広告ソースとして Mintegral を追加するに進んでください。

新しいメディエーション グループを作成するには、[メディエーション グループを作成] を選択します。

広告フォーマットとプラットフォームを入力して、[続行] をクリックします。

メディエーション グループに名前を付けて、ターゲットとする地域を選択します。次に、メディエーション グループのステータスを [有効] に設定し、[広告ユニットを追加] をクリックします。

このメディエーション グループを、既存の 1 つ以上の広告ユニット(AdMob )に関連付けます。[完了] をクリックします。

選択した広告ユニットが入力された広告ユニットカードが表示されます。

広告ソースとして Mintegral を追加

入札

[広告ソース] セクションの [入札] カードで、[広告ソースを追加] を選択します。Mintegral を選択します。

[パートナー契約の署名方法] をクリックし、Mintegralとの入札パートナーシップを設定します。

[確認して同意する] をクリックし、[続行] をクリックします。

Mintegralのマッピングがすでにある場合は、それを選択できます。それ以外の場合は、[マッピングを追加] をクリックします。

次に、前のセクションで取得した App Key, App ID, Placement ID, and Ad Unit IDを入力します。[完了] をクリックします。

重要:Mintegral UI と同様に、 App ID and App Key は対象のアプリに関連付ける必要があります。

ウォーターフォール

[広告ソース] セクションの [ウォーターフォール] カードで、[広告のソースを追加] を選択します。Mintegral を選択します。

[Mintegral] を選択します。 次に、Mintegral の eCPM の値を入力し、[続行] をクリックします。

Mintegralのマッピングがすでにある場合は、それを選択できます。それ以外の場合は、[マッピングを追加] をクリックします。

次に、前のセクションで取得した App Key, App ID, Placement ID, and Ad Unit IDを入力します。[完了] をクリックします。

Add Mintegral to GDPR and US state regulations ad partners list

GDPR 設定 米国の州規制の設定 の手順に沿って、 AdMob UI の GDPR および米国の州規制の広告パートナーのリストに Mintegral を追加します。

Step 3: Import the Mintegral SDK and adapter

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.0.0")
    implementation("com.google.ads.mediation:mintegral:16.7.21.0")
}

Manual integration

  1. To include the Mintegral SDK, go to Mintegral SDK for Android.

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

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

テスト広告を有効にする

AdMob。

バナー広告、インタースティシャル、リワード広告、ネイティブ広告フォーマットの Mintegral テスト広告を取得するには、 Mintegral テスト 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 AdMob 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.getAdapterResponse() 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.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() before onAdClosed() 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.