Welcome to the Verizon Media Ad Platform API Product Bulletin. This update includes a quick snapshot of recent and upcoming releases and is focused on features supported by the API. A summary of supported functionality is also included.
Product Bulletins are updated on a monthly cadence for Verizon Media API partners, account managers and developers.
Updated In-App Events Specification¶
We’ve updated our specification for the Server-to-Server In-App events integration with the Native Ad Platform API. Our spec is intended for 3rd Party Mobile Measurement Providers (3PMMP) who wish to integrate with Native Ad Platform via S2S. It is aimed at Data Providers, like Kochava, AppsFlyer, Adjust, Apsalar, CyberZ/FOX and others. The recent changes include updating all endpoints to replace
https://. To review all in-app event fields, endpoints, request and response examples, and other requirements, see the updated Server-to-Server In-app Events Specification.
Native Ads Reminders and Resources¶
As a reminder, DPA for Travel & Hotels and DPA for Retail are available as strategic ecommerce solutions. If you’re an advertiser who is familiar with Facebook Dynamic Ads for Travel, specifically Hotels and Cruise feed formats, you’ll want to be sure to sign up for this offering from Verizon Media. Our implementation is similar to that of Facebook’s. Note that our Travel & Hotel Solutions and Retail Solutions guides are intended for advertisers who have already iterated through the sections for Dynamic Product Ads in the Advertiser Guide. In addition, DPA Custom Audience targeting and DPA Site Bid Adjustments help optimize your site-level campaign performance. For setup steps, see How to Create a Dynamic Product Ad in our Advertiser Guide.
Site Group X Device targeting is now supported in the latest versions of the API, as well as both Bulk v2+ and API v2+. Site Group X Device targeting allows native advertisers to modify their bids on a per-site group, per-device basis on selected site groups, and is applicable to native channels-only, as well as VisitWeb, Shopping or PromoteBrand objectives-only. Site Group X Device targeting can be set at either the campaign or ad group level. See our Targeting documentation for details and an example.
Some sites have been migrated to site groups. Advertisers should make a GET call to the site group API endpoint to get a list of all new site groups. See the Data Dictionary to get the latest list of valid site group names.
Site Blocking at the campaign level is useful for ensuring the safety of your brand as well as improving the performance of your Native campaigns. Subdomain Blocking allows you to block the subdomains beneath a domain, up to 3 levels.
We’ve updated the API documentation for Bulk operations, with the latest information on how to upload and download bulk files in your advertiser accounts. A sample tab-separated CSV file spreadsheet is provided, along with information on Bulk schemas and objects. Check out the latest documentation for Bulk Operations.
We continue to enhance our best-in-class Native Ad Platform documentation suite, designed to help you simplify the process of integrating with us.
Reminder: Strict Validation for Redirect URLs¶
Glossary of Key Native Ad Platform Terms, Definitions & Concepts¶
A Verizon Media Glossary of Key Native Terms, Definitions and Concepts used within our ad platform is available. If you’re looking for definitions of key terms or an abbreviated listing of Native Ad Platform terms for advertisers who are getting started and creating their first campaigns and ad groups, you’ll find them in this alphabetical listing.
Reminder: Updated Postman to v3 Endpoint¶
Updated the Postman collection to the v3 endpoint for all API calls. Using Postman, you can test and verify the calls you make in the Native & Search API. See Postman API Toolkit.
Required Fields by Ad Type Matrix¶
A matrix is available which details the required fields when serving different ad types. For more information, see the Matrix view of required fields.