Integrate Pangle with mediation

Note: See Pangle's documentation for regions that Pangle supports.

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Pangle using mediation, covering 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	^1
Formats
App open	^2
Banner
Interstitial
Rewarded
Rewarded Interstitial

¹ Waterfall integration is in closed beta.

² Not supported in bidding (supported only for waterfall mediation).

Requirements

• Unity 5.6 or higher
• Latest Google Mobile Ads SDK
• To deploy on Android
  • Android API level 19 or higher
• To deploy on iOS
  • iOS deployment target of 11.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 Pangle

Sign up or Log in to your Pangle account.

Add a new application

Navigate to the Applications tab and click on the Add App button.

Note: If your app supports both the Android and iOS platforms, you need to set up each one of them separately.

Select the Operating System you wish to create an application for and fill out the rest of the form. Then, click Submit.

Android

iOS

Take note of your application's App ID.

Android

iOS

Create an ad placement

Once your application has been created, click on the Add button as shown below to create your ad placement.

Android

Bidding

Select your Ad Format and Ad Placement Name, and select In-App Bidding as the Pricing Type. Fill out the rest of the form and click Submit.

Waterfall

Select your Ad Format and Ad Placement Name, and select Global CPM as the Pricing Type. Fill out the rest of the form and click Submit.

iOS

Bidding

Select your Ad Format and Ad Placement Name, and select In-App Bidding as the Pricing Type. Fill out the rest of the form and click Submit.

Waterfall

Select your Ad Format and Ad Placement Name, and select Global CPM as the Pricing Type. Fill out the rest of the form and click Submit.

Once your ad placement is created, take note of the Ad Placement ID.

Android

iOS

Locate Pangle Reporting API key

Bidding

This step isn't required for bidding integrations.

Waterfall

Take note of the User ID at the bottom left corner of the page.

Click Integrations > SDK & API > Pangle Reporting API 2.0. Take note of Role ID and Security Key.

Step 2: Configure mediation settings for your AdMob ad unit

You need to add Pangle to the mediation configuration for your ad unit. First sign in to your AdMob account.

Note: If you're deploying your Unity app to both Android and iOS, you need two AdMob ad units, one for each platform.

Android

Navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add Pangle as an ad source.

To create a new mediation group, select Create Mediation Group.

Enter your ad format and platform, then click Continue.

Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled. Then click Add Ad Units, which will open up the ad unit selection overlay.

Associate this mediation group with your existing AdMob ad unit. Then click Done. You should now see the ad units card populated with the ad units you selected.

Add Pangle as an ad source

Bidding

Under the Bidding card in the Ad Sources section, select Add Ad Source. Then select Pangle.

Click How to sign a partnership agreement and set up a bidding partnership with Pangle.

Click Acknowledge & agree, then click Continue.

If you already have a mapping for Pangle, you can simply select it. Otherwise, click Add mapping.

Next, enter a Mapping name, the App ID and the Ad Placement ID obtained in the previous section. Then click Done.

Waterfall

Under the Waterfall card in the Ad Sources section, select Add Ad Source.

Select Pangle and enable the Optimize switch. Enter the Reporting API user id, Reporting API role id, and Secret Key obtained in the previous section. Then enter an eCPM value for Pangle and click Continue.

Note: You only need to set up ad source optimization once per network.

If you already have a mapping for Pangle, you can simply select it. Otherwise, click Add mapping.

Next, enter a Mapping name, App ID, and Ad Placement ID. Then click Done.

Note: Ad source optimization takes a few days to gather enough data to accurately calculate eCPM for a mediation network. In the meantime, the ad source optimization status is PENDING, so you must manually set an eCPM value for the network. Once the eCPM can be calculated, the ad source automatically starts updating the eCPM on your behalf.

iOS

Navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add Pangle as an ad source.

To create a new mediation group, select Create Mediation Group.

Enter your ad format and platform, then click Continue.

Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled. Then click Add Ad Units, which will open up the ad unit selection overlay.

Associate this mediation group with your existing AdMob ad unit. Then click Done.

You should now see the ad units card populated with the ad units you selected.

Add Pangle as an ad source

Bidding

Under the Bidding card in the Ad Sources section, select Add Ad Source. Then select Pangle.

Click How to sign a partnership agreement and set up a bidding partnership with Pangle.

Click Acknowledge & agree, then click Continue.

If you already have a mapping for Pangle, you can simply select it. Otherwise, click Add mapping.

Next, enter a Mapping name, the App ID and the Ad Placement ID obtained in the previous section. Then click Done.

Waterfall

Under the Waterfall card in the Ad Sources section, select Add Ad Source.

Select Pangle and enable the Optimize switch. Enter the Reporting API user id, Reporting API role id, and Secret Key obtained in the previous section. Then enter an eCPM value for Pangle and click Continue.

Note: You only need to set up ad source optimization once per network.

If you already have a mapping for Pangle, you can simply select it. Otherwise, click Add mapping.

Next, enter a Mapping name, App ID, and Ad Placement ID. Then click Done.

Note: Ad source optimization takes a few days to gather enough data to accurately calculate eCPM for a mediation network. In the meantime, the ad source optimization status is PENDING, so you must manually set an eCPM value for the network. Once the eCPM can be calculated, the ad source automatically starts updating the eCPM on your behalf.

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: Additional code required

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

See the How to add Test Ad guide for detailed instructions on how to enable Pangle test ads. You can then use the Ad Inspector to verify if your implementation is correct.

That's it! You now have a working mediation integration with Pangle.

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 2.3.0

• Supports Pangle Android adapter version 5.3.0.6.0.
• Supports Pangle iOS adapter version 5.3.1.2.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 8.4.1.

Version 2.2.0

• Supports Pangle Android adapter version 5.2.0.6.0.
• Supports Pangle iOS adapter version 5.2.0.9.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 8.3.0.

Version 2.1.0

• Supports Pangle Android adapter version 5.1.0.9.0.
• Supports Pangle iOS adapter version 5.1.1.0.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 8.1.0.

Version 2.0.0

• Moved adapter content to GoogleMobileAds/Mediation/Pangle/.
• Refactored adapter namespace to use GoogleMobileAds.Mediation.Pangle.
• Supports Pangle Android adapter version 5.0.0.7.0.
• Supports Pangle iOS adapter version 5.0.0.6.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.4.1.

Version 1.5.1

• Supports Pangle Android adapter version 4.9.0.7.0.
• Supports Pangle iOS adapter version 4.9.0.8.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.4.0.

Version 1.5.0

• Supports Pangle Android adapter version 4.9.0.6.0.
• Supports Pangle iOS adapter version 4.9.0.7.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.3.1.

Version 1.4.0

• Supports Pangle Android adapter version 4.8.1.0.0.
• Supports Pangle iOS adapter version 4.8.1.0.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.3.1.

Version 1.3.1

• Supports Pangle Android adapter version 4.7.0.6.0.
• Supports Pangle iOS adapter version 4.7.0.6.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.2.0.

Version 1.3.0

• Renamed the following methods in the Pangle class:
  • SetGDPR() -> SetGDPRConsent()
  • SetCCPA() -> SetDoNotSell()
• Supports Pangle Android adapter version 4.7.0.5.0.
• Supports Pangle iOS adapter version 4.7.0.5.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.2.0.

Version 1.2.0

• Supports Pangle Android adapter version 4.5.0.6.1.
• Supports Pangle iOS adapter version 4.5.2.8.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.1.0.

Version 1.1.0

• Supports Pangle Android adapter version 4.5.0.3.0.
• Supports Pangle iOS adapter version 4.5.1.3.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.0.2.

Version 1.0.0

• Initial release!
• Supports Pangle Android adapter version 4.3.0.8.0.
• Supports Pangle iOS adapter version 4.3.0.5.0.
• Built and tested with the Google Mobile Ads Unity Plugin version 7.0.0.