Mobile Phone Creative Guidelines
2015 ADVERTISING CREATIVE GUIDELINES FOR DISPLAY & MOBILE – UPDATED FOR HTML5
Here are the revised specifications for Display Advertising and Mobile Advertising Creative Guidelines.


The display guidelines in this document have been updated to reference HTML5 Ad requirements. Extensive ad load performance testing was done over a period of 4 -5 months to collect performance data of different types of ad units on real publisher pages across browsers and controlled network speeds to reflect average internet and mobile usage to conclude optimum file weights.

Please email [email protected] if you have any questions.

Download PDF | Download Excel
For IAB Display Advertising Guidelines, click here
For IAB Mobile Rising Stars, click here

 

Loading data. Please stand by...

Creative Unit Name: Feature Phone Small Banner Feature Phone Medium Banner Feature Phone Large Banner Smartphone Static Interstitial Smartphone Static Banner Smartphone Static Wide Banner  

Initial Dimensions:
(WxH in pixels)

120x20
view sample

168x28
view sample

216x36
view sample

300x250
view sample
Increased dimensions allowed for display in high resolution devices. Please see Note 1 below.

300x50
view sample
Increased dimensions allowed for display in high resolution devices. Please see Note 1 below.

320x50
view sample
Increased dimensions allowed for display in high resolution devices. Please see Note 1 below.
Maximum Expanded Dimensions:
(WxH in pixels)
Not allowed for this unit  
Max Initial File Load Size: 3 KB 4 KB 5 KB 30 KB 15 KB 15 KB  
Max Additional Initial File Load Size
for OBA Self-Reg Compliance:
The current Self-Regulatory Principles for Online Behavioral Advertising include mobile, but implementation guidelines were not yet established as of the publication of these guidelines. As a result, a specific guidance is not included at this time.  
Subsequent Max Polite File Load Size: Not allowed for this unit  
Subsequent Max User Initiated File Load Size: Not allowed for this unit  
Subsequent Max User Initiated Additional
Streaming File Size:
Not allowed for this unit  
Max Video & Animation Frame Rate: Not allowed for this unit  
Maximum Animation Length:
(i.e. Flash™)
15-sec 15-sec 15-sec 15-sec 15-sec 15-sec  
Max Video Length: Not allowed for this unit  
Audio Initiation: Not allowed for this unit  
Z-Index Range: 0 - 4,999 0 - 4,999 0 - 4,999 6,000,000+ 0 - 4,999 0 - 4,999  
Max Percentage of CPU Usage:3 Changing connectivity speeds and device variability affect how ad display is processed.
Please see Best Practices below for more information.
 
Minimum Required Controls: Not applicable  
Labeling Requirements, Font Size, etc.: Ad unit content must be clearly distinguishable from normal webpage or application content
(i.e. ad unit must have clearly defined borders and not be confused with normal page content)
 
Submission Lead-Time: 3 business days
(If conflicts are found with the creative the submission lead time may restart upon re-submission.
Please check with the publisher for specific lead time requirements.)
 
Implementation Notes & Best Practices: Ensure images are mobile web optimized; do not use Flash™ assets; landing pages must be mobile optimized, include dimensions in file name  
Supported Creative Types: GIF, JPG, PNG GIF, JPG, PNG GIF, JPG, PNG GIF, JPG, PNG GIF, JPG, PNG GIF, JPG, PNG  

1. High resolution creatives may be accepted by some publishers for higher quality images on double-density/retina displays. The accepted file weight for these high resolution creatives will also increase, but should be no more then double the file size noted in these guidelines. Please check with you media provider for accepted file weights. To identify these creatives note 2x in the file name.

2. Full screen is dependent on the device model and may be restricted by status bars or navigations menus of the OS, browser and/or application.

3. The term "Best Practice" as used in these guidelines means the attribute is allowed and is important, but a current lack of testing tools, studies, etc. prevented certain guidelines form being set. See Release Notes & Best Practice tabs for more information.

Creative Unit Name: Smartphone Rich Interstitial Smartphone Rich Banner & Expandable Smartphone Rich Wide Banner & Expandable  
Initial Dimensions:
(WxH in pixels)

