Yahoo Native Ad Technical Specifications & Matrix Views¶

The programmatic Yahoo Ad Tech service for Ads provides you with methods for adding, updating, and retrieving ads, as described in the section below.

Definitions of ad types, such native standard, carousel and video app install, are also provided, with links to more detailed information and example use cases.

Technical Specifications for Images¶

We recommend using high-quality PNG files for your native ads. Include a rectangular image (1200x627 pixels) with a 1.9:1 aspect ratio, and a square image (627x627 pixels) with a 1:1 aspect ratio (required).

Larger images than 1200x627 pixels and 627x627 pixels may be used as long as they maintain the 1.9:1 aspect ratio and 1:1 aspect ratio, respectively.

Ideally, the Square Image (627x627 pixels) is derived from the Large HQ Image. Advertisers have the option to provide an alternate image. The 1.9:1 aspect ratio is highly recommended. The Square Image will be scaled down to various sizes, including 180x180 pixels.

Note

The maximum file size for images is 7MB. For animation: static images only, no animated GIFs.Thumbnail aspect ratio 1:1 will now be enforced. It is still optional asset for Image Ads, and still required for Mail Ads

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.

For Portrait Moments native ads, we recommend using 720p to 1080p high resolution images. The dimensions for this vertical image is 1080px by 1920px (9:16 aspect ratio). The min dimension should be 720px by 1280px

For Panorama Moments native ads, the image must be 2276px by 1280px or wider (max of 6826px by 1280px) high resolution image. The mage aspect ratio must be between 16:9 and 48:9.

Matrix View of Required fields When Serving Different Ad Types¶

For a comprehensive matrix view of required fields when serving different ad types, refer to Matrix View of Ad Types.

Matrix View of Search Changes When Serving Eligible Channels¶

The following table describes the behavior (current and new) for Search when serving eligible channels. For terminology: SON means Search on Native, SRN means Search Retargeting on Native, KRT means Keyword Retargeting. Note that for SON, the sub_channel can be SRN_AND_SEARCH or SRN_ONLY.

Input Channel	Input Sub-Channel	Current	New
SEARCH	SRN_AND_SEARCH	SEARCH, SON	SON
SEARCH	NULL	SEARCH, SON (based on the advertiser’s setup. Category 1 -> Search Only. Category [2\|3\|4] -> SEARCH, SON)	No OP., or SON (based on the Advertiser’s setup. Category 1 -> No OP. Category [2\|3\|4] -> SON)
NATIVE	SRN_ONLY	NATIVE KRT	NATIVE KRT
SEARCH AND NATIVE	NULL	SEARCH, NATIVE	NATIVE

The following table describes the current behavior (unchanged) for Search when serving eligible channels.

Input Channel	Input Sub-Channel	Current	New
SEARCH	SRN_ONLY	SON	SON
NATIVE	SRN_AND_SEARCH	Throws an exception	Throws an exception
NATIVE	NULL	NATIVE	NATIVE
SEARCH AND NATIVE	SRN_AND_SEARCH	Throws an exception	Throws an exception
SEARCH and NATIVE	SRN_ONLY	Throws an exception	Throws an exception

For more information on the Ad object, refer to Ad.