AD SPECS & GUIDELINES

Specs & Delivery

Files and size restrictions - 3rd Party Tags - Desktop

  • We do not accept keyword blocking tags. If you do require us to exclude specific topics or keywords please request
    at the time of booking

  • Autovia does not allow the collection of our users data by 3rd parties via cookies and pixels. If you do wish to utilize the Autovia user data segments please let us know.

  • Autovia does not allow any third party tracking implementation on content across our sites, sponsored or otherwise. At Autovia, we use Google Analytics to monitor and track site performance. If you require us to supply this campaign data please request at the time of booking

  • We only accept HTML5 via 3rd Party vendors (3rd Party JavaScript tags)

  • Tags must accept third party click tracking.

  • Tags must be able to accept cache-busting code.

  • Tags code must be provided as HTTPS (Preferably DFP Redirects)

  • Tags should not be frequency capped at the third-party side unless approved in advance.

  • Tags must utilise the document.append method rather than document.write

  • Tags must not utilise HTML local storage

  • Maximum Video & Animation Frame Rate 24 fps

  • Maximum Animation Length 30 sec

  • Maximum Video Length Unlimited

  • Maximum CPU Usage 40%

  • Maximum Time for visualisation to start 1 sec

  • Audio Initiation Must be user initiated (click for sound)

  • Hot Spot Not to exceed 1/4 of the ad, must NOT initiate audio

  • Z-Index Range 0 - 4,999

  • Minimum Required Controls Video must include: play, pause and mute

  • Labelling Requirements Ad unit content must be clearly distinguishable from normal web page content

  • Submission Lead-Time Min. 6 days before campaign starts


  • Initial file load: 100kb - Includes all assets and files necessary for completing first visual display of the Ad

  • Cached JavaScript / Shared Libraries - It is our policy to not exempt any javascript load sizes just because they are thought to be "cached" which is in line with IAB guidelines "For calculating ad file weight, all files for the ad, including those shared libraries not exempt by the publisher or ad server, must be included as part of the maximum file weight calculation.”

  • Host-initiated subload: 1MB where allowed, additional files may load one second after the browser domContentLoadedEventEnd event. The ad should be able to “listen” for the browser domContentLoadedEventEnd event before subsequent files beyond the initial max file size may be loaded

  • User-initiated file size: 1.5 MB for creative files, 10 MB for creative & video combinedAds that allow additional file size for host initiated subload also allow for unlimited file load after user-initiated interaction. User initiation is the willful act of a user to engage with an ad. Users may interact by clicking the ad (or a portion of an ad).

  • Max number of host-initiated file requests: 30 file requests during initial file load and host-initiated subload. Unlimited file requests allowed after user-interaction.

  • HTML5 Note (IAB): HTML5 introduces new options for developing ads. IAB has developed an “HTML5 for Digital Advertising” guide to help ad designers provide ads in HTML5 unit that will perform more successfully across the display advertising ecosystem. Please review this document and adopt its recommendations to help improve HTML5 ad performance in the industry.

The initial file load size should not exceed 100 KB. This is the size of the index.html file that is initially fetched from the ad server. It should contain the required logic for the ad and manage asset acquisition. You should measure the ad file size after compressing it to a zip file. The archive must include all the assets and libraries used by the creative. If the ad contains multimedia formats (e.g. video/audio) the overall size should not exceed 10 MB. This restriction is changed to 1.5 MB if the multimedia assets are loaded from YouTube or any other optimized video delivery platform.

If you decide to host your assets on your own Content Delivery Network (CDN), you still must provide them as part of your creative package in order to allow us to monitor for any potential issue regarding performance and delivery.

Optimization

Ensuring proper optimization is critical to provide highly performing creatives. High latency ads will show poorer performance as the user may have scrolled it out of view before it is completed loaded. You may want to consider multiple network speeds and reliability when developing an HTML5 creative.

The Internet Advertising Bureau (IAB) provides a list of products and services - mostly free - on their wiki that you can use for code and asset compression. Furthermore, we recommend that you use base64 encoded images whenever possible in order to reduce the number of network calls. This is particularly appropriate when dealing with small size images (e.g. logos).