300x250
view sample
Increased dimensions allowed for display in high resolution devices. Please see Note 1 below.

300x50
view sample
Increased dimensions allowed for display in high resolution devices. Please see Note 1 below.

320x50
view sample
Increased dimensions allowed for display in high resolution devices. Please see Note 1 below.
 
Maximum Expanded Dimensions:
(WxH in pixels)
Expansion not allowed
for this unit
300x250, Full Screen
(Technical restrictions may apply for full screen expansion. Please see Note 2 below.)
320x416, Full Screen
(Technical restrictions may apply for full screen expansion. Please see Note 2 below.)
 
Max Initial File Load Size: 35KB 35KB 35KB  
Max Additional Initial File Load Size
for OBA Self-Reg Compliance:
1
The current Self-Regulatory Principles for Online Behavioral Advertising include mobile, but implementation guidelines were not yet established as of the publication of these guidelines. As a result, a specific guidance is not included at this time.  
Subsequent Max Polite File Load Size: Best practice  
Subsequent Max User Initiated File Load Size: Best practice  
Subsequent Max User Initiated Additional
Streaming File Size:
Best practice  
Max Video & Animation Frame Rate: 24 fps 24 fps 24 fps  
Maximum Animation Length:
(i.e. Flash™)
15-sec 15-sec 15-sec  
Max Video Length: 30 seconds 30 seconds 30 seconds  
Audio Initiation: User Initiated: Tap  
Z-Index Range: 6,000,000+ 5,000 - 1,999,999
(for entire ad unit)
5,000 - 1,999,999
(for entire ad unit)
 
Max Percentage of CPU Usage:3 Changing connectivity speeds and device variability affect how ad display is processed. Please see Best Practices tab for more information.  
Minimum Required Controls: Control = “Close X” on expanded panel and “Expand” on collapsed panel
Font = 8pt (11px) - 16pt (21px)
Retract Feature = Either tap to close/expand
Video may be played in native player which has standard controls
Custom video players must include: Play, Pause, Mute (volume control to zero (0) output may be included instead of or in addition to Mute control)
 
Labeling Requirements, Font Size, etc.: Ad unit content must be clearly distinguishable from normal webpage content (i.e. ad unit must have clearly defined borders and not be confused with normal page content)  
Submission Lead-Time: 5 business days
(If conflicts are found with the creative the submission lead time may restart upon re-submission. Please check with the publisher for specific lead time requirements.)
 
Implementation Notes & Best Practices: Ensure images are mobile web optimized; do not use Flash™ assets; landing pages must be mobile optimized; include dimensions in file name; use MRAID specifications when appropriate  
Supported Creative Types: HTML5; JavaScript;
Animated GIF
HTML5; JavaScript;
Animated GIF
HTML5 JavaScript;
Animated GIF
 

1. High resolution creatives may be accepted by some publishers for higher quality images on double-density/retina displays. The accepted file weight for these high resolution creatives will also increase, but should be no more then double the file size noted in these guidelines. Please check with you media provider for accepted file weights. To identify these creatives note 2x in the file name.

2. Full screen is dependent on the device model and may be restricted by status bars or navigations menus of the OS, browser and/or application.

3. The term "Best Practice" as used in these guidelines means the attribute is allowed and is important, but a current lack of testing tools, studies, etc. prevented certain guidelines form being set. See Release Notes & Best Practice tabs for more information.

Creative Unit Name: Full Page Flex Adhesion Banner Pull Slider Filmstrip Full Screen Filmstrip  

Initial Dimensions:
(WxH in pixels)

May launch from any IAB or MMA Standard Banner

Phone Example: 320x50 or in expanded state as an interstitial

Fits to any IAB or MMA Banner Standard or Guideline

Phone Example: 320x50 Refer to “III. Behavior and UI
Elements” in the Style Guide

May launch from any IAB or MMA Standard Banner

Phone Example: 320x50

May launch from any IAB or MMA Standard Banner

Phone Example: 320x50

May launch from any IAB or MMA Standard Banner

