Ad Dimension |
300 x 250 |
Max File Size - Non-Rich & Rich Media |
Static: 40K HTML5: 200K |
Additional Rich Media File Size |
Rich Media: 300K In-Page Video: 1.2MB |
Accepted File Types |
JPG, GIF, PNG Third-Party tags from Edmunds' accepted vendors |
Animation |
Total length: 15 seconds; Maximum number of loops: 3 |
In Unit Video |
30 seconds max |
Video & Animation Frame Rate |
24 FPS max |
Audio |
Must be user initiated (on click: mute/un-mute) Default state is muted |
Expansion |
Not accepted |
Labeling |
Not required |
Linking Strategy |
Clicks may direct consumer to the client's website Click must spawn new tab or browser window Clear/prominent call to action recommended |
CPU Usage |
Max Percentage: 20% |
Serving and Tracking - Third Party |
Third-Party tags from Edmunds' accepted vendors. If Third-Party served native creative is requested, Edmunds will supply a design style template to follow per native specs. Creative assets must not write cookies to the user's computer (including Local Shared Objects, i.e., Flash Cookies). By delivering creative to Edmunds the client will be representing and warranting no cookies will be written by such creative assets. |
Serving and Tracking - Native Site-Served |
If Edmunds first-party serves, client 1x1 impression and click (redirect or appended) tags accepted. Assets required for native site-served build:
|
SSL Compliance |
All assets / creative elements comprising the ad being served--tags, images, tracking pixels, etc.--must be secure, i.e., be SSL (Secure Sockets Layer) compliant, make secure calls, and use secure URLs (https, protocol-relative URLs). If a non-secure creative is served on the site, it can prompt a warning in the user's browser, cause ad serving ad problems, or cause the entire page to be blocked. |
Submission Lead-Time |
Minimum 5 business days prior to campaign launch |
Native Medium Rectangle Example