Formats and mechanics

HTML content

HTML content is supported in banner and interstitial ad units. We don't recommend using custom UI controls (close button, skip, rewind, menu button) because Yandex SSP renders controls automatically.

Keep the recommended creative payload under 64 KB.

Yandex SSP supports MRAID versions 1.0 and 2.0. Add <script src="mraid.js"></script> to your creative code for correct rendering, and only trigger clicks via mraid.open().
Supported media formats: JPG/JPEG, PNG, and GIF. Audio autoplay and autoclicks aren't allowed.

For proper ad placement, use the dimensions passed in the .imp.banner.w and .imp.banner.h fields.

Video content

Video content is supported in banner, interstitial, and rewarded ad units.

The video player supports VAST 2.0, 3.0, 4.0, and Wrapper. It also supports VPAID, but for web inventory only. Check the .imp.video.protocols and .imp.video.api to select the right type of creative.

The maximum file size is 2 MB. Video duration limits vary per request. Check the .video.maxduration and .video.minduration for current limits. Recommended lengths are 5–30 seconds for interstitial ads and 20–60 seconds for rewarded ads.
If your video exceeds the allowed duration, the player stops playback automatically. The video loops until the user closes the ad.

Yandex Mobile SDK supports companion ads. Check the .video.companionad and .video.companiontype to verify support. If these fields are missing, companion ads aren't available. We strongly advise against sending empty companion objects or passing more than one at once. If a VAST response contains multiple objects, the player selects the first non-empty one in the following order:

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

Pass the companion dimensions inside the <Companion width="720" height="1280"> tag.

Tracking URLs are triggered according to VAST 4.0. For companion ads, CompanionClickThrough and CompanionClickTracking are triggered.

Native content

OpenRTB Native 1.2 is supported across all inventory.

The Title and Main image assets are required for rendering. We recommend passing all available assets for the best performance. All URLs must use https. For media assets, refer to wmin and hmin in the BidRequest.

Asset parameters

Asset ID	Asset name	Description	Data type	Asset type	Limit
1	Title	Title describing the advertised product or service	String	Required	Max 140 chars
2	Main image	Main banner to display	Img	Required	Min 150×150
5	Description	Additional text describing the advertised product or service	String	Recommended	Max 140 chars
9	display_url	Display domain or bundle that opens when the ad is clicked	String	Recommended	Max 50 chars
10	CTA	Call to action rendered on the clickable button	String	Recommended	Max 15 chars
11	Icon	Supplemental icon (favicon) for mobile app ads, usually matching the app store icon	Img	Recommended	Min 50×50

CTV content

CTV content is disabled by default for DSP partners. Contact your account manager for more information.

Only VAST InLine without companion ads is supported. Videos must be horizontal and meet the technical requirements listed in the table below.

Parameter	Requirement
Formats	MP4 (H.264/AVC), MOV (ProRes 422), WebM (VP9), AVI (XviD)
Resolution	Minimum 720p, but 1080p (Full HD) or 4K are recommended
Video bitrate	≥ 8 Mbps (1080p), ≥ 12 Mbps (4K)
Video frame rate	24–60 FPS (native rate, no added frames)
Aspect ratio	16:9 (standard)

Additional capabilities

AutoStoreKit and SKOverlay

AutoStoreKit and SKOverlay are only available for iOS devices (depending on the OS version). They're supported when the BidRequest contains an .ext.skadn object. If your skadnetids are missing, contact your account manager.

When .ext.skadn is passed in the BidResponse, AutoStoreKit and SKOverlay always render together during a single impression. For fullscreen ads, SKOverlay displays by default at the bottom of the screen. AutoStoreKit triggers when the user taps skip (if using an end card) or automatically after 5 seconds of playback.

You can configure AutoStoreKit behavior directly through Yandex SSP. Pass a valid BidResponse value in the .seatbid.bid.ext.skadn.ext.ask field.

Value	Type	Description
null	-	If the flag is omitted, AutoStoreKit displays after the user taps skip. A click triggers automatically.
1	Integer	AutoStoreKit displays after the user taps skip. A click doesn't trigger after AutoStoreKit opens.