Latest Updates

To stay current with the latest changes, updates and new feature releases in the Verizon Media Native Ad Platform, we’ve added this new section. The section is intended to provide API partners, account managers and developers with timely and relevant information.

The section is updated on an as-needed basis.

Important: New Restrictions for Square Image (imageLargeUrl)

When creating your ad, you will need to include an imageUrl and imageUrlHQ. Note that the imageLargeUrl must have a 1:1 aspect ratio. A square image (imageLargeUrl) is mandatory. If you upload an 800x1000 image, for example, the asset will be cropped to 800x800 pixels. Also ensure a 1:1 aspect ratio and exact size of 627x627 for a square asset for single image ads.

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.

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

Asset

Native UI

Native API

Aspect ratio enforced?

Rectangle image - 1200x627px

Required

Required

Yes - 1.9.1

Square image - 627x627px

Required

Required

Yes - 1:1

Thumbnail - 180x180px

Optional

Optional

No - 1:1

Account logo - Height: 180px min, Width: 180px - 2560px

Optional

Optional

No - 10.1 maximum

Account icon - Height: 180px min, Width: 180px - 2560px

Optional

Optional

No - 1:1

Important

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

Note that all GET request calls require a single advertiser parameter, if you are not fetching objects by ids.

When making GET requests for ads, for example, only one adGroupId or advertiserId parameter is allowed to be passed in as a query parameter for all filtered list GET calls. Similarly, when making GET requests for campaigns, only a single advertiserId parameter is allowed to be passed in as a query parameter for filtered list campaign calls.

It is essential that when making GET requests, you explicitly pass in the advertiserId parameter. If you don’t strictly follow this recommendation, you’ll experience performance degradation based on the number of accounts associated with the advertiser.

This recommendation applies to other endpoints as well. API partners need to make these changes, which will be enforced on the Native Ad Platform backend in an effort to ensure optimal performance of each advertiser account.

For resellers, any GET call needs to explicitly have the advertiserId passed.

Note that GET calls that use id(s) can remain as is.

For example:

GET https://api.gemini.yahoo.com:4080/mb_be/rest/ad/?id=818231&id=39823718

However, GET calls that do not pass id(s) should always be accompanied with the advertiserId parameter.

For example:

GET https://api.gemini.yahoo.com:4080/mb_be/rest/ad/?si=0&mr=500&exstatus=DELETED&exstatus=REJECT_INTERNAL&exstatus=MATCHED&exstatus=PROSPECT&exstatus=PROPOSAL&advertiserId=531231

New Dynamic Product Ads Guide

  • We’ve 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 Thought Leadership Series: Trusted News

  • Verizon Media has launched a new thought leadership series, starting with Trusted News. 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.

Podcast

Tune into the December 2019 Product Bulletin podcast for the latest on Verizon Media API features, changes and product enhancements released this month by the product development team.

[New] DPA Targeting Attributes

  • When setting up Dynamic Product Ads in the Ad Platform UI, you can target Custom Audiences as well as set site bid adjustments to optimize your site-level campaign performance. For setup steps, see How to Create a Dynamic Product Ad in the Advertiser Guide.

[New] Site Group X Device Targeting Support

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. 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 Site X Device Targeting for more information and Data Dictionary for a list of valid site group names.

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 Example

{
  "value": "MSN_US_HOMEPAGE|DESKTOP",
  "id": 338497,
  "type": "SITE_GROUP_X_DEVICE",
  "status": "ACTIVE",
  "advertiserId": 87292,
  "parentType": "CAMPAIGN",
  "parentId": 46756,
  "exclude": "FALSE",
  "bidModifier": 0.2
}

Bulk Example

Object Type

Site

Device

Campaign ID

Bid Modifier

Site Group X Device Target

MSN_US

DESKTOP

46576

-80

New: Dynamic Product Ads (DPA) for Travel & Hotels, and DPA for Retail

  • Verizon Media now provides you with two new feed ad solutions: Dynamic Product Ads for Travel & Hotels and Dynamic Product Ads for Retail. Because Dynamic Product Ads automatically show products to shoppers who have already viewed, searched, initiated checkout or purchased a hotel or cruise reservation, they provide an effective solution for travel and hotel retailers.

  • For an overview of key benefits, steps to get started, best practices, strategies and solutions, see our Travel & Hotel Solutions and our Retail Solutions guides. If you’re an advertiser who is familiar with Facebook Dynamic Ads for Travel and Facebook Retail & ecommerce ads, 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 both Travel & Hotel Solutions and the Retail Solutions guides are intended for advertisers who have already iterated through the sections for Dynamic Product Ads in the Advertiser Guide.

[New] Countdown Timer Prefix Text for Flash Sale Ad

  • Flash Sale Ads are enhanced with an optional countdownPrefixText field. This can help inform and encourage users to take action before a sale is scheduled to end. You’ll find example representations in the Fields and Operations sections of our Ad Object documentation, plus a set of valid input values in our Data Dictionary. To add a Countdown Prefix to a Flash Sale Ad in the UI, refer to the Advertiser Guide for options and examples.

[New] Shopping Objective Support Added for Site Bid Adjustments

  • Support has been add added for the Shopping objective in site bid adjustments, also known as Site X Device targeting; other supported objectives are VisitWeb and PromoteBrand. See details in Targeting and Bulk Field Objects documentation.

[New] Change for Redirect URLs

This is an important change that API partners should take into consideration when working with redirect URLs.

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. An error will be returned.

Note this change in your coding and development workflow.

For Reference:

As discussed in Campaigns, for app install and re-engage app campaigns, redirects should not be part of the defaultLandingUrl. These should be provided at the ad level through ad landingUrl.

Also, in Ad, supported third-party impression tracking URLs cannot include redirects.

[Update] For Native Resellers

Native resellers can create and manage their advertiser accounts using the Native Ad Platform API, specifically the Advertiser service.

If you’re a reseller note the following:

Important

When making GET calls to retrieve objects that belong to child accounts, the advertiserId parameter must be provided. For example, if you have an adgroup 111 under a managed advertiser with an id 222, to read the targeting settings for that ad group you’ll need to make the following GET call: https://api.gemini.yahoo.com/v4/rest/targetingattribute?advertiserId=222&parentId=111&parentType=ADGROUP

For more information, see Reseller Management API.