Native Content Module

Media Specifications

• Client to supply 2-3 1536×1000 Pixel images to accompany article (editorial team will only choose one photo to accompany native content module)
• Client to supply two banner ads (one 300×250, one 728×90)
• Max File Load Size: 200 KB.
• File Formats: JPG, GIF, PNG (Minimum 120dpi)
• HTML5: No, not accepted.
• Click-through: Static, UTM tracking or third-party tags accepted.
• Animation: GIFs accepted, Limited to one loop not to exceed 15 seconds.
• Requirements: URL location for click-through. Multiple URL’s accepted.

Third-Party Tag Formats

• Image
• IFRAME
• JavaScript
• Click tags
• Impression tracker pixel

Third-Parties Vendors Accepted (including but not limited to): Bonzai, Celtra, Dianomi, Double Click / DFP, Sizmek, Google Ad Manager, Polar, and ResponsiveAds

Third-Party Guidelines

• All page requests will be via HTTPS. Any ad or creative making requests for tracking pixels, impression tracking, creative assets, or data must default to HTTPS (SSL compliant)
• No fourth-party tracking
• Third party tags must be live at the time of submission to enable thorough testing before launch

Mobile Specifications

• Same banner size runs on mobile
• No further assets required

Deadline: 10 days prior to launch

NOTE: Editorial team must be aware of chosen topic for native content module at least six weeks in advance of run date. Client has the right to approve facts of the article, but not the content. Facebook post will be boosted to targeted audience.