Problems with HTML5 banner ads like not loading, not animating or not being click-through enabled even though they are working perfectly on your local test environment can take a while to solve. These kinds of errors mostly occur because of a small detail that you missed. This post will walk you through all the steps needed to troubleshoot an HTML5 banner ad in the correct order.
Check the clickTag is wired correctly
This variable must be wired up to the clickable region of the banner and set to the correct URL. Check that the variable is set to the correct click URL for the ad, and that it has been correctly attached to the region of the banner which is to be clicked. Do not confuse this with the link tag which is used to specify a URL which is to be followed if the user clicks on something other than a clickable region.
Open the developer console for errors
One JavaScript error is enough to prevent a perfectly fine ad from displaying at all – even without any error messages in the ad itself. Inspect the ad in your browser by right-clicking on it and open the developer console (the Console tab). Most errors are quite easy to spot within this console and will even direct you to the faulty line within the HTML code of your ad.
Check the zipped file size
It’s very easy to overlook the file size when zipping up your HTML5 banner. The maximum file weight for uploaded ad materials is usually published on the ad network’s website (e.g. 150KB for FLASH; 500KB for HTML5; and so on for other formats), but it is often overlooked. The file might even work perfectly well for you on local test PCs, but upload it to the ad network’s server and you get an error message. It’s simply too big to be uploaded. And the reason for this is usually a single oversized file or a collection of big images, which can easily be compressed.
Check your file paths are relative
All file references within the HTML, CSS and links to external files must be defined with relative paths, for example: images/logo.png instead of C:/Users/yourname/Desktop/banner/images/logo.png. Also external file references must not be defined with local file URLs (e.g. file://C:/Users/yourname/Desktop/banner/images/logo.png). Even though they may work on your local machine because of the local environment setup, they will fail when uploaded to a remote server, because the local environment is not available on the server. See also HTML 5 Ads.
Run it through the platform’s own validator
Opening an HTML5 banner in a browser on your local machine will only confirm whether your banner works for you, not whether it complies with the requirements of an ad network. The majority of platforms now offer a preview and/or validator of your banner within their own environment. This tool can test for a range of things including file size, clickTag setup, maximum dimensions and prohibited scripts. It’s well worth using these tools to test your banner for potential problems before resubmitting.
Check the loop count and duration

Most networks of HTML5 banners set a time frame for how long an animation can run and how many times it can be played back before it has to change to a static end frame. Mostly this is between 15-30 seconds and up to 3 times replayed. As soon as an animation runs on indefinitely it can get muted or can even freeze on the first frame. Therefore in your animation settings you have to set a finish after a certain amount of time instead of infinitely looping.
Test across browsers and devices
The banners can behave differently on other desktop browsers and even on different models of mobiles, especially when it comes to the in-app browsers of applications such as Instagram, Facebook, etc. This is because each of the different environments can interpret the HTML5 banners, fonts and videos in different ways and, in some cases, even block certain features of the HTML5 banners. It is therefore good practice to test your banners on at least one desktop browser and one mobile browser and also within the app in which they are intended to appear.
Confirm the static backup image works
Check the static backup image for the ad has been included as part of the submission. The static file must be the correct size for the ad and include the key message of the banner plus the brand. The static image may be displayed to users who are unable to view HTML5 ads (for example older browsers, some mobiles, some in-app browsers and some placements). A missing or blank static image can result in the entire submission bouncing.
Working your way through this list of checks should identify the cause of any failure and, where necessary, provide evidence to support a return to ad submission. The list is relatively short, and covers the vast majority of causes of HTML5 banner failure at the ad submission stage.
Leave a Reply