Guardian Commercial On-line
United Kingdom
Specifications for Guardian Commercial online ad formats. This includes all standard and expandable ad formats and all new ad formats along with delivery information and contact details. Should you have any queries, please do not hesitate to contact our Ad Operations team at:
guardian.adops@guardian.co.uk
This Publication carries on-line advertising only. For information on our print sections please see our other pages on Specle.
Please take some time to read the following guidelines for different creative applications for use on the Guardian network. We are constantly working with agencies and clients and will keep you informed of developments and extensions to these guidelines.
Non-expandable creative
Maximum File Size for all of below is 40k
MPU: 300 wide x 250 high (pixels)
Skyscraper: 120 wide x 600 high (pixels)
Leaderboard: 728 wide x 90 high (pixels)
Super Skyscraper: 160 wide x 600 high (pixels)
American Super Skyscraper/Double MPU: 300 wide x 600 high (pixels)
Static Super Leader: 900 wide x 250 high (pixels)
Delivery Formats
GU hosted GIF: Send GIF file and clickthrough URL
GU hosted Flash: Send swf file using ClickTag clicktracking method, backup gif and clickthrough url. Please See ‘Flash and Rich Media Instructions’ section on this page for further information on supplying Flash Creatives.
Third Party Hosted: We accept only iFRAME tags and internal redirects. Please include detailed implementation instructions.
Expandable creative
Initial File Size for all of below is 40k
MPU: 900 wide x 500 high (pixels)
Skyscraper: 350 wide x 600 high (pixels)
Leaderboard: 728 wide x 900 high (pixels)
Super Skyscraper: 390 wide x 600 high (pixels)
American Super Skyscraper: 530 wide x 600 high (pixels)
Half-Page: 900 wide x 600 high (pixels)
Expandable Super Header pushdown
Width 900 Length 90
• Auto expands to 900×250 on arrival at page, pushes content down, will auto close after 15seconds
• 900×90 will remain on page inviting users to interact
• Subject to creative approval on news
• Low Frequency
Click to Full Screen (Can be Superbanner, MPU or Half Page Ads)
• Click to open, Click to Close
Notes on expandable creative
We serve ads through an iFrame so require you to provide code to allow the ad to expand.
We fully support expandable creative from the following third parties (other third party ad code will require technical time): Mediamind (Eyeblaster), DART Motif, Flashtalking, Atlas, RM, Mediaplex.
All expandable creative requires editorial approval
Creative must contract on roll-off
Please See ‘Flash and Rich Media Instructions’ section on this page for further information on supplying Flash Creatives.
Page Skin
Width 1600 Length 1200
• No Click To remove
• No Animation of Skins allowed
• Low Frequency
• Only able to run through a Third party and must be rich media
• Agency need to supply the third party with a GIF or JPG – 1600×1200 creative – middle (980 pixels) must be blank
• Third party to provide tag that we traffic as an intrusive ad
• Max weight of creative the third party allows is 300k for Eyeblaster, and 400k for Flashtalking.
General Notes
White Creative: All white and light-coloured creative must have a dark one-pixel border.
Click into new window: All ads must click into a new browser window.
Browser compliance: We target all rich media ads to all versions of IE and Firefox unless otherwise instructed. We target gif ads to all browsers unless otherwise instructed.
Rich Media: For Flash, Expandable creative, please See ‘Flash and Rich Media Instructions’ section on this page for further information.Testing: All solutions are subject to final senior editorial approval (rich media campaigns are subject to testing).
Flash Versions: We accept all versions of Macromedia/Adobe Flash up to version 10.
Technical Contact: For all rich media campaigns we need the name of a technical contact at your end.
Lead Time: Please allow 2 days lead time for gifs and 5 days for all other creative.
Sound: All sound must be user click activated.
Misleading Ads: We will not carry any form of advertising that is deemed to be misleading or confusing to our users.
More information: For information on ad types not covered here please contact us directly via the navigation bar on the left of this page.
CPU: We may measure CPU, and reject or remove ads that drive the CPU too high (i.e. negatively affect the speed of the page load or certain page functionality) Please See ‘Flash and Rich Media Instructions’ section on this page for further information on supplying Flash Creatives.
Guidelines on Photosensitive effects
(affecting people with complaints such as epilepsy and migraine)
General flash threshold
A sequence of flashes or rapidly changing image sequences where both the following occur:
1. The combined area of flashes occurring concurrently (but not necessarily contiguously) occupies more than one quarter of any 335 × 268 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 by 768 pixels and…
2. There are more than three flashes within any one-second period.
Note: For the general flash threshold, a flash is defined as a pair of opposing changes in brightness of 10% or more of full scale white brightness, where brightness is calculated as .2126*R + .7152*G + .0722B using linearised R, G, and B values. Linearised-X = (X/FS)^2.2 where FS is full scale (usually 255 today). An “opposing change” is an increase followed by a decrease, or a decrease followed by an increase.
Red flash threshold
A transition to or from a saturated red where the following occurs: The combined area of flashes occurring concurrently occupies more than one quarter of any 335 × 268 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 by 768 pixels and there are more than three flashes within any one-second period.
Contacts:
All creative should be supplied to our Ad Operations team at guardian.adops@guardian.co.uk
Any technical queries should be emailed to your Ad Operations Executive
Requests for reports should be made to: guardian.adops@guardian.co.uk
Flash and Rich Media instructions
We will need the following information:
Flash builder/designer name/designer phone number and CPU Usage Guidelines
We will need the following items for each creative:
Both the original flash file (.fla) which has been modified to our requirements as below in the instructions and the corresponding shockwave file (.swf)
Clickthrough URL
Alternative GIF
Whenever a banner is supplied that has a background colour other than black or white, we need the hexidecimal code supplied to us (ie – the 6 figure code made up of letters and numbers).
Instructions and specifications on how to build flash banners.
We can only accept shockwave/flash up to version 10
There are currently several versions of the shockwave/flash player in use. The earlier the version, the higher the penetration of users. There are pros and cons with using earlier or later versions of the player, higher penetration versus the level of functionality available. We accept up to and including version 10 compatible .swf files. You can, of course use Macromedia Flash MX (Version 6 of the Flash application) to develop your fla files, but you must then publish them so they can be viewed by users using the Flash 10 player. These publish settings are found under: (File/Publish SettingsÖ)
Dialogue Window Settings
Current Profile: Default
Version: Flash Player 10 (Maximum, depends on Flash software version)
Load Order: Bottom Up (Flash 3)
ActionScript Version: ActionScript 3.0 (or 2.0)
Options: Compress movie & Export/Include hidden layers checked. All other Options check boxes unchecked
Script time limit: 15 seconds
JPEG quality: 80%
Audio stream: MP3, 16kbps, Mono
Audio Event: MP3, 16kbps, Mono (Overide sound settings & Export device sounds unchecked)
Local playback security: Access local files only
We use the ClickTag method for passing URLs to flash media and tracking clicks
For a detailed run through of how to use this method for passing URLs to flash media and tracking clicks, please see Here If this aspect of the fla file has not been properly implemented (ie: in close accordance with the instructions linked above) problems will arise that may lead to the delay or under-performance of your campaign. There is no need to insert any URL or link in your fla file ñ that is all handled using the ClickTag layer. The code you will be using in your ClickTag layer button will look like this:
ActionScript 2.0
Note: This code is always attached directly to the invisible button:
on (release) {
if (clickTag.substr(0,4) == "http") {
getURL(clickTag, "_blank");
}
}
ActionScript 3.0
Note: The following is the Actionscript 3 click tag. This code must NOT be attached directly to the invisible button! The code should be placed on the timeline in the first frame. The invisible button in this case must have the instance name of “invisible_btn”:
invisible_btn.addEventListener(
MouseEvent.CLICK,
function():void {
if (root.loaderInfo.parameters.clickTag.substr(0,4)=="http") {
navigateToURL(
new URLRequest(root.loaderInfo.parameters.clickTag),
"_blank"
);
}
}
);
We draw your attention particularly to the "_blank" part of this code in both examples. We frequently encounter problems when this is omitted by designers.
wmode setting
Please make sure the wmode is set to ‘opaque’ and not ‘window’
Please note also: The quotation marks in either of the two action script examples above (Actionscript 2 & 3) are set as Straight rather than Curly or Smart quotes. It is essential, for the coding to work, that quotation marks are always Straight. Although we have made every effort to ensure that the code on this page is correct it is possible that, in some web browsers and possibly under other circumstances beyond our control, quotation marks will be re-rendered as Curly/Smart, which will stop your actionscript from working. This can be easily fixed by pasting the examples into a basic text editor (Text Edit on a Mac, or Notepad on a PC are good examples), ensuring the quotation marks are Straight then copying and pasting into Flash from there.
Here is a link to the Adobe Flash resource centre explaining this: Click Here
Notes:
Rich Media Tags.
We can, of course, accept rich media through third party tags. We accept standard banner and button rich media through third party tags but would advise the following:
Please inform us of the number of creatives pulled by a piece of code. This is important as we need to test all creatives but cannot test what we are unaware of.
Please do not change the creatives pulled by a piece of code without informing us and getting our approval. It is important that all creatives appearing on our site has been fully tested and approved.
This section of our policy does not cover expandable banners – these are addressed below.
Expandable banners.
We accept expandable banners, with the following provisos
As we fire all our banners, buttons and skyscrapers through iFrames we require iFrame busting code to allow the banner to expand out of its frame. This is a technically difficult thing to achieve and as a result we discourage clients from trying to accomplish this using technologies other than the following, which have been fully tested and offer a high standard of reliability:
Mediamind (Eyeblaster) (www.eyeblaster.com)
Flashtalking (www.flashtalking.com/)
Dart Motif (www.doubleclick.com/motif/)
Atlas (www.atlassolutions.com)
Adform (www.adform.com)
If you do not use one of the technologies recommended above it is your responsibility to provide us with all the code we need to allow your creatives to function reliably on our sites. This, in normal practice, would require that you supply us with fully function iFrame busting code for the technology you wish to use. This code would have to be fully tested by our team, which will increase the lead-time for such campaigns.
All expanding banners must adhere to the following standards:
Any sound must be user click activated.
Banner must contract on roll off
Page must be restored to normal after banner contraction
CPU usage guidelines
Macromedia’s Flash Player utilizes a computer’s CPU (central processing unit) in handling all animation, masking, and computation contained within a Flash file. If a Flash file contains heavy amounts of mathematical computation for elements such as animation, loops, or timers, it will require a much greater percentage of CPU usage. As a result, the Flash file is forced to compete with other Flash files and other applications for CPU usage, which causes all Flash elements on the page to slow down significantly.
There are two types of usage:
Running Usage: This is the amount of cpu power utilized after a flash file has completed its primary series of animations and is sitting “idle”.
Spike Usage: This is the amount of cpu power utilized when fluctuations, “spikes”, occur during the primary series of animations.
There are several ways to help cut down on the CPU which is controlled by mathematical-based action script. One way is to limit or eliminate looping functions in action script. Looping functions are usually associated with timers. Masking and animated masking techniques can also require a large amount of CPU resources.
One way to estimate how CPU intensive your Flash file may be is to open the “Task Manager” on a PC (control+alt+delete) and view the “Performance” tab or the “Activity Monitor” on a Mac and view the “CPU” tab. These system utilities give a graphical estimate of CPU usage. With the appropriate utility running, open your swf file in the Flash player – you may see a spike as your Flash file is animating.
A small spike may have a duration of 2 – 3 seconds. A small spike of 20%-30% is normal, although we would prefer is lower. If your CPU Usage jumps up to 50-100%, the Flash file may need revising until it uses less CPU resources.
