- Creative must be submitted as finished HTML or as one image.
- Maximum width: 600 pixels, maximum height: 1000 pixels
- Finished HTML File must be supplied in a ZIP archive file, along with all images referenced in the HTML inside a separate folder. Images are not permitted to be hosted on servers external to Seventh Street Media’s email platform.
- All required click-through tracking must be embedded prior to creative submission
- All HTML code should be run through the W3C Validator prior to creative submission – http://validator.w3.org/
- Incorrectly submitted creative will be returned for revision
- Subject line character length: 50 characters (incl. spaces and punctuation)
Additional Guidelines: HTML
Important note: HTML email documents have a tendency to render with slight inconsistency among a variety of email clients. The information presented in this document is essential in ensuring a quality, consistent outcome across the most common email platforms. Please note that failure to adhere to these recommendations, PARTICULARLY HTML CODE, may impact campaign effectiveness, delivery scheduling / timelines and end-user experience.
- Do not use
<div> tags in email production as the box model is not supported by a majority of e-mail clients; instead use Tables for e-mail layout.
- Do not use CSS classes as they are not supported across all email clients and will cause inconsistent rendering.
- Do not use use rowspan as it won’t render consistently.
- Set cellpadding and cellspacing to 0 on the table elements.
- Use line-breaks (
<br />) instead of paragraphs (
<p>) to ensure a more consistent rendering.
- Do not use CSS definitions in the head of the e-mail, use in-line CSS
<TD> instead as this will ensure the highest specificity and correct rendering.
- Do not use using decimal values for font size in the creative (use 15px instead of 15.5px).
- Do not use padding or margin attributes as some email clients, such as Outlook 2007 do not support them. Use blank
<td> tags with spacer images, or use alignment techniques with nested tables where necessary.
- 1px by 1px transparent GIFs may be stretched in order to define custom spacing within table cells. It is also advisable to define width (or height) for
<td> cells as well since some email clients render default spacing for tables differently.
- Do not use empty lines of code and spaces in between an
<img> tag and
</td> tag. Some browsers may read this as an actual space in overall layout and this can lead to misaligned graphics.
- More email clients are blocking images by default. To combat this trend, include compelling alt tags to grab the user’s interest and encourage them to click ‚”display images”.
- Do not use negative tracking in the copy as this is not supported by email clients and will produce rendering inconsistencies during the production.
- File size considerations – To reduce the likelihood of being caught in spam filter, the total email weight must be a maximum of 100 kb.
- Do not use HTML anchor targets
Additional Guidelines: Design Considerations
- Images should not make up more than 50% of the email. Do not use Background images.
- Do not use vertically aligned content regions where height is determined by text, since some email clients, such as Outlook 2007, display blocks of text with slightly different leading and kerning.
- Do not use Forms within email.
- You must explicitly define colour values in order to override defaults. Example, URLs and email addresses (even when not hyperlinked) will appear as links in Gmail.
- All image tags should include width and height attributes.
- Do not use Flash or animated GIFs as they are not supported across all email environments.
- Include at least one non-graphical call to action above the fold.