- Supported Ad Formats
- Download and Integration
- Set Up Verizon Media on the MoPub Dashboard
- Network Reporting and Auto CPM
- Migrate Verizon Media from Custom Native Setup
- Sample App
This guide is intended for publishers who want to use the MoPub SDK to load and display ads from Verizon Media via mediation. Below, you will find information about the ad network, integration/setup instructions, and more. For more information about how MoPub mediation works, visit this guide.
Supported Ad Formats
The following ad formats are currently supported by Verizon. For the latest support, visit the Verizon homepage.
- Rewarded Video
Download and Integration
For the latest download and integration instructions, consult Verizon Media’s tutorials before you integrate the SDK and adapters.
Android Integration Help
Verizon Media adapters are released as an Android Archive (AAR) file starting from version 184.108.40.206. The AAR includes the required Manifest data for Verizon Media. As a result, you no longer have 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
Placement IDare required.
Network Reporting and Auto CPM
To enable Verizon Media network reporting and Auto CPM, you must enter the Company ID and Secret Key.
Go to the Verizon portal and sign in.
Under Account Settings, click on Reporting Credentials to get your Company ID and Company Access Key (which is the Secret Key).
This setup is required to take advantage of Auto CPM.
Migrate Verizon Media from Custom Native Setup
Placement ID(if applicable) from the old custom native connection to the supported Verizon Media instance.
MoPub will initiate the following Verizon Media custom event class names to render the ads:
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 custom event class names, have both the old custom native network and the new Verizon Media network UI set up for backward compatibility.
Important: During migration, make sure the custom native network and the Verizon Media network are not both live at the same time, because this may impact your revenue.
For sample code, visit Verizon Media’s support center.
Last updated March 04, 2020
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.
© 2020 MoPub (a division of Twitter, Inc.)