- Coding for email is not like coding for a website. Because each email client (Outlook, Gmail, AOL, etc.) separately controls how coded HTML will render in their email environment, coding standards are much more simplified and elementary. For example, external CSS is not allowed in email coding although it is widely used in website coding. For email, the general rule of thumb is “code like it’s 1995”. For more information on email coding best practices, please see the subsequent section on General Email Design Best Practices. If you are using a 3rd party email builder like Litmus, Unlayer, Stripo, or other email building software, simply export the HTML and image files to send to us.
- The maximum combined weight of your HTML file + image files cannot exceed 300kb as our email marketing platform will not deploy above that limit. Image files received above the maximum limit will be attempted to be re-sized by the Email Coordinator; however, this may delay deployment of your campaign. Also, please be advised that re-sizing will result in reduced quality of the image.
- Creative must be HTML-5 compliant & supported by the most recent browsers, and for up to 2 versions prior. This is to ensure our audience can engage with your campaign using any version of the most widely accepted browsers currently in use.
- All click-through URLs must be hardcoded into the HTML file received. Only fully qualified and properly formatted URLs may be used (example: https://www.ntmllc.com/).
- All tracking codes and/or tags must also be hardcoded as part of the click-through URL in the HTML file received. All testing of tracking mechanism must be done by client prior to sending materials to NTG. Do not send separate files with third-party trackers - NTG cannot implement and test third-party tracking. NTG will provide metrics reports as proof of deploy and performance, but will not guarantee tracking by any third-party vendor or offer any make-goods for non-functioning third-party tags.
- Map all images locally within the HTML file or use a third-party hosting environment as a placeholder for the image path. All images will be transferred to an NTG environment for hosting when building your campaign.
- When possible, ensure all links and assets are SSL compliant so browsers can render the creative properly in all environments and to avoid your landing page being blocked by users trying to click through your email. This refers to both your email materials as well as all materials used on your landing page(s). NTG will not deploy any email where clicking-through to your landing page or website is blocked by security protocols. For more information on SSL compliance, please visit: https://support.google.com/richmedia/answer/6015286?hl=en
HTML File
- Maximum File Size: 300KB (HTML + Images) - YOUR MAILING CANNOT BE SENT BY OUR SYSTEM IF IT EXCEEDS 300KB
- Maximum Pixel Width: 600 pixels
- Use inline styling (within each HTML element) or internal styling (embedded within tags). External Cascading Style Sheets (CSS) are not allowed in email.
- Use only basic, cross-platform fonts such as Arial, Verdana, Georgia, Times New Roman, or other web-safe fonts.
- All click-through URLs and tracking tags/pixels are required to be embedded into the HTML file.
- Ensure all image dimensions (height, width) noted in the HTML code match the dimensions for that specific image. Optimize & save all images for webview.
Image Files
- Image formats allowed: GIF, JPG, PNG (no PDFs or WEBPs)
- Maximum Width: 600 pixels
- All graphics used must be 72dpi
- Map all images locally within the HTML file or use a third-party hosting environment as a placeholder for the image path. All images will be transferred to an NTG environment for hosting when building your campaign.
What’s NOT ALLOWED
- NO Animation – all images must be static
- NO Embedded Video – instead use a static first frame or preview image of your video and link out to a hosted site. (i.e. hosted video on your website, YouTube, Vimeo, etc.)
- NO Background images, nested background colors or background colors outside of table structure
- NO Map tags
- NO Javascript, Flash, Script Tags, or other plugins
- NO PDF files
- NO Image Layers
- NO External CSS (Cascading Style Sheets)
- NO CSS Floats, CSS Positioning
Email Client Rendering Disclaimer
Due to the limited and varied support of features in the various popular email clients in use (i.e. Outlook, Gmail, AOL, & others), we cannot guarantee your email will render correctly in every email client and web browser. When possible, please provide fallback options with your creative code. As an alternative, a “view in browser” link is included in every email NTG deploys so it can be viewed as a webpage by any recipient who otherwise can’t view the email correctly in their chosen email client.
Also, because there is no universal industry standard for rendering HTML code in an email environment, what appears fine in one email client may not appear fine in another. This makes it impossible to create a dynamic HTML email that will display well in every email client application. NTG will strive to ensure your email renders the best it can in the most widely-used email clients and browsers.