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

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

2 Waterfall integration is in closed beta.

Requirements

  • Android API level 21 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.

Select Header Bidding 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 Ad Manager ad unit ID. Navigate to Account > API Tools. Take note of your Skey and 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 값을 입력합니다. Save를 클릭합니다.

Add Mintegral to GDPR and US state regulations ad partners list

GDPR 설정 및 미국 주 규정 설정 Mintegral 를 Ad Manager UI의 GDPR 및 미국 주 규정 광고 파트너 목록에 추가합니다.

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.2.0")
    implementation("com.google.ads.mediation:mintegral:16.7.81.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

테스트 광고 사용 설정

Ad Manager

배너, 전면 광고, 보상형 광고, 네이티브 광고 형식용 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 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.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() 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.