- Supported Ad Formats
- Download and Integrate
- Set Up Verizon Media on the MoPub Dashboard
- Network Reporting and Auto CPM
- Migrate Verizon Media from Custom Native Setup
- Background ad requests
- Sample App
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|
|Medium Rectangle||Medium Rectangle|
|Rewarded Video (Advanced Bidding not supported)||Rewarded Video (Advanced Bidding not supported)|
|Native (Advanced Bidding not supported)||Native (Advanced Bidding not supported)|
Download and Integrate
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 184.108.40.206. 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
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:
In the Network settings page for Verizon Media:
enable reporting access
provide the Client ID and Secret Key; you can find them as follows:
Contact your Verizon Media account manager to request Reporting API access. If you do not have a Verizon Media account manager, email email@example.com.
After you request Reporting API access from your Verizon Media account manager, search for an email from firstname.lastname@example.org.
In the email, click Get Credentials. You will be redirected to the OAuth credential generation page.
Click Create Credentials to create your Client ID and Client Secret.
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.
Navigate to the Auto CPM preferences page and turn on 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 mediation adapter 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 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 in v1.8.0 of the Verizon Ads SDK, ad requests made when your app goes into the background will return an error and be cancelled. This behavior is expected and controlled by Verizon, and cannot be overridden by publishers or mediation adapters. Additionally, rate limiting might apply if you immediately make another ad request.
Due to that behavior, you should expect a discrepancy in the number of ad requests recorded on your MoPub dashboard compared to that recorded on the Verizon dashboard.
For sample code, visit Verizon Media’s support center.
Last updated September 11, 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.)