미디에이션과 InMobi 통합

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from InMobi using mediation, covering both waterfall and bidding integrations. It covers how to add InMobi to an ad unit's mediation configuration, and how to integrate the InMobi SDK and adapter into a Unity app.

Supported integrations and ad formats

Integration
Bidding  1
Waterfall
Formats
Banner
Interstitial
Rewarded

1 Bidding integration is in closed beta, reach out to your account manager to request access.

Requirements

  • Latest Google Mobile Ads SDK
  • Unity 4 or higher
  • To deploy on Android
    • Android API level 21 or higher
  • To deploy on iOS
    • iOS deployment target of 10.0 or higher
  • A working Unity project configured with Google Mobile Ads SDK. See Get Started for details.
  • Complete the mediation Get started guide

Step 1: Set up configurations in InMobi UI

InMobi 계정에 가입합니다.

입찰

Google 공개 입찰에서 InMobi SSP 사용을 선택하고 Google 게시자 ID를 입력합니다.

폭포

폭포식 구조 통합에는 추가 단계가 필요하지 않습니다.

확인이 완료되면 InMobi 계정에 로그인합니다.

앱 추가

InMobi 대시보드에 앱을 추가하려면 Inventory > Inventory Settings(인벤토리 설정)를 클릭합니다.

인벤토리 추가를 클릭하고 드롭다운 메뉴에서 모바일 앱 채널을 선택합니다.

검색창에 게시된 앱 스토어 URL을 입력하기 시작하면 자동으로 입력된 결과에서 앱을 선택합니다. 계속을 클릭합니다.

앱이 게시되지 않은 경우 직접 연결을 클릭하고 필요한 세부정보를 입력합니다. 계속을 클릭합니다.

앱 및 웹사이트 규정 준수 설정을 검토한 다음 게재위치 저장 및 만들기를 클릭합니다.

게재위치

인벤토리를 설정하면 시스템에서 게재위치 만들기 워크플로로 리디렉션됩니다.

입찰

광고 단위의 유형을 선택합니다. 게재위치 이름을 입력하고 잠재고객 입찰 및 파트너에 대해 각각 사용과 Google 공개 입찰을 선택한 후 양식의 나머지 부분을 작성합니다. 완료되면 Create Placement를 클릭합니다.

폭포

광고 단위의 유형을 선택합니다. 그런 다음 게재위치 이름을 입력하고 잠재고객 입찰에서 사용 안함을 선택한 후 양식의 나머지 부분을 작성합니다. 완료되면 게재위치 만들기를 클릭합니다.

게재위치가 생성되면 해당 게재위치의 세부정보가 표시됩니다.AdMob 광고 단위를 설정할 때 사용되는 게재위치 ID를 기록해 두시기 바랍니다.

계정 ID

InMobi 계정 ID는 금융 > 결제 설정 > 결제 정보에서 확인할 수 있습니다.

InMobi Reporting API 키 찾기

입찰

이 단계는 입찰 통합에는 필요하지 않습니다.

폭포

내 계정 > 계정 설정으로 이동합니다. API 키 탭으로 이동하여 API 키 생성을 클릭합니다.

키가 필요한 사용자의 이메일을 선택하고 API 키 생성을 클릭합니다. API 키와 사용자 이름/로그인 이름이 포함된 파일이 생성됩니다.

계정의 게시자 관리자만 모든 사용자를 위한 API 키를 생성할 수 있습니다. 이전에 생성된 API 키를 잊은 경우 API 키 탭에서 메일 위로 마우스를 가져가 API 키를 재설정합니다.

테스트 모드 사용 설정

모든 실시간 노출 또는 특정 테스트 기기에서만 게재위치에 테스트 모드를 사용 설정합니다.

Step 2: Set up InMobi demand in AdMob UI

광고 단위에 대한 미디에이션 설정 구성

Android

자세한 내용은 Android 가이드의 2단계를 참고하세요.

iOS

자세한 내용은 iOS 가이드의 2단계를 참고하세요.

Add InMobi to GDPR and US state regulations ad partners list

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

Step 3: Import the InMobi SDK and adapter

Download the latest version of Google Mobile Ads mediation plugin for InMobi from the download link in the Changelog and extract GoogleMobileAdsInMobiMediation.unitypackage from the zip file.

In your Unity project editor, select Assets > Import Package > Custom Package and select the GoogleMobileAdsInMobiMediation.unitypackage file you downloaded. Make sure that all the files are selected and click Import.

Then, select Assets > Play Services Resolver > Android Resolver > Force Resolve. The Unity Play Services Resolver library will perform dependency resolution from scratch and copy the declared dependencies into the Assets/Plugins/Android directory of your Unity app.

Step 4: Implement privacy settings on InMobi 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 Google Mobile Ads mediation plugin for InMobi version 2.1.0 added the InMobi.UpdateGDPRConsent() method that lets you pass consent information to InMobi. The following sample code shows how to pass consent information to the InMobi SDK. If you choose to call this method, we recommend that you do so prior to requesting ads with the Google Mobile Ads SDK.

