SHORTHAND
Please provide a clear, specific, written brief with visual storyboard and all final and approved supporting assets.
Planning tips:
- https://support.shorthand.com/en/articles/3-story-planning-tips
- https://support.shorthand.com/en/articles/85-checklist-for-planning-a-multimedia-story
Examples:
Storyboard:
Outline the Shorthand story content section-by-section and detail the onscreen effects/transitions
Asset specifications:
Note, the dimension of assets depends on how the image/video will be used (e.g. full size, background, reveal, scroll-mation, etc.)
- https://support.shorthand.com/en/articles/13-images
- https://support.shorthand.com/en/articles/18-safe-area-guides
- https://support.shorthand.com/en/articles/17-video-encoding-guidelines
Material deadline 5 working days prior to start date
SPONSORED CONTENT
Please provide the following:
- HEADLINE (mandatory)
- SUGGESTED TEASER/SUBHEADER TEXT (optional)
- ARTICLE (mandatory) 800 words Max
- ARTICLE PIC (mandatory, HIGH RES preferred)
- Any other pics to be featured in a gallery (optional, also HIGH RES)
- Any other links to be included (optional)
Copy to be provided in WORD format (preferred).
The editorial team will review the piece, make edits if necessary, pass the piece on for final client approval before publication.
The piece will be published on the News page, Home page, E-Newsletter and Social post.
Material is due at least THREE DAYS prior to publication.
TEADS (InRead) WEBSITE VIDEO (embedded in article pages)
- File type: mp4
- Maximum file size: 3MB (low file weight important due to Heavy Ad Intervention* block in web browsers)
- Ratio: 16:9
- Dimension: 1280x720px (Responsive to the page level)
- Length: 15/20 sec max
- FPS: 24
- Click-Thru URL (or VAST redirect)
Third-party hosted tags accepted:
- 1x1 VAST
- VPAID
- JS
- All tags must be SSL only
- Maximum file size of hosted creative: 3MB (low file weight important due to Heavy Ad Intervention* block in web browsers)
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:
- Uses the main thread for more than 60 seconds in total
- Uses the main thread for more than 15 seconds in any 30 second window
- Uses more than 4 megabytes of network bandwidth
TEADS InRead SCROLLER (embedded in article pages)
- Maximum file size: 200kb
- Image file: jpg/png
- Dimensions: 700 x 1600px
- Design to Landscape safe area: https://misc.teads.tv/demo/product/specs/Viewable%20Display/Scroller.pdf
- Click-Thru URL
- Pixels Accepted: SSL 1x1
- Material deadline 5 working days prior to start date
SUPER SIZE
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 250KB
- 960 (w) x 500 (h) pixels
- Image file: gif/png/jpg
- Material deadline 5 working days prior to start date
WEBSITE LEADERBOARD
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 728 (w) x 90 (h) pixels
- Image file: gif/png/jpg
- Material deadline 5 working days prior to start date
HTML5 creative:
- HTML5 requires implementation of a tracking macro. See more HTML5 specs here »
- HTML5 for mobile requires an additional HTML5 package at 300x50, as well as the desktop size.
- Be within Google's Heavy Ad criteria in order to display in Chrome web browsers*
Third-party tags:
- Third-party tags require implementation of a tracking macro. See more third-party specs here »
- Supply backup image at 728x90 (jpg/gif/png)
- Third-party tags for mobile require an additional tag and backup image at 300x50, as well as the desktop size.
- Be within Google's Heavy Ad criteria in order to display in Chrome web browsers*
HTML5 & third-party tags require implementation of a click tracking macro. Otherwise accurate reporting cannot be supplied by AdNews. For further instructions, see information for HTML5 here: http://adbutler.com/help/article/adbutler-click-tracking-html5. And examples of third-party tag implementation here: https://www.adbutler.com/help/article/examples-of-common-3rd-party-ad-tags
*Regarding Heavy Ad Intervention
Heavy Ad Interventions 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:
- Uses the main thread for more than 60 seconds in total
- Uses the main thread for more than 15 seconds in any 30 second window
- Uses more than 4 megabytes of network bandwidth
WEBSITE LEADERBOARD (Extended)
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 960 (w) x 90 (h) pixels
- Image file: gif/png/jpg
- Material deadline 5 working days prior to start date
HTML5 creative:
- HTML5 requires implementation of a tracking macro. See more HTML5 specs here »
- HTML5 for mobile requires an additional HTML5 package at 300x100, as well as the desktop size.
- Be within Google's Heavy Ad criteria in order to display in Chrome web browsers*
Third-party tags:
- Third-party tags require implementation of a tracking macro. See more third-party specs here »
- Supply backup image at 960x90 (jpg/gif/png)
- Third-party tags for mobile require an additional tag and backup image at 300x100, as well as the desktop size.
- Be within Google's Heavy Ad criteria in order to display in Chrome web browsers*
HTML5 & third-party tags require implementation of a click tracking macro. Otherwise accurate reporting cannot be supplied by AdNews.
For further instructions, see information for HTML5 here: http://adbutler.com/help/article/adbutler-click-tracking-html5.
And examples of third-party tag implementation here: https://www.adbutler.com/help/article/examples-of-common-3rd-party-ad-tags
Third-party hosted and HTML5 ads must be within Google's Heavy Ad criteria in order to display in Chrome web browsers. See more »*
WEBSITE STRAPLINE
Not visible in mobile/tablet view.
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 960 (w) x 40 (h) pixels
- Image file: gif/png/jpg
- Material deadline 5 working days prior to start date
WEBSITE LARGE MREC (LREC)
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 300 (w) x 600 (h) pixels
- Image file: gif/png/jpg
- Material deadline 5 working days prior to start date
HTML5 creative: also supply a backup image at 300x600 (jpg/gif/png). See more HTML specs here »
Third-party hosted and HTML5 ads must be within Google's Heavy Ad criteria in order to display in Chrome web browsers See more »*
WEBSITE MREC
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 300 (w) x 250 (h) pixels
- Static OR Animated Gif/PNG/Jpeg file
- Material deadline 5 working days prior to start date
HTML5 creative: also supply a static image at 300x250 (jpg/gif/png) as a backup. See more HTML specs here »
Third-party hosted and HTML5 ads must be within Google's Heavy Ad criteria in order to display in Chrome web browsers See more »*
BILLBOARD
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 250KB
- 960 (w) x 250 (h) pixels
- Static OR Animated Gif/PNG/Jpeg file
- Material deadline 5 working days prior to start date
HTML5 creative: also supply a static image at 960x250 (jpg/gif/png) as a backup. See more HTML specs here »
Mobile requirement: HTML5 Billboard
- additional size required for correct display on mobile
If booking an HTML5 billboard, also design a mobile placement 300x150 (billboard) and supply an additional HTML5 package or third-party tags at this size, as well as the desktop size.
HTML5 requires implementation of click tracking macros. For instructions, see more information here: http://adbutler.com/help/article/adbutler-click-tracking-html5
Third-party hosted and HTML5 ads must be within Google's Heavy Ad criteria in order to display in Chrome web browsers See more »*
WEBSITE RAILS
(Sometimes called 'gutters' or 'wings')
Rail ads appear in the external left/right-hand side margin of the website.
Note: only visible for users with a screen resolution of 1360x765 or more (web browser zoom 100%).
Not visible in mobile/tablet view.
- 160 pixels (w) x 750 pixels (h) each gutter ad
- File size must be no larger than 200KB
- 2 x jpg/png/gif or third party hosted ad tags
- Clickthrough URL/Web Address needs to be provided
HTML5 creative: also supply static images at 160x750 (jpg/gif/png) as a backup. See more HTML specs here »
HTML5 requires implementation of click tracking macros. For instructions, see more information here: http://adbutler.com/help/article/adbutler-click-tracking-html5
HTML5 ads must be within Google's Heavy Ad criteria in order to display in Chrome web browsers See more »*
Guide to RAILS:
- Rails should be used to support the MREC/LARGE MREC messaging and draw users to an experience.
- Rail imagery is aligned to top of page and sit out slightly away from the page edges.
- Rail imagery is set in position (does not scroll with page).
- Rails can click through to the client website. Clickthrough URL/Web Address needs to be provided
- Property brand cannot be obscured or encroached upon (any logos, images or text should be positioned at least 150px from the top of the page).
- Rails must not display any external URLs on the creative.
- Rails must be in keeping with the style of the property.
- Rails can contain subtle animation; flashing, blinking or excessive animations will not be approved.
- Final creative is subject to approval by YAFFA and must be submitted 5 working days prior to live date.
BACKGROUND WALLPAPER/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.
- 1920px wide by 1200px high
- Static JPEG or GIF only
- Design to safe area (see below)
- File size must be no larger than 250kb
- Clickthrough URL/Web Address needs to be provided
A guide to the 'safe area':
- for small screens, contain essential information towards top of image and within the area 465px from left/right edge of image
- display of content outside this area will depend on individual user's screen resolution
- no content will be visible in the centre 990px of image (do not fill with white space)
- click here for the safe area guide
ENEWSLETTER AD SPECIFICATIONS
HTML5 is not available for email ads.
ENEWS BANNER
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 580 (w) x 120 (h) pixels
- Static or animated GIF file or static JPEG file only
- Third party tags, urls & tracking pixels can not be used for enewsletter ads
- Note: animated GIF files are not supported by Outlook 2007/2010 (ad will appear as first frame of animation only). Other Outlook versions as well as most email providers, such as Gmail, Hotmail & Yahoo, should see the animation as intended.
ENEWS MREC
- Clickthrough URL/Web Address needs to be provided
- File size must be no larger than 200KB
- 300 (w) x 250 (h) pixels
- Static or animated GIF file or static JPEG file only
- Third party tags, urls & tracking pixels can not be used for enewsletter ads
- Note: animated GIF files are not supported by Outlook 2007/2010 (ad will appear as first frame of animation only). Other Outlook versions as well as most email providers, such as Gmail, Hotmail & Yahoo, should see the animation as intended.
ENEWSLETTER VIDEO
- File format: mp4 preferred (others accepted .mov, .avi, .divx, .webm, .ogg, .xdiv, .flv, .3gp or or YouTube video URL)
- File weight limit 120MB
- Duration: maximum of 900 seconds and a minimum of 2 seconds
- Dimensions: recommended video width 600 pixels wide (maximum width 750 pixels, minimum width 580 pixels)
- Clickthrough URL/Web Address needs to be provided
Due to incompatibility with video some email programs may display a 10 second preview or a fallback image instead.
More about email compatibility: https://blog.viewed.video/technology/video-in-email-compatibility-and-support#Video-experience-based-on-user-technology-Discover
EDMS
EDM GUIDELINES
JavaScript and Flash are not accepted as these technologies are generally not supported by email clients.
- Material must be supplied complete in HTML code format, which has been specifically designed for email (i.e. not a webpage)
- For the blast to work properly, all the logos/images need to be hosted on a public facing server at your end, and their full location included in the html code (e.g. http://www.yoursite.com/public_images/hello_world.jpg" Hello World ).
We do not edit the supplied HTML. It needs to be final, tested and complete. - Client must supply the email blast Subject Line
- Client list of Email addresses need to be provided for testing and approvals
- Max design width of 600 pixels will work best. Consider those recipients who open/click/transact on mobile devices
- Total package size should not exceed 5MB
- The EDM will be sent to our database of subscribers at 2:00pm unless otherwise specified
- EDM deadline 10 WORKING DAYS prior to start date
- All third party tracking tags need to be inserted to the EDM before supplying to us
- Include the AdNews footer code at the bottom of your EDM so subscribers can manage their preferences and unsubscribe:
THE FOLLOWING DISCLAIMER MUST BE INCLUDED
Download the eDM footer code here »
For more detailed guidelines on creating the EDM please VIEW HERE
ALTERNATIVE EDM OPTION - for clients who can't do the HTML coding.
If client who can design or have access to a designer but can not HTML CODE the EDM they can simply provide the following:
- The designed artwork (jpg) at 600px wide by (900px high (max) )
- 250kb max file size
- Design should only refer to 1 clickthrough link only
- Link needs to be provided
- Client must supply the email blast Subject Line
- Client list of Email addresses need to be provided for testing and approvals
RICH MEDIA including 3rd party hosting
- 40 kb Max. Polite File Size
- 200 kb Max. Polite Video File Size
- 4mb (preloaded with no user initiation)
- Mouse cursor hovers over ad for at least one second or click to open, expanding panel closes immediately on mouse-off
- Clearly defined calls-to-action should be provided "Close X" on expanded panel and "Expand" on collapsed panel Audio Initiation
Must be user initiated (on click: mute/un-mute); default state is muted Required Video / Audio Controls
Play, Pause, Mute, Volume Slider
These are standard 3rd party ad specs obtained from IAB Australia guidelines located below.
http://www.iabaustralia.com.au/uploads/uploads/2013-09/1380477600_c4b58db930808f5de9661bb0ae73bb10.pdf
HTML5 ad items
A Rich Media Ad contained in a zip archive.
Requirements
- Archive contains at least one html file.
- Design should be responsive with a max width to ad dimension
- All resources referenced by relative URLs.
- Relative URLs match file path in archive.
- Click tracking macros are to be implemented (details follow »)
- Supply a static backup image (jpg/png/gif)
- All assets supplied 5 business days before launch
- Be within Google's Heavy Ad criteria in order to display in Chrome web browsers.* See more »
NOTE: HTML5 is not available for eNews ads
IMPORTANT - Click tracking macro required for HTML5 & third-party hosted creative
HTML5 requires implementation of click tracking macros.
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".
- [TRACKING_LINK] - unescaped click tracking macro
- [TRACKING_LINK_ENCODED] - escaped click tracking macro
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:
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:
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 AdNews and we will add it to the campaign in our ad server.
Note: without click tracking macros implemented, accurate reporting cannot be supplied.
Other specs:
- Should support GPT Sync, Async and Legacy Dart rendering
- Should always conform to the ad boundary and visibility that are set by the site, in particular when ad div is relocated or hidden on window resizing
- Initial file size = 40KB
- Total file size = 200kb (without video), 1MB (true video streaming only, progressive download must be on user click)
- Animation: maximum 30 seconds in duration
- Looping: no limit
- Frame rate per second: 24 fps or less
Creative guide recommendations: http://advertising.aol.com/specs/guidelines/creative-guidelines
MOBILE REQUIREMENTS
HTML5 Leaderboard / Extended Leaderboard / Billboard
- additional size required for correct display on mobile
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/png image file in case of any delivery or platform compatibility issues with 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 supplied files must be contained in a zip archive
- the html file must be in the root directory of the zip archive
- all other supplied assets and code can be in the root or sub-directories
- a static backup image should be supplied (jpg/png/gif) max. file size 200kb
- click macro tracking must be implemented
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, accurate reporting cannot be supplied in reports by AdNews.
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
Reference
For additional information about scripting and click macros:
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, accurate reporting cannot be supplied in reports by AdNews.
All HTML5 content must be supplied five business days prior to launch for testing to verify compatibility with our system.
Third-party supplied 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 AdNews 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.
Contact your third-party ad server for all assistance with hosting, loading and troubleshooting on their platform.Suggested third-party vendors: