ONLINE ADVERTISING SPECIFICATIONS

Advertorials
Videos
TEADS Video
- regarding heavy ad intervention
HTML5
- Click Tracking Macro implementation
HTML5 mobile
Third-party hosted ads
- mobile requirements

Super Size
Web Leaderboard (728x90)
 Web Extended Leaderboard (960x90)
Web LARGE MREC (LREC) (300x600)
Web MREC (300x250)
Billboard (960x250)
Web Rails (160x750)
Background Skin

eNewsletter Banner (600x90)
eNewsletter MEDIUM Banner (468x60)
eNewsletter MREC
eDMs


ADVERTORIALS

Please provide the following:

HEADLINE (mandatory)
TEASER TEXT (mandatory)
ARTICLE (mandatory) 250 words Max
ARTICLE PIC (mandatory)
Any other pics to be featured in a gallery (optional)

back to top


VIDEOS

Videos need to be uploaded to clients own YOUTUBE or VIMEO account and link to uploaded video supplied to us.

back to top


TEADS InRead VIDEOS - Embedded in article pages

Third-party hosted tags accepted:

Material deadline 5 working days prior to start date

*Regarding Heavy Ad Intervention

Heavy Ad Intervention is a new feature on Chrome and Edge browsers that will block all ads considered "heavy" on the user's device resources (unless the user interacts with the ads by clicking on them): either because they use too much network bandwidth (>4MB) or because they use too much CPU.

Heavy Ad criteria:

 

back to top

HTML5 ad items

A Rich Media Ad contained in a zip archive.

HTML5 is not available for eNews ads

Requirements:

 

IMPORTANT

HTML5 and Third-party tags require implementation of click tracking macros for reporting purposes.

For instructions, see more information here: http://adbutler.com/help/article/adbutler-click-tracking-html5

Click Macro Implementation

Add the macro [TRACKING_LINK] or [TRACKING_LINK_ENCODED] as your link or JavaScript in the file named "index.html".

Consult with your ad tag provider to know where you need to insert tracking macros and whether you need to use a basic TRACKING_LINK or TRACKING_LINK_ENCODED macro.

An example of a 3rd-Party Ad Tag with included tracking link macros:

JavaScript Method examples

In the of the HTML file, add:

<script>window.clickTag = '[TRACKING_LINK]';></script>

In the click handler function of your ad, ensure that window.clickTag is used as the redirect URL:

window.open(window.clickTag, '_blank');

Or wherever you would usually use the click-thru URL, use the click macro [TRACKING_LINK] or [TRACKING_LINK_ENCODED] instead.

For example:

Basic Link Method example

If JavaScript is not being used for click redirection, introduce the Macro as:

<a href="[TRACKING_LINK]" target="_blank">CLICK ME</a>

Or wherever you would usually use the click-thru URL, use the click macro [TRACKING_LINK] or [TRACKING_LINK_ENCODED] instead.

Provide the destination URL to the advertising co-ordinator and we will add it to the campaign in our ad server.

See the following link for more examples of implementing the tracking macro: https://www.adbutler.com/help/article/examples-of-common-3rd-party-ad-tags

Note: without click tracking macros iplemented, accurate reporting cannot be supplied.

Other specs:

 

Creative guide recommendations: http://advertising.aol.com/specs/guidelines/creative-guidelines

Mobile Requirement for HTML5
Leaderboard / Extended Leaderboard / Billboard

If booking an HTML5 leaderboard, extended leaderboard or billboard, also design a mobile placement at 300x50 (leaderboard) / 300x100 (extended leaderboard) / 300x150 (billboard) and supply an additional HTML5 package at this size, as well as the desktop size.

 

Backup image

Please provide a backup jpg/gif image file (under 250kb) in case of any delivery or platform compatibility issues with the HTML5.

 

Working time

Because of the variability in the HTML5 format, we request all final and approved HTML5 code and assets supplied five business days prior to launch for loading, testing and potential adjustment to meet compatibility with our ad server system.

 

All HTML5 content must be supplied five business days prior to launch for testing to verify compatibility with our system.

IMPORTANT

HTML5 requires implementation of click tracking macros.

For instructions, see more information here: http://adbutler.com/help/article/adbutler-click-tracking-html5

Without click tracking macros implemented, accurate reporting cannot be supplied.

Web browser compatibility

Some web browsers, such as Internet Explorer, may have problems with certain HTML5 elements

 

Resources and tools

Current list of HTML5 enabled browsers:

 

For more information, see the

 

 

Third-party tags

Using a custom HTML / 3rd-Party ad tag you can provide a block of HTML code for a custom ad or tracking script.

