Verizon Media

If you plan to use the MoPub SDK to load and display ads from Verizon Media via mediation, use this article for integration instructions and information unique to the ad network. To learn more about how MoPub mediation works, refer to our MoPub Network Mediation article.

Supported Ad Formats

Verizon Media currently supports the following ad formats. For support information, visit the Verizon homepage.

MoPub Formats Verizon Media Ad Formats
Banner Banner
Medium Rectangle Medium Rectangle
Interstitial Interstitial
Rewarded Ad (Advanced Bidding not supported) Rewarded Video (Advanced Bidding not supported)
Native (Advanced Bidding not supported) Native (Advanced Bidding not supported)

Download and Integrate

To download the Verizon Media adapters, navigate to the Mediation Integration Tool. You must also download the Verizon Media SDK.

For the latest download and integration instructions, consult Verizon Media’s tutorials before you integrate the SDK and adapters.

For Android, Verizon Media adapters are released as an Android Archive (AAR) file starting from version 1.0.2.0. The AAR includes the required Manifest data for Verizon Media. As a result, you no longer need to update your AndroidManifest manually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by Verizon must be manually entered into the AndroidManifest.

Set Up Verizon Media on the MoPub Dashboard

Site ID and Placement ID are required.

Network Reporting and Auto CPM

The following setup is required to take advantage of Auto CPM. To enable Verizon Media network reporting and Auto CPM:

  1. Navigate to the MoPub UI’s Networks tab. (Refer to these additional instructions that provide more detail for the remaining steps.)

  2. In the Network settings page for Verizon Media:

    • enable reporting access

    • provide the Client ID and Secret Key; you can find them as follows:

      1. Contact your Verizon Media account manager to request Reporting API access. If you do not have a Verizon Media account manager, email pubsuccess@verizonmedia.com.

      2. After you request Reporting API access from your Verizon Media account manager, search for an email from support@verizonmedia.com.

      3. In the email, click Get Credentials. You will be redirected to the OAuth credential generation page.

      Verizon Portal

      1. Click Create Credentials to create your Client ID and Client Secret.

      2. Click Download to save a .csv file with your Client ID and Client Secret.

    • provide the OrgID; you can find your OrgID by generating a report on the reporting portal one.aol.com/publisher/reporting/index.html#/. The OrgId will be a part of the url of the report on top of the page. OrgID is the numeric value following OrgID1M%3D. Also note that OrgID is different from the Company ID found on the Verizon UI.

      Verizon Portal

  3. Navigate to the Auto CPM preferences page and turn on Auto CPM.

Migrate Verizon Media from Custom Native Setup

  1. Transfer Site ID and Placement ID (if applicable) from the old custom native connection to the supported Verizon Media instance.

  2. MoPub will initiate the following Verizon Media mediation adapter class names to render the ads:

    • iOS

      • MPVerizonBannerCustomEvent
      • MPVerizonInterstitialCustomEvent
      • MPVerizonRewardedVideoCustomEvent
      • MPVerizonNativeCustomEvent
    • Android

      • com.mopub.mobileads.VerizonBanner
      • com.mopub.mobileads.VerizonInterstitial
      • com.mopub.mobileads.VerizonRewardedVideo
      • com.mopub.mobileads.VerizonNative

    If you are manually entering these class names or any other class names, migrate to the new network setup and pause the Custom Native Network. If you are using your own mediation adapter class names, make sure that both the old custom native network and the new Verizon Media network UI are set up for backward compatibility.

Important: During migration, make sure that the custom native network and the Verizon Media network are not both live at the same time, because this may impact your revenue.

Background Ad Requests

Starting with v1.8.0 of the Verizon Ads SDK, ad requests occurring when your app is in the background return an error and are cancelled. This behavior is expected and controlled by Verizon, and cannot be overridden by publishers or mediation adapters. Additionally, rate limiting may apply if you immediately make another ad request.

Because of this, expect a discrepancy in the number of ad requests recorded on your MoPub dashboard compared to the number recorded on the Verizon dashboard.

Test an Ad

We recommend that you test your Verizon integration using MoPub mediation test mode to verify that the adapter works as expected. Test mode must be set up on both the MoPub side and the Verizon side.

Set Up Test Mode on the MoPub Side

Refer to our Mediation Test Mode article for complete details on using this mode.

Set Up Test Mode on the Verizon Side

To test Verizon using our mediation test mode, contact Verizon to obtain Verizon test ads. You can then use these test ads to test with MoPub mediation test mode.

Early Initialization to Test Advanced Bidding

To test Advanced Bidding, Verizon requires that you initialize the network SDK early (before the MoPub SDK even), and that you initialize it manually, without waiting for the MoPub server to trigger Verizon to initialize. To do this, you must include the Verizon-specific Site ID key in your initialization code for both iOS and Android, as well as for Unity Prefabs.

If your Verizon test environment is under a different Site ID key, then you must update these test keys in your initialization code for iOS, Android, and Unity Prefabs before you test, so that Verizon initializes not only for your production account details, but for your testing account details as well. (This is not a concern if you use the same Site ID for your Verizon production and testing environments.)

Sample App

For sample code, visit Verizon Media’s support center.


Last updated March 30, 2021

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2021 MoPub (a division of Twitter, Inc.)