Integrating Verizon Media with Mediation

This guide is for publishers who want to use the Google Mobile Ads SDK to load and display ads from Verizon Media ads via mediation. It covers how to add Verizon Media to an ad unit's mediation configuration, how to set up Ad Network Optimization (ANO), and how to integrate the Verizon Media SDK and adapter into an iOS app.

Supported ad formats and features

The AdMob mediation adapter for Verizon Media has the following capabilities:

Formats
Banners
Interstitials
Rewarded Video
Native Advanced
Features
Smart Banners
Ad Network Optimization (ANO)

Requirements

  • iOS deployment target of 8.0 or higher
  • Latest Google Mobile Ads SDK

Step 1: Set up Verizon Media

Sign up or log in to Verizon Media's SSP. Under Applications and Sites, click the button to create your app and select iOS as the platform.

Fill out the form and click Save and Add Placement to create your app.

Once you've created an app, you will need to create a Placement. Select a Placement Type, fill out the form, and click Save & Monetize. Take note of your Placement ID. You will need this in the next step.

You will need to add an Ad Source to your placement. On the next form, select Oath Ad Platforms SSP as an Ad Source and fill out the form with the required information. Once you've completed the form, click Save.

Finally, drag the Ad Source that you just created under the Waterfall Ad Sources table to add it to your placement. Take note of the Site ID, just beside your app's name. You will also need this in the next step.

Open the Navigation menu and select Reporting Credentials under Account Settings.

Take note of the Company ID and Company Access Key.

Step 2: Configure mediation settings for your ad unit

You need to add Verizon Media to the mediation configuration for your ad unit.

First, sign in to your AdMob account. Next, 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 Verizon Media 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, and then click Add Ad Units.

Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.

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

Add Verizon Media as an ad source

In the Ad Sources card, select Add Ad Network. Select Verizon Media and enable the Optimize switch. Enter the Company ID and Company Access Key obtained in the previous section to set up ANO for Verizon Media. Then enter an eCPM value for Verizon Media and click Continue.

Enter the Placement ID and Site ID obtained in the previous section.

Using rewarded video ads

In the settings for your rewarded video ad unit, provide values for the reward amount and reward type. Then, to ensure you provide the same reward to the user no matter which ad network is served, check the Apply to all networks in Mediation groups box.

If you don't apply this setting, the Verizon Media adapter defaults to a reward of type "" (empty string) with a value of 1. The Verizon Media SDK does not provide specific reward values for its rewarded video ads.

For more information on setting reward values for AdMob ad units, see Create an ad unit.

Step 3: Import the Verizon Media SDK and adapter

Add the following line to your project's Podfile:

pod 'GoogleMobileAdsMediationVerizonMedia'

From the command line run:

pod install --repo-update

Step 4: Additional code required

No additional code required for Verizon Media integration.

Step 5: Test your implementation

Verizon Media ads can be tested by creating a Test Ad Source and adding it into your placement's Waterfall Ad Sources. Navigate to your Placement ID's settings, click the Add button and select Test Ad Source.

Once you've created the Ad Source, drag it into your placement's Waterfall Ad Sources.

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

Optional steps

Under the Google EU User Consent Policy, you must ensure that certain disclosures are given to, and consents obtained from, users in the European Economic Area (EEA) regarding the use of device identifiers and personal data. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information about each network's use. Google currently is unable to pass the user's consent choice to such networks automatically.

Enabling/disabling personalized ads

The Verizon Media adapter contains a -setPrivacyData: method that forwards consent information to the Verizon Ads SDK once it's initialized. This method takes one parameter:

consentInfo
Consent data to pass to the Verizon Ads SDK

Sample usage:

#import <VerizonAdsCore/VerizonAdsCore.h>
#import <VerizonMediaAdapter/VerizonMediaAdapter.h>
// ...

[GADMVerizonPrivacy.sharedInstance setPrivacyData:@{kVASConfigIABConsentKey: "IAB consent string"}];
Visit Verizon Media's Privacy Settings guide for more information about what inputs can be passed.

Using native ads

Ad rendering

The Verizon Media adapter populates the following Native ads advanced field descriptions for a GADUnifiedNativeAd.

Field Populated by Verizon Media adapter
Headline
Image
Body
App icon
Call to action
Advertiser Name
Star rating
Store
Price

Verizon Media iOS Mediation Adapter Changelog

Version 1.7.0.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.7.0.
  • Now requires Google Mobile Ads SDK version 7.62.0 or higher.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.62.0.
    • Verizon Ads SDK version 1.7.0

Version 1.6.0.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.6.0.
  • Now requires Google Mobile Ads SDK version 7.60.0 or higher.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.60.0.
    • Verizon Ads SDK version 1.6.0

Version 1.5.0.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.5.0.
  • Removed support for legacy Nexage adapter configurations.
  • Removed support for the i386 architecture.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.57.0.
    • Verizon Ads SDK version 1.5.0

Version 1.4.0.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.4.0.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.55.1.
    • Verizon Ads SDK version 1.4.0

Version 1.3.0.1

  • Added missing GADMVerizonPrivacy.h header.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.53.1.
    • Verizon Ads SDK version 1.3.0.

Version 1.3.0.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.3.0.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.53.0.
    • Verizon Ads SDK version 1.3.0.

Version 1.2.2.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.2.2.
  • Built and tested with:
    • Google Mobile Ads SDK version 7.53.0.
    • Verizon Ads SDK version 1.2.2.

Version 1.2.1.0

  • Verified compatibility with Verizon Ads Standard Edition version 1.2.1.
  • Added support for native ads
  • Added support for rewarded video ads

Version 1.1.2.0

  • Initial release.
  • Verified compatibility with Verizon Ads Standard Edition version 1.1.2.
  • Supports banner and interstitial ads.
  • 'One by AOL' has been rebranded to 'Verizon Media'.