Phone Example: 320x50

300x600
  view sample view sample view sample view sample view sample    
 
Download
Style Guide

(.pdf, 311 KB)

Download
Style Guide

(.pdf, 377 KB)

Download
Style Guide

(.pdf, 406 KB)

Download
Style Guide

(.pdf, 696 KB)

Download
Style Guide

(.pdf, 274 KB)

Download
Style Guide

(.pdf, 303 KB)
 
Maximum Expanded Dimensions:
(WxH in pixels)
Varies by device, following the principle that the Full Page Ad Component will cover 100% of the available screen space. Refer to “Input Design” section for specific sizes. N/A Varies by device, following the principle that the Full Page Ad Component will cover 100% of the available screen space. Refer to the IAB Full Page Flex Specifications for additional and tablet guidance. Varies by device, following the principle that the Full Page Ad Component will cover 100% of the available screen space. Refer to the IAB Full Page Flex Specifications for additional and tablet guidance. Varies by device, following the principle that the Full Page Ad Component will cover 100% of the available screen space. Refer to IAB Mobile Full Page Flex Style Guide and Tech Specs for additional input.
 
300x600px  
Phone Example: 320x480   Phone Example: 320x480 Phone Example: 320x480 Phone Example: 320x480    
Max Initial File Load Size: Phone: 40 KB
Tablet: 60 KB
Phone: 40 KB
Tablet: 60 KB
Phone: 40 KB
Tablet: 60 KB
Phone: 40 KB
Tablet: 60 KB
Phone: 40 KB
Tablet: 60 KB
Tablet: 100 KB  
Subsequent Max User Initiated File Load Size: Phone: 100 KB
Tablet: 150 KB
N/A Phone: 100 KB
Tablet: 150 KB
Phone: 100 KB
Tablet: 150 KB
Phone: 100 KB
Tablet: 150 KB
N/A  
Subsequent Max Additional User-Initiated File Size: Phone and Tablet: 2.2 MB N/A Phone and Tablet: 2.2 MB Phone and Tablet: 2.2 MB Phone and Tablet: 2.2 MB Tablet: 2.2 MB  
Max Video & Animation Frame Rate: 24 FPS 24 FPS 24 FPS 24 FPS 24 FPS 24 FPS  
Maximum Animation Length: 15 seconds No looping 15 seconds 15 seconds No looping 15 seconds No looping 15 seconds No looping 15 seconds No looping  
Max Video Length: 30 seconds N/A 30 seconds 30 seconds 30 seconds 30 seconds  
Audio Initiation: User Initiated  
Z-Index Range: 5,000 - 1,999,999 (for entire ad unit) 5,000 - 1,999,999 (for entire ad unit) 5,000 - 1,999,999 (for entire ad unit) 5,000 - 1,999,999 (for entire ad unit) 5,000 - 1,999,999 (for entire ad unit) 5,000 - 1,999,999 (for entire ad unit)  
Minimum Required Controls: See “III.C Exit Point” Style Guide
for mandatory close specs
Font = 8pt (11px) - 16pt (21px)
Video must include: Play, Pause, Mute (volume control to zero (0) output may be included instead of or in addition to Mute control)
Close button in the upper right hand corner Base Ad Component “Expand” or other CTA

Full Page Ad Component: “Close X” on in the upper right hand corner
Font = 8pt (11px) - 16pt (21px)
Retract Feature = Tap to close/expand

Video must include: Play, Pause, Mute (volume control to zero (0) output may be included instead of or in addition to Mute control)
Close: Back Banner Bar in same exact position as Base Ad Component with “back” button.

Open: Base Ad Component with “swipe” or “slide” to expand Full Page Ad Component.

Font = 8pt (11px) - 16pt (21px)
Video must include: Play, Pause, Mute (volume control to zero (0) output may be included instead of or in addition to Mute control)
Base Ad Component:
Expand CTA button must be included

