Expandable banners provide a user-initiated panel to extend the ad beyond standard unit ad dimensions. The expanded panel allows extra space for users to interact with the partner’s message without leaving the page.
The 970×90 footer expands to a 970×415* panel. It expands upwards from the creative.The expand (and close) is user initiated on-click. The expanded ad unit must include a close button.
*The footer expandable may also accomodate a 728×90 that expands upward to 728×315.
- Initial Dimensions: 970×90 expands to 970×415
- Maxium Expanded Dimensions: Expansion must be user-initiated
- Max Initial File Load Size*: 80 KB
- Host-Initiated Subload**: 300 KB
- Frames per Second: Minimum 24 fps for video
- Animation/ Video Guidelines (See video notes below): 15 sec max length (unlimited user-initiated); 1.1 MB additional file size allowed for host-initiated video; Unlimited file size for user-initiated video
- Z-Index Range: 5,000 – 1,999,999 (for entire ad unit)
- Unit-Specific Notes (See General Ad Requirements below): Retract feature = either click to close/ expand or enable mouse-off retraction
- *Initial file load: Includes all assets and files necessary for completing first visual display of the Ad.
- **Host-initiated subload: where allowed, additional files may load one second after the browser domContentLoadedEventEnd event. The ad should be able to “listen” for the browser domContentLoadedEventEnd event before subsequent files beyond the initial max file size may be loaded.
- Required for ads with video: Video may omit controls until user initiates interaction. Upon user interaction, video controls must include Play, Pause, Mute or volume control to zero (0) output for videos that expand out of initial ad upon interaction. For auto play videos that play in banner only Mute or volume control to zero(0) is required.
- HTML5 video controls: To improve performance and reduce file size, use control attributes in the HTML5 video tag for controls instead of providing custom assets for displaying controls
- Adaptive bitrate streaming: HTML5 does not support streaming video, but it can simulate a streaming experience using adaptive bitrate streaming technologies such as HLS and MPEG-DASH. Formatting files for adaptive bitrate streaming enables a smoother viewer experience. Adaptive bitrate streaming uses short fragments (2-3 seconds) of the video at different quality levels and stores them in a playlist file such as M3U8. During playback, the player detects bandwidth at the start of each fragment and plays the fragment at the quality level best suited to the bandwidth and player environment. Common protocols for adaptive bitrate streaming include HTTP Live Streaming (HLS) in the US and MPEG-DASH in the EU.
- Video codec: Use MPEG-4 (MP4) file formats for H.264-encoded video for a more seamless delivery across devices. The H.264 codec should use a Baseline profile to allow for more diverse execution in systems that range from a cellular connection on a mobile screen to a high-speed cable connection on an HTTP-connect TV screen. For audio, AAC is more widely supported (PCM audio is unsupported in Flash players).
- Video format: At a minimum, the MP4/H.264 file format should be provided, but alternate files using formats such as WebM and VP8 may also be submitted.
- The MOOV atom: Use the web-optimized setting when encoding the MP4 file, which sets the MOOV (movie) atom at the start of the file.
General Ad Requirements (Apply to all ads):
- Interest-Based Advertising (IBA): Include IBA self-regulation controls for ads using behavioral targeting (5 KB max file size)
- Audio: Must be user-initiated. To allow for audio initiation in videos without player controls, a control may be included for user to initiate audio.
- Hotspot: Not to exceed 1/4 size of ad. Initiated when cursor rests on hotspot for at least 1 sec. Must NOT initiate audio.
- Defining ad space: Ad unit content must be clearly distinguishable from normal webpage content (ad unit must have clearly defined borders and not be confused with normal page content).
- Max CPU: ad not to exceed 30% CPU usage during host-initiated execution.
- Submission lead time: Minimum lead time for ad file submission is 6 days before campaign start.
- Max number of host-initiated file requests: ad not to exceed 15 file requests during initial file load and host-initiated subload. Unlimited file requests allowed after user-interaction.