using GoogleMobileAds.Api.Mediation.InMobi;
using System.Collections.Generic;
// ...

Dictionary<string, string> consentObject = new Dictionary<string, string>();
consentObject.Add("gdpr_consent_available", "true");
consentObject.Add("gdpr", "1");

InMobi.UpdateGDPRConsent(consentObject);

See InMobi's GDPR implementation details for more information about the possible keys and values that InMobi accepts in this consent object.

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.

See InMobi's CCPA documentation for guidelines on how to enable CCPA settings for InMobi.

Step 5: Add required additional code

Android

No additional code is required InMobi integration.

iOS

SKAdNetwork integration

Follow InMobi's documentation to add the SKAdNetwork identifiers to your project's Info.plist file.

Step 6: Test your implementation

테스트 광고 사용 설정

AdMob 용 테스트 기기를 등록하고 InMobi UI에서 테스트 모드를 사용 설정해야 합니다.

테스트 광고 확인

InMobi에서 테스트 광고를 수신하고 있는지 확인하려면 광고 검사기에서 InMobi (Bidding) and InMobi (Waterfall) 광고 소스를 사용하여 단일 광고 소스 테스트를 사용 설정하세요.

Optional steps

Android

Permissions

For optimal performance, InMobi recommends adding the following optional permissions to your app's AndroidManifest.xml file.

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />

You may optionally add these permissions to the Plugins/Android/GoogleMobileAdsInMobiMediation/AndroidManifest.xml file.

iOS

No additional steps required for iOS integration.

Error codes

If the adapter fails to receive an ad from InMobi, publishers can check the underlying error from the ad response using ResponseInfo under the following classes:

Android

com.google.ads.mediation.inmobi.InMobiAdapter
com.google.ads.mediation.inmobi.InMobiMediationAdapter

iOS

GADMAdapterInMobi
GADMediationAdapterInMobi

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

Android

Error code Reason
0-99 InMobi SDK Errors. See code for more details.
100 InMobi server parameters configured in the AdMob UI are missing/invalid.
101 Failed to initialize the InMobi SDK.
102 The requested ad size does not match an InMobi supported banner size.
103 Ad request is not a unified native ad request.
104 Attempted to request an InMobi ad without initializing the InMobi SDK. This should in theory never happen since the adapter initializes the InMobi SDK prior to requesting InMobi ads.
105 InMobi's ad is not yet ready to be shown.
106 InMobi failed to display an ad.
107 InMobi returned a native ad that is missing a required asset.
108 InMobi's native ad image assets contain a malformed URL.
109 The adapter failed to download InMobi's native ad image assets.

iOS

Error code Reason
101 InMobi server parameters configured in the AdMob UI are missing/invalid.
102 InMobi Adapter does not support the ad format being requested.
103 An InMobi ad is already loaded for this network configuration.
Other InMobi SDK returned an error. See IMRequestStatus.h for more details.

InMobi Unity Mediation Plugin Changelog

Version Next

  • Renamed DummyClient to PlaceholderClient.

Version 4.6.2

Version 4.6.1

Version 4.6.0

Version 4.5.1

Version 4.5.0

Version 4.4.1

Version 4.4.0

Version 4.3.3

Version 4.3.0

Version 4.2.2

Version 4.2.1

Version 4.2.0

Version 4.1.0

Version 4.0.4

Version 4.0.3

Version 4.0.2

Version 4.0.1

Version 4.0.0

Version 3.2.0

Version 3.1.2

Version 3.1.1

Version 3.1.0

Version 3.0.3

Version 3.0.2

Version 3.0.1

Version 3.0.0

Version 2.4.0

Version 2.3.0

  • Supports Android adapter version 7.2.9.0.
  • Supports iOS adapter version 7.3.2.0.

Version 2.2.2

  • Updated the plugin to support the new Rewarded API.
  • Supports Android adapter version 7.2.7.0.
  • Supports iOS adapter version 7.2.7.0.

Version 2.2.1

  • Supports Android adapter version 7.2.2.0.
  • Supports iOS adapter version 7.2.4.0.

Version 2.2.0

  • Supports Android adapter version 7.2.1.0.
  • Supports iOS adapter version 7.2.0.0.

Version 2.1.2

  • Supports Android adapter version 7.1.1.1.
  • Supports iOS adapter version 7.1.2.0.

Version 2.1.1

  • Supports Android adapter version 7.1.1.1.
  • Supports iOS adapter version 7.1.1.2.

Version 2.1.0

  • Supports Android adapter version 7.1.0.0.
  • Supports iOS adapter version 7.1.1.1.
  • Added the InMobi.UpdateGDPRConsent() method.

Version 2.0.0

  • Supports Android adapter version 7.0.4.0.
  • Supports iOS adapter version 7.1.1.0.

Version 1.0.0

  • First release!
  • Supports Android adapter version 6.2.4.0.
  • Supports iOS adapter version 6.2.1.0.