Interactive banner requirements
The archive and files used in the HTML5 banner must meet the following requirements:
The file and directory names can only contain Latin letters, digits, and the symbols
All links in an HTML5 banner must be relative and lead to other files in the archive.
The maximum size of the index.html file in the archive must be under 500 KB.
The archive will ignore the contents of the __MACOSX folder andDS_Store and Thumbs.db files. These are the operating system's auxiliary files which are not necessary for the HTML5 banner to work.
A click on the banner opens the mobile app (if installed) or the app page in the store (if the app is not installed). Banner clicks must open this page by calling the
|||UNTRANSLATED_CONTENT_START|||<a id="click_area" href="#" target="_blank">...</a> // после элемента "<a href ...></a>" // присваиваем для него значение атрибута href так: <script> document.getElementById("click_area").href = yandexHTML5BannerApi.getClickURLNum(1); </script>|||UNTRANSLATED_CONTENT_END|||
The following banner sizes are allowed: 160×600, 240×400, 240×600, 300×250, 300×300, 300×500, 300×600, 320×50, 320×100, 320×480, 336×280, 480×320, 728×90, 970×250, 1000×120.
Specify the banner size in the
<meta name="ad.size" content="width=300,height=250">
HTML5 banners must follow Yandex Direct rules:
Do not use rapid animations, flickering graphic elements or a flashing background. The time before switching to the next frame should be long enough to read all of the text shown on the frame.
The advertised app or store page must open in a new window (and only after the user left-clicks on the HTML5 banner).
HTML5 banners should display correctly and work the same way for all users on all platforms throughout the ad campaign in the following browsers: Yandex Browser 14 and higher, Google Chrome 14 and higher, Mozilla Firefox 14 and higher, Opera 14 and higher, Internet Explorer 9 and higher, and Microsoft Edge.
In HTML5, you can't use video or audio clips, script behavior that is annoying or malicious (like scripts that launch pop-ups or spoof IP addresses), browser extensions or plugins (Adobe Flash and others). The banner source code should not be obfuscated, meaning it should not be difficult to analyze.
HTML5 banners must meet CPU utilization requirements.