Full Page Ad Component:
Close button must be included in upper right corner Navigation icons to transition between content cells
Video must include: Play, Pause, Mute (volume control to zero (0) output may be included instead of or in addition to Mute control)
Video must include: Play, Pause, Mute (volume control to zero (0) output may be included instead of or in addition to Mute control)  
Labeling Requirements, Font Size, etc.: Ad unit content must be clearly distinguishable from normal webpage content (i.e. ad unit must have clearly defined borders and not be confused with normal page content)  
Submission Lead-Time: Min 10 business days before campaign start  
Implementation Notes & Best Practices: See “III. Behavior and UI Elements” in the Style Guide
Ensure images are mobile web optimized and no flash
See “III. Behavior and UI Elements” in the Style Guide
Ensure images are mobile web optimized
Base Ad Component:
Expand CTA must be clearly defined
Tapping anywhere on the banner expands the ad

Full Page Ad Component:
Close button
Recommended size: 40x40
Clearly located in upper right corner
Tapping the close button will collapse the unit and display the Base Ad Component

Wallpaper
Recommended size for phone: 320x480

Content Module
Recommended size for phone: 290x205 If feature contains multiple sections (i.e. photo gallery), page navigation dots will appear illustrating the number of pages available for that feature

Navigation Tray
Recommended size for phone:
Nav Tray: 320x100
Nav Icon: 80x75
Ensure images are mobile web optimized and no flash
Base Ad Component:
Expand CTA must be clearly defined by “slide” or “swipe” icon.

Tapping anywhere on the Base Ad Component expands the ad

Full Page Ad Component:
Back Banner Bar
Container is exact shape, size, position as Base Ad Component.
Recommended “back” cta size: 40x40
Clearly located in left corner of Back Banner Bar.
Tapping the back button will slide the unit horizontally closed and display the Base Ad Component

Ensure images are mobile web optimized and no flash
See “III. Behavior and UI Elements” in the Style Guide
Ensure images are mobile web optimized
See “III. Behavior and UI Elements” in the Style Guide
Ensure images are mobile web optimized
 
Supported Creative Types: HTML5 HTML5 HTML5 HTML5 HTML5 HTML5  

IAB Mobile Rising Stars File Size Approach:
The IAB Mobile Rising Stars, will load in three distinct phases. (the first of which applies to the IAB Mobile Adhesion Banner)

  1. Initial File Load whereby the Base Ad Component loads (for the Adhesion Banner, should the ad include a tap to expand component,) a “hidden frame” of the Full Page Ad Component also loads. This hidden frame enables rapid deployment of the Full Page Ad Component before additional files download.
  2. Subsequent User-Initiated File Load, where the “resting state” of the Full Page Ad Component loads. Importantly, this resting state is essentially one layer deep in that it presents the full experience to the viewer, but has not loaded additional files that may be called upon with further interaction. Note: for IAB Mobile Rising Stars that do not have a Base Ad Component like the in-content IAB Mobile Filmstrip or the in-line IAB Mobile Full Page Flex or Mobile Filmstrip, this is the first loading of any ad files.
  3. Subsequent Additional User-Initiated File Load. This includes all files that load as a result of the viewer further interacting with the Full Page Ad Component.
Additional File Size Notes:
For the Filmstrip’s full screen deployment, the Base Ad Component would be considered the “Initial File,” the first full page panel, the “Subsequent User-Initiated File,” and the additional Filmstrip panels “Subsequent Additional User-Initiated Files.”

The Filmstrip’s in content for tablets deployment does not have a Base Ad Component and the first loading of the ad unit is the initial full panel. As such, the size restrictions on this initial file load will mirror the “Subsequent User-

Ad Serving Standards: The IAB Mobile Adhesion Banner must be compatible with MRAID 1.0 and MRAID 2.0.

 


 

View a dynamic demonstration of IAB Z-Index guidelines

