Formats and mechanics

HTML Content

Supported in banner and interstitial ad units. It is not recommended to use custom controls (close button, skip or rewind, adtune button), as Yandex SSP will display them automatically.

The recommended creative payload is up to 64KB.

Yandex SSP supports MRAID versions 1.0 and 2.0. The creative code must include <script src="mraid.js"></script> for proper rendering, and the click must be triggered using mraid.open().
Supported media formats: JPG/JPEG, PNG, GIF. Auto-play of sound and auto-click are prohibited.

To correctly display the ad, always use the block dimensions — they are passed in the .imp.banner.w and .imp.banner.h fields.

Video Content

Supported in banner, interstitial, and rewarded ad units.

The video player supports VAST 2.0, 3.0, 4.0, and Wrapper, VPAID is additionally supported only for web inventory. Refer to .imp.video.protocols and .imp.video.api for the correct creative type selection.

The maximum file size allowed is 2MB. Video duration can be limited individually, actual limits are provided in the .video.maxduration and .video.minduration fields.
For interstitial ads, the recommended duration is 5–30 seconds, for rewarded ads — 20–60 seconds.. The video will replay until the user closes the ad.

Yandex Mobile SDK supports Companion Ad. refer to .video.companionad and .video.companiontype, if these fields are not passed – Companion is not available for showing. It is strongly recommended not to send empty Companions or multiple Companions at once.
If several Companion objects are present in one VAST, the first non-empty one will be selected in the following order:

1. Static Resource
2. HTML Resource
3. iframe Resource

You must specify the Companion size in the tag <Companion width="720" height="1280">.

Tracking links are fired according to VAST 4.0. For Companion Ads, CompanionClickThrough and CompanionClickTracking are fired respectively.

Native Content

Native Ad is supported across all inventory based on oRTB Native 1.2

The required assets for display are Title and Main image. It is recommended to send all available assets for better performance. Entire URLs must support https.
For media assets sizes, refer to wmin and hmin in BidRequest.

Asset parameters

Asset ID	Asset Name	Description	Data Type	Asset Type	Restriction
1	Title	A title with a description related to the advertised product or service	String	Mandatory	up to 140 characters
2	Main image	The primary banner to be displayed	Img	Mandatory	minimum 150x150
5	Description	Additional text related to the advertised product or service	String	Recommended	up to 140 characters
9	display_url	The display domain or bundle to which a transition will be made.	String	Recommended	up to 50 characters
10	CTA	Call to Action placed on a clickable button	String	Recommended	up to 15 characters
11	Icon	An additional icon (favicon) for the advertisement of mobile applications. Often matches the icon from the app store.	Img	Recommended	minimum 50x50

CTV Content

Unavailable for DSP partners by default. Contact your account manager for details.

Only VAST InLine without Companion Ads is supported.
Horizontal video orientation and other technical restrictions listed in the table below are mandatory.

Parameter	Requirement
Formats	MP4 (H.264/AVC), MOV (ProRes 422), WebM (VP9), AVI (XviD)
Resolution	Minimum 720p, recommended 1080p (Full HD) or 4K
Video Bitrate	≥ 8 Mbps (1080p), ≥ 12 Mbps (4K)
Frame Rate	24–60 FPS (no artificial frame interpolation)
Aspect Ratio	16:9 (standard)

Additional Features

AutoStoreKit and SKOverlay

Available only for iOS devices (depending on iOS version). Supported when the .ext.skadn object is present in the BidRequest. If you do not see your skadnetids, contact your account manager.

ASK and SKOverlay always show together within an ad impression if the .ext.skadn object is included in the BidResponse. By default, for fullscreen ads, SKOverlay appears first at the bottom of the screen, and ASK opens after pressing the skip button (if an EndCard is present) or automatically after 5 seconds from the start of the ad.

Yandex SSP allows control of ASK behavior. One of the following values should be passed in .seatbid.bid.ext.skadn.ext.ask field in BidResponse.

Value	Type	Description
null	-	If the flag is not provided, ASK will be opened after skip. The click will be fired automatically.
1	Integer	If the flag is not provided, ASK will be opened after skip. The click will be fired automatically.