将 Pangle 与中介集成

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

Supported integrations and ad formats

The AdMob mediation adapter for Pangle has the following capabilities:

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded
Rewarded Interstitial

Requirements

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

Step 1: Set up configurations in Pangle UI

注册登录您的 Pangle 帐号。

添加新应用

转到 Applications(应用)标签页,然后点击 Add App(添加应用)按钮。

选择要为其创建应用的操作系统,并填写表单的其余部分。然后点击提交

Android

iOS

记下您应用的应用 ID

Android

iOS

创建广告展示位置

创建应用后,点击添加按钮创建广告展示位置。

Android

iOS

出价

选择广告格式广告展示位置名称,然后选择应用内出价作为定价类型。填写表单的其余部分,然后点击提交

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

Android

iOS

瀑布

选择广告格式广告展示位置名称,然后选择全局每千次展示费用作为定价类型。填写表单的其余部分,然后点击提交

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

Android

iOS

找到 Pangle Reporting API 密钥

出价

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

瀑布

记下页面左下角的 User ID

依次点击集成 > SDK 和 API > Pangle Reporting API 2.0。记下角色 ID安全密钥

开启测试模式

请按照 Pangle 的如何添加测试广告指南中的说明启用 Pangle 测试广告。

Step 2: Set up Pangle demand in AdMob UI

为广告单元配置中介设置

Android

如需了解相关说明,请参阅 Android 指南中的第 2 步。

iOS

如需了解相关说明,请参阅 iOS 指南中的第 2 步。

Step 3: Import the Pangle SDK and adapter

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

In your Unity project editor, select Assets > Import Package > Custom Package and find the GoogleMobileAdsPangleMediation.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: Add required code

Android

No additional code required for Pangle integration.

iOS

SKAdNetwork integration

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

Step 5: Test your implementation

启用测试广告

请务必为AdMob 注册您的测试设备,并在 Pangle 界面中启用测试模式

验证测试广告

如需验证您收到的是来自Pangle的测试广告,请使用相应广告来源在广告检查器中启用单一广告来源测试Pangle (Bidding) and Pangle (Waterfall)

Error codes

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

Android

com.pangle.ads
com.google.ads.mediation.pangle.PangleMediationAdapter

iOS

GADMediationAdapterPangle

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

Android

Error code Domain Reason
101 com.google.ads.mediation.pangle Invalid server parameters (e.g. Missing app ID or placement ID).
102 com.google.ads.mediation.pangle The requested ad size does not match a Pangle supported banner size.
103 com.google.ads.mediation.pangle Missing or invalid bid response.
-1-60000 com.pangle.ads Pangle SDK returned an error. See Pangle's documentation for more details.

iOS

Error code Domain Reason
101 com.google.ads.mediation.pangle Invalid server parameters (e.g. Missing app ID or placement ID).
102 com.google.ads.mediation.pangle The requested ad size does not match a Pangle supported banner size.
-1-60000 Sent by Pangle SDK Pangle SDK returned an error. See Pangle's documentation for more details.

Pangle Unity Mediation Plugin Changelog

Version 4.0.1

Version 4.0.0

Version 3.0.0

Version 2.8.1

Version 2.8.0

Version 2.7.0

Version 2.6.0

Version 2.5.0

Version 2.4.0

Version 2.3.0

Version 2.2.0

Version 2.1.0

Version 2.0.0

Version 1.5.1

Version 1.5.0

Version 1.4.0

Version 1.3.1

Version 1.3.0

Version 1.2.0

Version 1.1.0

Version 1.0.0