Are you a qaing HTML5 ads publisher that has strict rules in place on specifications? Well I am and the publisher I currently work for is getting more and more qaing HTML5 ads offers which need to be QA'd and ensure the qaing HTML5 ads offers meets our specs .
Okay let’s start.
First step is to get the creative to appear in a browser by itself.
There are a couple options of getting the file to appear by itself.
- Save the text doc as a .html
- Load the ad into your ad server and get the direct response from it. See below as an example.
If you have troubles accessing the file by itself? Please use the contact us form or leave a comment and I can help you.
Once you have the ad loading to the browser by itself. In this example I am going to use my browser of choice chrome.
Feel free to use any browser you like as long as it gives you the information required.
- Okay so press f12 on your keyboard or alternatively right click and click and click "inspect element"
- A new window will open.
- Click the Network tab in the top.
Here you will see the files that are attributed to the creative.
Before we start to analyse the file sizes. You will need to know what calls/files to count towards the weight of the creative.
For example if you a publisher and are adding third party scripts for viewabiility tracking, they are calls you can ignore and shouldn't count to the file weight.
So let's take a look at the image below.
If you are like some publishers and follow IAB standards. You will find that the below specs is what needs to be followed, unless you have something a bit different, but that is up to the publishers discretion.
Backup Image = 40KB
Initial/Default Load = 40KB
Polite / Subsequent load= 100KB
Backup Image - I won't go in too much detail here, as this post is more about HTML5 and not backup images. A quick tip as the backup image does not get loaded in this particular execution. You can always use the user agent switcher and change to IE 8 or below.
This will force the ad to display the backup because IE 8 or below doesn't not support HTML5.
Initial/Default Load - Initial load which is the first files that are downloaded by the user. You want to ensure this is set to 40KB or below to prevent loading issues and lets face it, it's good to be able to follow IAB standards as a publisher.
The initial load size of the creative includes only the index.html document.
Polite / Subsequent load - Anything beyond the index.html that would be considered as polite / subsequent load including the enabler and external .js libraries/style-sheets. Please see the screenshot attached for reference.
Note: This particular execution consits of video. So keep in mind you may want to ignore this asset as the IAB standards state an ad unit can have video up 2.2 MB.
So if you look at the "Content " column. You will find there is 2 file sizes.
Top one is size which is the size of response itself.
Bottom is the size of resource that the user is accessing. Thipuplishers is what you want to count towards your file weight.
Unfortunately I haven'f found an easy method of counting except a manual calculator. I will be sure to update once I find an easy way.
Here are some things to consider before running HTML5
- What is the vendors DFA - Double Click for Advertisrs and Sizmek? These are the two main ones used here in Australia.
- Is your publisher certified with the vendor running the Rich media creative?
- What browsers is the ad running on? As mentioned above HTML5 is not supported from IE 8 and below. So it may be an option to exclude these browsers if your publishers are trying to keep a high viewability.
Some HTML 5 Tools
If you found this article useful Please be sure to follow me on twitter or add your comments below.