Product Bulletin

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.

April, 2020

Important: New Restrictions for Square and HQ Images in Single Image ads

When creating your ad, you will need to include an imageUrl and imageUrlHQ in the API and an Ad HQ Image URL in BULK. Note that the imageUrl must have a 1:1 aspect ratio. A square image (imageLargeUrl) is mandatory. If you upload an 800x800 image, for example, the asset will be resized down to 627x627 pixels. And if you upload an 800x850 image, the asset will be resized and cropped down to 627x627 pixels. If the image is off from the 1:1 aspect ratio by more than 10%, the asset will be rejected and ad creation will fail. For example, if an 800x1000 image is more than 10% off from 1:1 square, it will be rejected.

This applies to API, UI and BULK uploads. Ensure that you follow these requirements when creating single image and carousel ads. Use a 1:1 aspect ratio and an exact size of 627x627 for a square asset for carousel ads.

Note that this is a requirement now for Image ad formats. Video, Mail sponsored, and Carousel ads are unchanged as they’re already required to meet these restrictions.

The image requirements for various assets is shown in the table below:

Asset

Required?

Aspect ratio enforced?

Rectangle image - 1200x627px

Yes

Yes - 1.9.1

Square image - 627x627px

Yes

Yes - 1:1

Thumbnail - 180x180px

Optional

Yes - 1:1

Note

The Thumbnail aspect ratio of 1:1 is now enforced. It is still an optional asset for Image Ads, and still required for Mail Ads.

Note

Existing ads that are missing square assets will experience reduced supply as they are dropped from rendering on ad units that need the square asset.

Important: For Advertisers Making GET Requests

Important

As a reminder, only one adGroupId or advertiserId parameter is allowed to be passed in as a query parameter for all filtered list GET calls. See the latest documentation in the Ad Object section, What’s New, and Latest Updates.

New Dynamic Product Ads Guide

  • We’ve recently rolled out a new portal dedicated to Dynamic Product Ads in our documentation suite. This empowers partners and advertisers with an expanded set of resources in one location, to help streamline DPA planning and setup. This guide is a repository intended for DPA partners, developers and account managers. It serves as the source of truth for the combined documentation suites for all technical content dedicated to DPA for the Native API and Native UI. Use our guide as a toolkit to navigate topics and essential reference material, and to explore implementation details, how-to’s, case studies, FAQs and best practices.

New Infographic: The State of News

  • For advertisers, understanding how to navigate the various types of news sites to unlock the potential benefit for your brand is key. Check out Verizon Media’s new article and then read and download the full infographic. Also, Verizon Media has created a Coronavirus hub page across the Yahoo ecosystem (News, Finance, Sports, Lifestyle and Entertainment) that aggregates the latest news about the pandemic in the U.S. and across the globe to keep our nearly 900M users informed with trusted content.

Native Ads Reminders and Resources

  • As a reminder, 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 http:// with 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.

  • 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.

Important

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

Important

As a reminder, we now have strict validation for our redirect URLs. This means that if a registered redirect URL is, for example, http://example.com, but the actual redirect URL is http://example.com/test, the redirect will fail. For more details, see Latest Updates.

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.