Integrate PubMatic with bidding

  • This guide explains how to integrate PubMatic ads into your iOS app using the Google Mobile Ads SDK mediation for bidding integrations.

  • The PubMatic mediation adapter supports bidding and waterfall integrations for various ad formats including app open, banner, interstitial, rewarded, rewarded interstitial, and native ads.

  • Implementing PubMatic mediation requires setting up configurations in the PubMatic UI, setting up PubMatic demand in the Ad Manager UI, and importing the PubMatic SDK and adapter into your iOS project.

  • Proper implementation of privacy settings according to GDPR and US state regulations is necessary when using the PubMatic SDK.

  • Testing your implementation with test ads and verifying them through single ad source testing is recommended before releasing your app.

Select platform: AndroidNew Android iOS Unity Flutter

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

Supported integrations and ad formats

The mediation adapter for PubMatic has the following capabilities:

Integration
Bidding
Waterfall
Formats
App open
Banner
Interstitial
Rewarded
Rewarded Interstitial
Native

1 Waterfall integration is in alpha.

2 All other supported ad formats besides banners are in alpha.

Requirements

  • iOS deployment target of 13.0 or higher

Step 1: Set up configurations in PubMatic UI

Sign up or Log in to your PubMatic account and select the OpenWrap SDKcard.

Add a new application

Navigate to the Appstab and click the Add Appbutton.

Apps Dashboard

Select the Platform, as well as the App Store URLand App Namefor your app.

Under Integration Path, select iOS (Objective-C / Swift)and select AdMob - SDK Biddingas the Sub-integration Path. Then, click the Add Appbutton.

New App Form

Update your app-ads.txt

Authorized Sellers for Apps app-ads.txt is an IAB Tech Lab initiative that helps ensure your app ad inventory is only sold through channels you've identified as authorized. To prevent a significant loss in ad revenue, you'll need to implement an app-ads.txt file. If you haven't done so already, create an app-ads.txt file for Ad Manager .

Before your app is finalized, you will be presented the appropriate entries to add to your app-ads.txt .

app-aps.txt

For additional information on how to implement app-ads.txt for PubMatic, see How to Implement app-ads.txt .

Profile ID

Once your app is created, navigate to the Appstab and take note of your newly created application's Profile ID.

App Profile ID

Create an ad unit

Under the Ad Unitstab, select the app you created on the previous section and click the Create Ad Unitbutton.

Create Ad Unit

Fill out the form with the details of your ad unit and click Save.

Create Ad Unit Form

Take note of your newly created OpenWrap Ad Unit ID.

App Ad Unit ID

Obtain your Publisher ID

Navigate to the Analytics Dashboard . Hover over the profile icon and take note of your ID.

Publisher ID

Step 2: Set up PubMatic demand in Ad Manager UI

Sign in to your Ad Manager account .

Add PubMatic OpenWrap SDK in Companies

Bidding

This step isn't required for bidding integrations.

Waterfall

Navigate to Admin> Companies, then click the New companybutton in the All companiestab. Select Ad network.

Select PubMatic OpenWrap SDKas the Ad network, enter a unique Nameand enable Mediation.

You don't need to enter a Usernameor Password. Click Savewhen done.

Enable secure signal sharing

Bidding

Navigate to Admin> Global settings. Go to the Ad Exchange account settingstab and review and toggle on Secure signal sharing. Click Save.

Waterfall

This step isn't required for waterfall integrations.

Bidding

Navigate to Inventory> Secure Signals. Under Secure signals, search for PubMaticand toggle on Enable app integration.

Click Save.

Waterfall

This step isn't required for waterfall integrations.

Allow secure signal sharing for SDK Bidding

Bidding

Navigate to Delivery> Demand channel settings. In the Default settingstab, toggle on Allow secure signal sharingfor SDK Bidding.

Click Save.

Waterfall

This step isn't required for waterfall integrations.

Configure PubMatic OpenWrap SDK bidding

Bidding

