Stay organized with collections
Save and categorize content based on your preferences.
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 an iOS app.
Supported integrations and ad formats
The Ad Manager mediation adapter for Pangle has the
following capabilities:
This step isn't required for bidding integrations.
Waterfall
Navigate to Admin > Companies, then click the New company button
in the All companies tab. Select Ad network.
Select Pangle as the Ad network,
enter a unique Name and enable Mediation.
You don't need to enter a Username or Password. Click Save when
done.
Enable secure signal sharing
Bidding
Navigate to Admin > Global settings. Go to the
Ad Exchange account settings tab and review and toggle on
Secure signal sharing. Click Save.
Waterfall
This step isn't required for waterfall integrations.
Configure Pangle bidding
Bidding
Navigate to Delivery > Bidders, and click New bidder under the
SDK Bidding tab.
Select Pangle as the bidder.
Toggle on Add this bidder's signal library to the list of allowed
signals and Allow signals to be shared with this bidder. Then, click
Continue.
Click Continue.
Click Done.
Waterfall
This step isn't required for waterfall integrations.
Configure ad unit mapping
Bidding
Navigate to Delivery > Bidders, and select the company for
Pangle under the SDK Bidding tab.
Go to the Ad unit mapping tab and click New ad unit mapping.
Choose Specific ad unit. Select an ad unit and format, Mobile app as
the Inventory type, and your Mobile application. Then, enter
App ID and Ad Placement ID obtained in the
previous section. Finally, click Save.
Waterfall
Navigate to Delivery > Yield groups and click the New yield
group button. Select your Mobile application.
Scroll down and click Add yield partner.
Select the company you created for Pangle
in the previous section. Choose Mobile SDK mediation as the
Integration type, iOS as the
Platform, and Active as the Status.
Enter the App ID and Ad Placement ID
obtained in the previous section, and the Default CPM value. Click
Save.
Step 3: Import the Pangle SDK and adapter
Using CocoaPods (recommended)
Add the following line to your project's Podfile:
pod 'GoogleMobileAdsMediationPangle'
From the command line run:
pod install --repo-update
Manual integration
Download the latest version of the
Pangle SDK for iOS
and link all the .framework files and bundles in your project.
Download the latest version of the Pangle adapter from the download link in
the Changelog and link
PangleAdapter.xcframework in your project.
Step 4: Add required code
SKAdNetwork integration
Follow Pangle's documentation
to add the SKAdNetwork identifiers to your project's Info.plist file.
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).
Optional Steps
Native ads
Ad rendering
The Pangle adapter returns its native ads as
GADNativeAd
objects. It populates the following
fields
for a
GADNativeAd.
1 The Pangle adapter does not
provide direct access to the main image asset for its native ads. Instead, the
adapter populates the
GADMediaView
with a video or an image.
Error codes
If the adapter fails to receive an ad from Pangle, you can check the
underlying error from the ad response using
GADResponseInfo.adNetworkInfoArray
under the following classes:
GADMediationAdapterPangle
Here are the codes and accompanying messages thrown by the Pangle adapter when
an ad fails to load:
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.
Verified compatibility with Pangle SDK version 5.6.0.8.
Refactored the +setCOPPA method by replacing the deprecated adConfiguration.childDirectedTreatment property with the new GADMobileAds.sharedInstance.requestConfiguration.tagForChildDirectedTreatment property.