Z-Index Range Content Type Details
< 0 Background Elements None
0 - 4,999 Main Content, Standard Ads Standard ad tags in place with regular content. Includes OBA Self Regulation Message (CLEAR Ad Notice)
5,000 - 1,999,999 Expanding Advertising The entire expandable ad unit should be set within this range
2,000,000 - 2,999,999 Floating Advertising Over The Page ads (OTP's)
3,000,000 - 3,999,999 Pop-up Elements Chat windows, message notifications
4,000,000 - 4,999,999 Non-anchored Floating Elements Survey recruitment panels
5,000,000 - 5,999,999 Expanding Site Navigation Elements Drop down navigation, site warnings, etc. Only the expanding portion of navigation elements should be included on this level.
6,000,000+ Full-page Overlays Full-window Over-the-Page (OTP) ads and Between-the-Page ads IF they cover page content

Note: ad designers should consult each publisher individually for their specific Z-index guidelines

Z-index Definition
Enumerated layers of elements and content on a publisher’s webpage. Consideration of the z-element in page content design such as navigation, imagery, and ads is important for providing a seamless experience when page content overlaps (i.e. an expanding ad with a z-index that is lower [on the z-index scale] than navigational elements may give the appearance that page navigational elements are showing through the expanded portions of the ad).

Z-Index Range Use Recommendations
The Z-index represents layers of elements on a webpage. When ad elements and other page elements are layered incorrectly, proper display of either page content or ad content (or both) may be compromised. The accidental “collision” of competing elements on a webpage that share the same Z-index value leads to a poor consumer experience, in the form of distorted or mangled images and text. Accordingly, the establishment of an industry accepted z-index hierarchy and associated numerical range is crucial to solving the occurrence of collisions. Please note that adoption of these new Z-index guidelines by all publishers will take time. Creative designers are advised to consult directly with publishers for their individual Z-index guidelines.

Creative Display Guidelines Release Notes

The IAB Display Creative and Mobile Creative Guidelines have been updated to fully embrace HTML5 technology as the new standard for ad creative.

The audience capable of viewing Flash content continues to diminish. Mobile devices unable to play Flash content, combined with decreasing lack of Flash support among major desktop browsers, are rapidly accelerating this downward trend. HTML5 is the logical migration path for ad creative.

These creative updates are the result of testing diverse HTML5 ad creatives over a 4 month period for load performance and user experience to determine the optimum specifications for allowed file sizes and other HTML5 considerations. The test results were intensely debated by a cross-industry working group to establish the new specifications. The key goals for this update were to:

  • Develop new creative specifications that allow creative vendors to continue building immersive ad experiences using HTML5 technology.
  • Guide publishers on the updated file size limits necessary for executing HTML5 ads.
  • Provide guidance on factors to consider when building and serving ads in HTML5 that maximizes page and ad load performance and minimize time to visual display of the ad in users’ browsers.

Availability and Adoption
Please be advised that these IAB guidelines represent an industry recommendation. Accordingly, not all publishers, nor all IAB member companies, adopt these guidelines without modification relative to their own unique business offerings. Marketers, creative designers, and media agencies are strongly advised to consult directly with publishers regarding their ad creative requirements.

Consumer Experience and Performance
The new guidelines adhere to the principles of positive consumer experience while balancing the requirements of publishers and advertisers, namely page load performance and the trend toward rich multi-media creative, with the assumption that the consumer’s primary purpose for digital publications is consumption of content.

  1. All specifications were determined upon extensive load performance and time to visual display performance criteria with a goal of about one second to visual display.
  2. New specification criteria were determined based on the one second to visual display goal with subload and file request limits that support HTML5 ad combinations of multiple file types, video lengths, and animation frames.

Shared Libraries
Publishers and ad servers are encouraged to take advantage of browser caching functionality by allowing use of common and popular shared libraries in HTML5 Ads. Doing so improves ad load and page load performance since the previously used shared library will not need to be downloaded again.

For the current release, file weights for these libraries must be included in the initial file weight calculations for the gzipped HTML ad, but publishers have the option to exempt certain libraries from ad file size calculation. During the publisher certification process, publishers must approve both the shared library and its source before the library can be exempted from ad file size.

Although website developers have been using shared libraries for some time, we must observe and monitor the use of shared libraries for ad creative before we can exclude them from file weight calculations. The impact of shared libraries in file weight calculations will be reviewed in 3-6 months time and an appropriate update made in 2016.

File Requests
HTML5 Ads are like mini webpages that require a combination of multiple files and functions. The number of requests made to fetch files has a big impact on load performance of the ad as well as the page. HTML5 ads must optimize the number of requests being made to the server to reduce the impact on performance. For this release, a maximum of 15 file requests for initial file load is imposed to ensure little adverse effect on page load performance. This file request limit only applies for the file requests required to display the ad upon initial load. No file request limit has been placed on subsequent file loads.

Host-Initiated Subload
A host-initiated subload replaces the “polite load” in the previous release. Polite load was not clearly defined. The host-initiated subload is defined as “the additional file limit allowed for rich media and Rising Star units that is auto-initiated one second after the domContentLoadedEventEnd occurs (web page content has been loaded) on the host computer or device. Only rich media and rising stars ads allow for the additional host-initiated subload.

File Weight Calculation
File weights are the total, gzipped file size of all the ad assets being delivered to the browser at a given phase. The three ad-load phases in this release include: initial load, host-initiated subload, and user-initiated load.

  • Initial load – total, gzipped file size of all ad assets delivered to browser for initial ad display. It includes all files—images, HTML, CSS, JS, and any shared libraries or any other file type—required for initial ad display.
  • Subload – additional gzipped creative assets allowed for some ads that may loaded no sooner than one second (1s) after the browser domContentLoadedEventEnd event is fired. The ad will need to listen for the browser event and build triggers for subload accordingly.
  • User-initiated load – includes unlimited gzipped file load for any creative assets loaded after user-initiated ad interaction, like expansion or clicks. While no limits have been placed on user-initiated load, ad developers should consider user experience and load performance as part of their ad design. The assets for user-initiated ads should be optimized for load performance, and only necessary assets should be loaded.

Additionally, for ad units that allow video, another 1.1 MB of file size is allotted for auto-initiated 15-second videos, and 2.2 MB for auto-initiated 30-second videos in both display and mobile.

What is gzip?
All assets for HTML5 ads must be packaged together for delivery. To optimize the file size for delivery to browser, all assets should be delivered in compressed format. The common method for compressing files in transition over the Internet is the gzip utility, which is free to use and supported by all modern browsers. Ad servers compress ad files they serve as part of their general process.

Video Notes
HTML5 video cannot be streamed. Only progressive download is supported. However, standards exist to simulate streaming using an adaptive bitrate streaming format. This release provides guidance on how to format videos used in display and mobile advertising for optimal performance with HTML5 ads.

HTML5 Note
HTML5 ads are like mini web pages and contain multiple file types that combine different types of technologies such as HTML, Javascript, Cascade Style Sheets (CSS), Web Fonts, shared javascript libraries, SVG, WebGL and other assets like images and video files. A special note has been added to direct readers, especially ad creative designers, to refer to the IAB HTML5 Advertising Guide that has been developed concurrently with these guidelines.

 

When developing an ad unit for a mobile handheld device it is important to know where the ad unit will be delivered and optimized all assets and coding to produce the lightest ad unit possible to ensure a positive user experience. Here a few questions to guide you.

Q. Will the ad unit be displayed in an online or offline experience?
A. It is important to know if the ad unit will be delivered in an online or offline experience as differences will come into play when determining how to store and call assets. It is recommended to consult with publishers on best practices specific to their applications.

Q. What type of connection will a user be on when interacting with the ad unit?
A. Mobile phones have an array of data connection possibilities (Wi-Fi, 3G, 4G etc.) and plans that vary from carrier to carrier. Even if you know the type of connection a user has upon initial interaction, it could change as the user changes their physical location. This changing connectivity, combined with the smaller processing power of handheld devices, result in the crucial need to optimize the ad unit to its smallest file weight possible, ensuring faster load times. When applicable, targeting heavy rich media ad units to devices with strong fast connections such as Wi-Fi is recommended. This practice is especially encouraged with longer form video units.

Q. Does everything need to be loaded upfront?
A. The guidelines note initial and user subsequent file loads, but not all mobile publishers offer a second load experience. Some ad units are served with the entire ad loading upfront, while others may have the ability to call subsequent user initiated load. Polite file load (withholding a portion of the total ad creative file size from loading until publisher content has loaded) which has become prevalent for rich media ad served on computer browsers is not widely available in the mobile ecosystem. No matter how the ad unit is delivered the same processing and bandwidth restrictions exist, so optimizing is still very important.

It is recommended that rich media ad units with multiple panels/pages be loaded progressively when available. Only interactions that are available from the initial panel/page should be loaded at that time. As the user navigates through the ad experience, additional panels and animation may be loaded.

Q. Are the images and animation fully optimized?
A. All images and animation used should be optimized to produce the lightest total ad unit file weight possible. For example if the same image is used in multiple areas of an ad then it should be cached and re-used. When designing a high resolution ad unit be selective as to what assets need to be high resolution to ensure optimal image quality. It is also important to limit the amount of external calls that are made.

Q. Is the user directed to a mobile optimized experience?
A. All call to actions should be mobile optimized. For example, when direction to a landing page it should be optimized for the mobile device with simplified navigation, readable content without the need to zoom and touch friendly. Please see IAB’s Tap Into Mobile for more guidance on mobile optimized landing pages: http://www.iab.net/tapintomobile

Q. Are all creative files named suitably?
A. To help with the trafficking process creative files should be named with descriptive characteristics including creative dimensions and 2x for double density/retina creatives.

 

Universal Ad Package (UAP)

Medium Rectangle
300x250

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Universal Ad Package (UAP)

Rectangle
180x150

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Universal Ad Package (UAP)

Wide Skyscraper
160x600

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Universal Ad Package (UAP)

Leaderboard
728x90

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Other Ad Units

Super Leaderboard
970x90 (optionally 970x66 is offered by some publishers)

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Other Ad Units

Half Page
300x600

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Other Ad Units

Button 2
120x60

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Other Ad Units

Micro Bar
88x31

Submission Lead Time
Min 3 business days before campaign start

Best Practice
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.

Rich Media Guidance

In-Banner Video (file-loaded, streaming) or Expandable / Retractable
300x250

Submission Lead Time
Min 6 business days before campaign start

Implementation Notes & Best Practices:

In-Banner Video (file-loaded, streaming):
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.
Expandable / Retractable:
Expansion must be user initiated (note 2)

Best Practice
For times when the user’s browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file the same dimensions of the original (collapsed) ad dimensions.

Rich Media Guidance

In-Banner Video (file-loaded, streaming) or Expandable / Retractable
180x150

Submission Lead Time
Min 6 business days before campaign start

Implementation Notes & Best Practices:

In-Banner Video (file-loaded, streaming):
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.
Expandable / Retractable:
Expansion must be user initiated (note 2)

Best Practice: For times when the user’s browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file the same dimensions of the original (collapsed) ad dimensions.

Rich Media Guidance

In-Banner Video (file-loaded, streaming) or Expandable / Retractable
160x600

Submission Lead Time
Min 6 business days before campaign start

Implementation Notes & Best Practices:

In-Banner Video (file-loaded, streaming):
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.
Expandable / Retractable:
Expansion must be user initiated (note 2)

Best Practice: For times when the user’s browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file the same dimensions of the original (collapsed) ad dimensions.

Rich Media Guidance

In-Banner Video (file-loaded, streaming) or Expandable / Retractable
728x90

Submission Lead Time
Min 6 business days before campaign start

Implementation Notes & Best Practices:

In-Banner Video (file-loaded, streaming):
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.
Expandable / Retractable:
Expansion must be user initiated (note 2)

Best Practice: For times when the user’s browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file the same dimensions of the original (collapsed) ad dimensions.

Rich Media Guidance

In-Banner Video (file-loaded, streaming) or Expandable / Retractable
300x600

Submission Lead Time
Min 6 business days before campaign start

Implementation Notes & Best Practices:

In-Banner Video (file-loaded, streaming):
For times when the user's browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file.
Expandable / Retractable:
Expansion must be user initiated (note 2)

Best Practice: For times when the user’s browser does not support creative functionality (i.e. Flash™, HTML5), provide a standard image file the same dimensions of the original (collapsed) ad dimensions.