Banner

Size

Format

File Size

Special Instructions

SUPER LEADERBOARD

970x90
And (320x100 
or 320x50 static
for mobile)

html5, png, jpg

(if using html file, please provide fallback image for mobile)

Max 75k

All HTML5 banners must include a ClickTAG to enable links and tracking. All files associated with the banner (images, css, js etc) must be hosted on your servers or embedded absolute in the code. If using HTML5 creative please provide the html5 zip bundle and the URL for the ClickTAG when submitting. See below section for more info.

BILLBOARD

970x250 pixels
And (320x100
or 320x50 static
for mobile)

html5, png, jpg, gif, third-party tags also accepted

All HTML5 banners must include a ClickTAG to enable links and tracking. All files associated with the banner (images, css, js etc) must be hosted on your servers or embedded absolute in the code. If using HTML5 creative please provide the html5 zip bundle and the URL for the ClickTAG when submitting. See below section for more info.

Animation Allowed: Yes – Maximum 3 rotations – no forever looping.

BILLBOARD: Note that this unit can include video.  Because we use Google DFP for ad serving, we ask that any video embedded within this ad unit be sourced from YouTube.  If using video, please provide YouTube URL to NMG ad ops team for implementation.  

STICKY FOOTER: Sticky Footers run on all pages except Resources, Topic Centers and Videos. Client must provide a Leaderboard ad for display on desktop and a 320x100 for mobile display.

PRESTITIAL: Prestitials run on all pages except Resources, Topic Centers and Videos. Prestitials will only be served once per visitor every 24 hours. Client may provide a 640x480 ad or a 900x550 for display on desktop computers only.

LEADERBOARD

728x90 pixels
And (320x100 
or 320x50 static
for mobile)

STICKY
FOOTER
 

728x90 pixels or 970x90
And (320x100
or 320x50 static
for mobile)

MEDIUM RECTANGLE
 

300x250 pixels

HALF PAGE
 

300x600 pixels 

PRESTITIAL
 

640x480 or 900x550 pixels 

(Does not serve on mobile.)

SPEED BUMP

(within feature
story content)

120x120 pixels
image + text

png, jpg, gif

Headline: 50 characters, including spaces, bolded and URL

Body Copy: 240 characters including spaces. Can include one url inline.

No animation allowed for image. 

When building your HTML5 zip bundle, please follow these requirements.

• If you use Google Web Designer to build HTML5 creatives, be sure to select “DoubleClick” as the environment.
• The following guidelines should work for any browser that supports HTML5. However, some creative functionality may not work as desired in all environments.
• Confirm that your bundle is SSL compatible, HTML5 creatives must be SSL compatible to serve to HTTPS sites.

Follow dimension guidelines

• Unlike images or videos, HTML documents don't have dimensions on their own. Therefore, use the size meta tag to indicate the intended size for your creative and ensure your creative renders at the right dimensions: <meta name="ad.size" content="width=[x],height=[y]">.
• HTML5 creatives can only have fixed dimensions (e.g., 300x250, 970x250, 728x90, etc.). Dynamic sizes such as “Fluid” aren’t supported.
• Here's an example meta tag for a fixed size (such as 300x250):
  <meta name="ad.size" content="width=300,height=250">

Follow click tag guidelines – must have ClickTAG

• Click tags define click-through URLs for each exit on your HTML5 creative. An exit is any clickable area that directs the browser to a landing page.
• When an exit gets a click, the creative calls DFP for the click-through URL associated with that exit.
• You can set this URL in your creative or ad, depending on your needs and the creative type.
• If you set click tags in both the creative and ad, the ad-level setting overrides the creative-level settings.
• DFP detects click tags when you upload assets. You can change the click-through URL the click tag uses anytime, even after you export tags.

Here are some click tag best practices:

• Make sure your creative uses the click tag variable as the click destination.
• The click tag should be easy for the ad server to read — no minification or obfuscation, though you can use minifers in the rest of your code and in other files.
• We don't recommend hard-coded click-through URLs in your asset because that prevents DFP from tracking clicks and prevents traffickers from updating the URL.