Ad server features

Autovia uses Google Ad Manager (GAM) to serve all ads. This allows us to provide targeted delivery and a powerful reporting platform.

GAM is setup to use asynchronous rendering across our portfolio ensuring that ad latency does not impact the overall user experience. But, in that respect it is crucial that you optimize your ad code so it does not rely on page elements (e.g. jQuery) as they may not be available at the time your creative is rendered. Additionally, the creative will be served in an friendly iFrame. While this setup allows for content script to access the host page, it should be avoided and measures should be taken to avoid ID collision as the same tag could be used multiple times on the same page.

Files and size restrictions - Image Files

  • Image files can be supplied as gif or jpeg files

  • Maximum File Size = 50kb

Files and size restrictions - HTML5 Raw Files

  • We only accept HTML5 via 3rd Party vendors (3rd Party JavaScript tags)

Programmatic Guaranteed

  • Due to delivery issues we prefer deals from Buyer Seats in a "Production" rather than "Alpha/Beta" state

  • All PG campaign must adhere to our standard ad specs for 3rd Party tags listed in the section above

Glossary

Formats

Cascade: A specific creative served through the Billboard slot (also with the same contracted dimensions) that, once clicked, "folds" down the page resulting in an expanded unit of double the height. This can be clicked again to "fold" out to a triple height unit. Further interactions cause the unit to scroll through any additional "panels" of content.

Fireplace: A Skin/Wallpaper that takes up the sites gutters as well as a fixed space above the site. This is normally designed as one consistent piece.

Integrated Interscroller: View demo. Combines a Skin and Full Width Billboards and in page MPUs (for desktop) and Full Width MPUs for Mobile to give the impression of a fixed ad appearing through cut out areas of the site.

Responsive slot/creative: These slots and the ads within, are designed to be the full width of the site at any given browser size. As the browser width changes the ad adapts, moving its content around to fit the new dimensions. The height is usually kept fixed to simplify the build but this is not a requirement.

Slider: This format includes the skin, leader, and MPU slot and can be activated by clicking on any of these, causing the whole site to slide off and enabling use of the full screen. Only suitable for desktop.

Tile format/creative: A creative that folds out on user interaction (click or 3 second hover) to a large expanded overlay. This can be built into any standard display unit but works best with MPUs and HPUs.

Toggle creative: Refers to the functionality of switching an ads content to one of (up to) several different states. Depending on the creative this could be "good vs evil", switching between character bios, etc.

Wallpaper: Very similar to a skin in that it takes up the real estate to the left and right of a site (Also known as the gutters). Wallpapers, as with skins can be integrated into the Billboard slot as well as around the top of the site. (Known as a fireplace/pushdown skin)

Functionality that can be used within formats

Interscroller: A scroll effect added to a unit that gives the illusion that the ad is static behind the site and the unit is a windows into the creative. Any unit can have interscroller functionality added to it however it is recommended for simple non­interactive creatives. (The original concept was used on a full width DRS type unit)

Video Skin and Video Skin Switcher: View demo The video skin places a looping video around the sides of the site content. Additionally, it can create space between the site menu and the top of the page to increase the amount of media on display and to provide a more reliable space for branding and messaging. The Video Skin Switcher format has the extra functionality to allow for up to 4 videos, with supporting Headline Text, CTA's and Tracking. As more video's are added, next and previous buttons appear allowing the user to view a different video skin with different messaging and CTA's.

Sticky Inview MPU/HPU: The Desktop MPU/HPU slot in the right hand rail of Autovia sites.

Parallax: The visual effect of the background, mid ground and foreground of a scene moving at different speeds relative to each other. This can be animated automatically or activated on some sort of event, like the user scrolling. This is a purely aesthetic effect.

Pushdown: The functionality of a slot to push content down when it is expanded. (As opposed to overlaying content)

Other terms

Gutters: The areas immediately to the left and right of the site. These tend to be between 135px and 250px in width for meaningful content.