Ad Unit Specifications

	Standard	Rich Media In-Banner	Rich Media Expanding	Rich Media Voken (OTP)
File Size (uncompressed)	Creative: Follow IAB’s guidelines. However, Eyereturn will accept up to 300kb ads for HTML. Static images and gifs must be 40kb or less or 80kb or less for 300x600. Backup image: 40kb (80kb for 300x600)	Creative: 300kb - 2.2mb* Backup image: 40kb (80kb for 300x600)	Unexpanded: 300kb Expanded: 2.2mb* Backup image: 40kb (80kb for 300x600)	300kb initial load 2.2mb* progressive load
Dimensions	300x250 160x600 300x600 728x90	970x250 300x600 300x1050 970x90	300x250 to 600x250 180x150 to 600x150 160x600 to 600x600 300x600 to 600x600 728x90 to 728x360 (other dimensions may be allowed, provided publisher/IAB specs are followed)	250,000 pixel stage (Example: 500x500, 1250x200 or 100x2500) larger sizes possible with site approval
Animation Time	30 seconds (unlimited upon user interaction)		Unexpanded: 30 seconds (unlimited upon user interaction) Expanded: Unlimited	10 seconds (Unlimited upon user interaction)
Audio/Video	Minimum 24 fps for video Video can start automatically on mute (must include pause/play button). Audio must be user initiated on click (must include mute/unmute button). Video controls and playback should be tracked using eyeBuild IATs.
Design Requirements	All units must have a 1 pixel solid black border, and an opaque background color. If the creative has a black background, some publishers require the 1 pixel border to be white. Remove any margin/padding from your document, so that the creative sits flush to the edge of the page, and be sure that the border does not exceed the unit's dimensions. Expanding banners should be aligned opposite to its direction of expansion. For example, if a single file expanding big box is designed to expand to the left, then the creative should be aligned on the right side of the page. Double check the above with media planner as individual sites can have different size and timing restrictions. Also reference the list of site specific requirements.			Double check the above with media planner as individual sites can have different size and timing restrictions. Also reference the list of site specific requirements.
Interactivity Requirements			Rollover expansions are required to collapse on rollout, click expansions may remain open until close button is clicked. Expanded portion requires close button reading "Close X" in the following location: Leaderboard: top-right Big Box: top-left Skyscraper: top-left	Requires close button reading "Close X" in top right corner, and will auto-close after 10 seconds.
The above is based on IAB Specifications * larger files can be accomodated if required, contact us for details

Delivery to eyereturn

Standard files required 6 business days prior to campaign launch

Rich Media files required 10 business days prior to campaign launch

File package must include:

Published creative, all required assets
Project files for editing
.GIF or .JPG (up to 40kb, for backup)

Include where applicable:

all required fonts and code
list of events requiring tracking (if using eyeBuild, provide the list of corresponding names and IDs for tracked events)

Clicktags & Close

Clicktags and Close functionality should be implemented using eyeBuild. Learn more about eyeBuild for HTML here. If you are building Flash, click here

External Resources

All assets must be hosted on eyereturn's servers.

eyereturn certification by the major publishers and networks is based on eyereturn hosting all resources loaded and used by an ad unit. Rare cases where assets or resources must be hosted on a non-eyereturn server must be discussed and approved by eyereturn and the publishers before serving. Any externally hosted resources must also be disclosed to the agency. eyereturn cannot be responsible for the speed, quality or content of externally hosted resources.

Event Tracking

Any function or user interaction within an ad unit may be tracked. Please use eyeBuild (click here for more information) to add appropriate tracking OR send us a document detailing the unit's tracking requirements.*

Identifying the correct functions to modify with tracking events can be difficult and time-consuming in complex and unfamiliar applications. Wherever possible, consolidate your tracking methods by creating an easily located section of blank functions called by your trackable events in which eyeReturn will place our tracking events, or commenting your code to indicate where tracking events should be placed.

*In some cases, additional charges may apply to non-standard tracking requests