If you wish to receive reporting from Yaffa on your third-party ad item, you will need to insert our click tracking macros.

For more information, see: http://adbutler.com/help/article/serving-3rd-party-ad-tags

See the following link for more examples of implementing the tracking macro: https://www.adbutler.com/help/article/examples-of-common-3rd-party-ad-tags

Further details for 3rd Party INS Tag: https://adbutler.com/help/article/third-party-ins-tag

Third-party ad tags must be supplied five business days prior to launch for testing to verify compatibility with our system.

Third party ads must be within Google's Heavy Ad criteria in order to display in Chrome web browsers.* See more »

Contact your third-party ad server for all assistance with hosting, loading and troubleshooting on their platform.

Suggested third-party vendors:


More: http://advertising.aol.com/specs/vendors

Mobile Requirement for Third-Party ad tags
Leaderboard / Extended Leaderboard / Billboard

  • additional size required for correct display on mobile

If booking a third-party leaderboard, extended leaderboard or billboard, also design a mobile placement at 300x50 (leaderboard) / 300x100 (extended leaderboard) / 300x150 (billboard) and supply an additional third-party ad tag at this size, as well as the desktop size. Or supply a backup jpg/gif/png image file size under 250kb.

Backup image

Please provide a backup jpg/gif/png image in case of any delivery or platform compatibility issues with the third-party hosted ads.

back to top


SUPER SIZE

back to top


WEBSITE LEADERBOARD

 

HTML5 must be within Google's Heavy Ad criteria in order to display in Chrome web browsers.* See more »

**HTML5 Mobile Requirement: also design for mobile at 300x50 and supply additional HTML5 package at this size (one at the desktop size, one at the mobile size) See more HTML5 specs here »

 

back to top

WEBSITE EXTENDED LEADERBOARD

 

**HTML5 must be within Google's Heavy Ad criteria in order to display in Chrome web browsers.* See more »

HTML5 Mobile Requirement: also design for mobile at 300x100 and supply additional HTML5 package at this size (one at the desktop size, one at the mobile size) See more HTML5 specs here »

back to top

WEBSITE LARGE MREC (LREC)

 

**HTML5 must be within Google's Heavy Ad criteria in order to display in Chrome web browsers.* See more »

back to top

WEBSITE MREC

 

**HTML5 must be within Google's Heavy Ad criteria in order to display in Chrome web browsers.* See more »

back to top

BILLBOARD

 

**HTML5 must be within Google's Heavy Ad criteria in order to display in Chrome web browsers. See more »

HTML5 Mobile Requirement: also design for mobile at 300x150 and supply additional HTML5 package at this size (one at the desktop size, one at the mobile size) See more HTML5 specs here »

back to top

WEBSITE RAILS

Rail ads appear in the external left/right-hand side margin of the website.

Not visible in mobile view.

Note: only visible for users with a screen resolution of 1360x765 or more (web browser zoom 100%).

Not visible in mobile view.

 

**HTML5 must be within Google's Heavy Ad criteria in order to display in Chrome web browsers. See more »

Creative guide to RAILS:

back to top

BACKGROUND SKIN

Note: only visible for users with a screen resolution of 1280x600 or more (web browser zoom 100%).

HTML5 is not available in this position.

Not available in mobile view.


A guide to the 'safe area':

back to top


ENEWSLETTER AD SPECIFICATIONS

HTML5 is not available for email ads.

ENEWS BANNER

back to top

ENEWS MEDIUM BANNER

 

back to top

ENEWS MREC

back to top


eDMS

eDM GUIDELINES

Material must be supplied in HTML code format, which has been specifically designed for email (i.e. not a webpage)

We do not edit supplied HTML. It needs to be provided as complete, tested and final.

Material supply deadline is 10 WORKING DAYS prior to send date

Hosted images: For the creative to display properly, all associated images need to be hosted on a public facing server at your end, and their full source location referenced in the HTML code (e.g. <img src=“http://www.yoursite.com/public_images/hello_world.jpg”>).

Supplied images: Alternatively, images can be supplied for upload and local hosting alongside the HTML.


Total package size should not exceed 5MB

JavaScript and Flash are not accepted as these technologies are generally not supported by email clients.

Additional requirements:

MANDATORY DISCLAIMER TO BE INCLUDED

Download the eDM footer code here »

For more detailed guidelines on creating the EDM please click here (http://covers.yaffa.com.au/HTML-GUIDELINES.html)

ALTERNATIVE STATIC eDM OPTION - for clients who can't provide HTML code

If a client does not have access to an HTML designer and cannot supply HTML code, they can provide their eDM as a static image:

back to top

© 2020 Yaffa Media Pty Ltd.