Navigate to Delivery> Bidders, and click Go to SDK Bidding.

Click New bidder.

Select PubMatic OpenWrap SDKas the bidder.

Click Continueto enable SDK Bidding for this bidder.

Click Done.

Waterfall

This step isn't required for waterfall integrations.

Configure ad unit mapping

Bidding

Navigate to Delivery> Bidders, and click Go to SDK Bidding.

Select the company for PubMatic OpenWrap SDK.

Go to the Ad unit mappingtab and click New ad unit mapping.

Choose Specific ad unit. Select an ad unit and format, Mobile appas the Inventory type, and your Mobile application. Then, enter OpenWrap Ad Unit ID obtained in the previous section.

Finally, click Save.

Waterfall

Navigate to Delivery> Yield groupsand click the New yield groupbutton. Select your Mobile application.

Scroll down and click Add yield partner.

Select the company you created for PubMatic OpenWrap SDK in the previous section. Choose Mobile SDK mediationas the Integration type, iOSas the Platform, and Activeas the Status.

Enter the OpenWrap Ad Unit ID obtained in the previous section, and the Default CPMvalue. Click Save.

Add PubMatic to GDPR and US state regulations ad partners list

Follow the steps in European regulations settings and US state regulations settings to add PubMaticto the European and US state regulations ad partners list in the Ad Manager UI.

Step 3: Import the PubMatic OpenWrap SDK and adapter

Use Swift Package Manager

Before you continue, you must have the minimum supported adapter version 4.10.0.0.

To add a package dependency to your project, follow these steps:

  1. In Xcode, navigate to File > Add Package Dependencies....

  2. In the prompt that appears, search the following package URL:

     https://github.com/googleads/googleads-mobile-ios-mediation-pubmatic.git 
    
  3. In Dependency Rule, select Branch.

  4. In the text field, enter main .

Use CocoaPods

  • Add the following line to your project's Podfile:

     pod 'GoogleMobileAdsMediationPubMatic' 
    
  • From the command line run:

     pod  
    install  
    --repo-update 
    

Manual integration

  1. Download the latest version of the PubMatic OpenWrap SDK for iOS and link all the .xcframework files and bundles in your project.

  2. Download the latest version of the PubMatic adapter from the download link in the Changelog and link PubMaticAdapter.xcframework in your project.

Step 4: Implement privacy settings on PubMatic

To comply with Google EU User Consent Policy , you must make certain disclosures to your users in the European Economic Area (EEA), the UK, and Switzerland, and obtain their consent for the use of cookies or other local storage where legally required, and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). You are responsible for verifying consent is propagated to each ad source in your mediation chain.

PubMatic automatically reads GDPR consent set by consent management platforms that support Google's Additional Consent specification , including the UMP SDK . For more information, see Pass GDPR and GDPR consent .

US states privacy laws

US 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 through a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The US 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.

PubMatic automatically reads GPP consent set by consent management platforms that support Google's Additional Consent specification , including the UMP SDK . For more information, see Pass GPP consent .

Step 5: Add required code

Implement SKAdNetwork

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

Step 6: Test your implementation

Enable test ads

Make sure you register your test device for Ad Manager.

Verify test ads

To verify that you are receiving test ads from PubMatic OpenWrap SDK, enable single ad source testing in ad inspector using the PubMatic OpenWrapad source(s).

Optional Steps

Native ads

Ad rendering

The PubMatic adapter returns its native ads as GADNativeAd objects. It populates the following fields for a GADNativeAd .

Field Assets always included by PubMatic adapter
Headline
Image
Body
Icon
Call to action
Star rating
Store
Price
Advertiser

Error codes

If the adapter fails to receive an ad from PubMatic, you can check the underlying error from the ad response using GADResponseInfo.adNetworkInfoArray under the following classes:

  GADMediationAdapterPubMatic 
 

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

