Integrate Pangle with mediation

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

Integration
Bidding
Waterfall  1
Formats
Banner
Interstitial
Rewarded
Rewarded Interstitial
1 Waterfall integration is in open beta.

Requirements

  • Latest Google Mobile Ads SDK
  • Unity 5.6 or higher
  • [For bidding]: To integrate all supported ad formats in bidding, use Google Mobile Ads mediation plugin for Pangle 2.4.0 or higher (latest version recommended)
  • 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

Sign up or Log in to your Pangle account.

Add a new application

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

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 the Add button to create your ad placement.

Android

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.

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

Android

iOS

Waterfall

Select your Ad Format and Ad Placement Name, and 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

Turn on test mode

Follow the instructions in Pangle's How to add a Test Ad guide on how to enable Pangle test ads.

Step 2: Set up Pangle demand in Ad Manager UI

Configure mediation settings for your ad unit

Android

For instructions, see step 2 in the guide for Android.

iOS

For instructions, see step 2 in the guide for iOS.

Step 3: Import the Pangle SDK and adapter

OpenUPM-CLI

If you have OpenUPM-CLI installed, you can install the Google Mobile Ads Pangle Mediation Plugin for Unity to your project by running the following command from your project's root directory:

openupm add com.google.ads.mobile.mediation.pangle

OpenUPM

In your Unity project editor, select Edit > Project Settings > Package Manager to open the Unity Package Manager Settings.

Under the Scoped Registries tab, add OpenUPM as a scoped registry with the following details:

  • Name: OpenUPM
  • URL: https://package.openupm.com
  • Scope(s): com.google

OpenUPM Details

Then, navigate to Window > Package Manager to open the Unity Package Manager and select My Registries from the drop-down menu.

Unity Registries

Select the Google Mobile Ads Pangle Mediation package and click Install.

Install from OpenUPM

Unity Package

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.

Import from Unity

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

Force Resolve

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

Enable test ads

Make sure you register your test device for Ad Manager and enable test mode in Pangle UI.

Verify test ads

To verify that you are receiving test ads from Pangle, enable single ad source testing in ad inspector using the Pangle (Bidding) and Pangle (Waterfall) ad source(s).

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

Version 4.5.0

Version 4.4.2

Version 4.4.1

Version 4.4.0

Version 4.3.3

Version 4.3.2

Version 4.3.1

Version 4.3.0

Version 4.2.1

Version 4.2.0

Version 4.1.0

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