Технические требования

Требования к HTML-баннерам Yandex SSP

1. Data must be sent as a ZIP archive.

2. Archive size must not exceed 150 KB.

3. The archive may contain one HTML file and several files in JS, JSON, CSS, JPG, GIF, PNG, or SVG formats.

The contents of the __MACOSX folder and .DS_Store files will be ignored in the archive. They are created during the archiving process on Apple Mac OS X platforms and are not needed for creatives to work.

4. File and directory names may contain only: -._~, numbers and Latin letters.

5. All links in banner ad must be relative paths in the ZIP archive. When creating the ad there must not be any external network access. If necessary, all supporting JavaScript libraries must be presented together with the banner ad.

6. The number of files in the archive must be minimized. Combine images into a page of sprites. If necessary, combine JS/CSS/Image documents and include them in an HTML file. The maximum number of files is 50.

7. The banner ad must function correctly in the following browsers: Internet Explorer 9 and higher, Firefox 14 and higher, Safari 5 and higher, Chrome 14 and higher, Opera 14 and higher, Yandex.Browser 14 and higher, and Microsoft Edge. If necessary, the file must consider the browser functions necessary for its correct functioning.

8. The advertised site must open in a new window only if the user clicks on the banner.

9. Clicks on the banner must receive the address of the advertiser’s landing page via yandexHTML5BannerApi.getClickURLNum(1) call for the first click, yandexHTML5BannerApi.getClickURLNum(2) for the second click, etc.

<a id="click1_area" href="#" target="_blank">...</a> 
<a id="click2_area" href="#" target="_blank">...</a> 
<script> 
	document.getElementById("click1_area").href = yandexHTML5BannerApi.getClickURLNum(1); 
	document.getElementById("click2_area").href = yandexHTML5BannerApi.getClickURLNum(2); 
</script>
												

Please note that the previous of this point from link1 is also compatible, functional, and accepted

Clicks on the banner must use the linkN parameter value from the get URL parameters to the HTML document in the following manner:  link1 for the first click, link2 for the second and so on. Such a code can be used:

<script>
	function getUrlParam(name) {
		name = name.replace(/[\[]/, "\\[").replace(/[\]]/, "\\]");
		var regex = new RegExp("[\\?&]" + name + "=([^&#]*)"),
		results = regex.exec(location.search);
		return results == null ? "" : decodeURIComponent(results[1].replace(/\+/g, " "));
	}
</script>

<a id="click1_area" href="#" target="_blank">...</a>
<a id="click2_area" href="#" target="_blank">...</a>
<a id="click3_area" href="#" target="_blank">...</a>

<script>
	document.getElementById("click1_area").href = getUrlParam('link1');
	document.getElementById("click2_area").href = getUrlParam('link2');
	document.getElementById("click3_area").href = getUrlParam('link3');
</script>
													

10. The <META> tag shows the size of the banner file in the following manner:

<meta name="ad.size" content="width=300,height=250">
												

11. The Yandex ad library must be included immediately after the <HEAD> tag:

<HEAD>
	<script type="text/javascript" src="https://awaps.yandex.net/data/lib/adsdk.js"></script>
</HEAD>
												

12. In the banner it is permitted to use external links to several base libraries, included in the developer tools for HTML5: Adobe Edge Animate CCAdobe Flash CC HTML5 CanvasCreateJSGreenSockSwiffy and others. 

Only external links leading to the site of the library's creator can be allowed in the banner.

13. In the archive with the banner there should be a image-stub with the name preloader. Weight stub - no more than 150 kb. The image will go through separate moderation including the size. The image and text will be used for display in browsers not included in the list of support browsers.

14. It is forbidden to use irritating or harmful script behavior: for example, calls for the spontaneous opening of pop-up windows, change of page addresses, etc. The use of browser extensions (flash/java and others) is forbidden.

15. The ad banner must not lead to confusion (obfuscation).

16. It is assumed that the banner must behave identically and uniformly in all environments, on all platforms, each time the banner is opened, over the entire course of the campaign.

17. The ad banner must meet the requirements for CPU usage1

18. Ad materials must meet the requirements set in the document “Banner Ads. Advertising requirements,” on points 3-10.

19. The banner animation should not distract the user or make it difficult for them to view the pages of the website (banners with flashing graphics and/or backgrounds, fast-moving animations, etc. are not permitted).

20. When preparing banners, the use of low-quality graphical elements is not permitted, including:

  • deformed images or images with artifacts resulting from file compression

  • low-resolution (pixelated) images, or images that are blurry.


1 To test the level of CPU usage, advertising materials use a dedicated computer (an Intel® Core™2 Duo CPU P9600@ 2,53 GHz, 2 GB RAM, and 64-800 MB video memory) running Windows 7 Professional 64 bit. This computer is configured in a standard manner to operate in an office. A special page is loaded, which only contains this banner, for testing purposes. No other programs are running at the time.
The CPU load level is evaluated using the Task Manager.
During such tests, the banner should not take up more than 50% of the CPU’s resources based on information in the Performance tab of Task Manager (Update Speed is set to High for the test). If 50% of the CPU’s resources are used for a considerable amount of time (fractions of a second) or the CPU load peaks over 70%, the banner is considered to take up too much of the computer’s resources. RAM usage is not optimized, and no additional utilities or programs are loaded on start-up. After logging in (without any applications running), the amount of memory used by system processes is around 62-63 MB according to the Task Manager.
Top