Error code Domain Reason
101
com.google.ads.mediation.pubmatic Server configuration missing a required publisher ID.
102
com.google.ads.mediation.pubmatic The bidding signal collection request failed because multiple formats, no format, or an unsupported format was specified in the request parameters.
103
com.google.ads.mediation.pubmatic Invalid ad configuration for loading an ad.
104
com.google.ads.mediation.pubmatic Failed to present an interstitial ad because the ad was not ready.
105
com.google.ads.mediation.pubmatic Failed to present an rewarded ad because the ad was not ready.
106
com.google.ads.mediation.pubmatic Failed to load one of the native ad image sources.
1001-5002
Sent by PubMatic SDK PubMatic SDK returned an error. See PubMatic's documentation for more details.

PubMatic iOS Mediation Adapter Changelog

Version 5.0.1.0

  • Verified compatibility with PubMatic OpenWrap SDK version 5.0.1.

Built and tested with:

  • Google Mobile Ads SDK version 13.2.0.
  • PubMatic OpenWrap SDK version 5.0.1.

Version 5.0.0.0

  • Verified compatibility with PubMatic OpenWrap SDK version 5.0.0.

Built and tested with:

  • Google Mobile Ads SDK version 13.1.0.
  • PubMatic OpenWrap SDK version 5.0.0.

Version 4.12.0.0

  • Verified compatibility with PubMatic OpenWrap SDK version 4.12.0.
  • Updated the Google Mobile Ads SDK dependency to version 13.0.0.

Built and tested with:

  • Google Mobile Ads SDK version 13.0.0.
  • PubMatic OpenWrap SDK version 4.12.0.

Version 4.11.0.2

  • Updated the CocoaPods minimum iOS version to 13.0 .

Built and tested with:

  • Google Mobile Ads SDK version 13.0.0.
  • PubMatic OpenWrap SDK version 4.11.0.

Version 4.11.0.1

  • Added support for forwarding the tagForChildDirectedTreatment and tagForUnderAgeOfConsent Google Mobile Ads SDK parameters to the PubMatic OpenWrap SDK.

Built and tested with:

  • Google Mobile Ads SDK version 12.14.0.
  • PubMatic OpenWrap SDK version 4.11.0.

Version 4.11.0.0

  • Verified compatibility with PubMatic OpenWrap SDK version 4.11.0.

Built and tested with:

  • Google Mobile Ads SDK version 12.14.0.
  • PubMatic OpenWrap SDK version 4.11.0.

Version 4.10.0.0

  • Verified compatibility with PubMatic OpenWrap SDK version 4.10.0.

Built and tested with:

  • Google Mobile Ads SDK version 12.12.0.
  • PubMatic OpenWrap SDK version 4.10.0.

Version 4.9.0.0

  • Added waterfall support for banner, interstitial, rewarded and native ad formats.
  • Fixed a bug where native ad delegates were not correctly set.
  • Add a test mode property in the GADMediationAdapterPubMaticExtras class.
  • Verified compatibility with PubMatic OpenWrap SDK version 4.9.0.

Built and tested with:

  • Google Mobile Ads SDK version 12.12.0.
  • PubMatic OpenWrap SDK version 4.9.0.

Version 4.8.1.0

  • Verified compatibility with PubMatic OpenWrap SDK version 4.8.1.

Built and tested with:

  • Google Mobile Ads SDK version 12.9.0.
  • PubMatic OpenWrap SDK version 4.8.1.

Version 4.8.0.0

  • Verified compatibility with PubMatic OpenWrap SDK version 4.8.0.

Built and tested with:

  • Google Mobile Ads SDK version 12.8.0.
  • PubMatic OpenWrap SDK version 4.8.0.

Version 4.7.0.0

  • Initial release.
  • Supports bidding for banner, interstitial, rewarded and native ad formats.
  • Verified compatibility with PubMatic OpenWrap SDK version 4.7.0.

Built and tested with:

  • Google Mobile Ads SDK version 12.6.0.
  • PubMatic OpenWrap SDK version 4.7.0.
Design a Mobile Site
View Site in Mobile | Classic
Share by: