{"id":423,"date":"2012-07-11T12:01:21","date_gmt":"2012-07-11T12:01:21","guid":{"rendered":"http:\/\/www.ethinos.com\/blog\/?p=423"},"modified":"2012-07-11T12:16:02","modified_gmt":"2012-07-11T12:16:02","slug":"email-newsletters-decoded","status":"publish","type":"post","link":"https:\/\/www.ethinos.com\/blog\/email-newsletters-decoded\/","title":{"rendered":"EMAIL NEWSLETTERS \u2013 DECODED"},"content":{"rendered":"<p>If you\u2019re one of those who\u2019ve had the harrowing experience of coding an HTML E-newsletter, and spent hours trying to figure out what you\u2019ve done wrong that\u2019s causing the design to render differently on different email clients, this blog post is an effort to simplify things a bit.<\/p>\n<p>Before we go any further, it is most important to understand that coding for <a href=\"http:\/\/www.ethinos.com\/digitalmarketing\/\">HTML newsletters<\/a> is vastly different from coding an HTML web page.\u00a0 Browser compatibility, coupled with email clients\u2019 compatibility, creates a unique challenge to programmers coding for HTML newsletters.\u00a0 The reason for this is that various email clients have different levels of CSS Support.<\/p>\n<p>Pixel perfect or not, email newsletters are an important ingredient in the <strong><em>digital marketing strategy<\/em><\/strong> that speaks directly to the target audience. They are here to stay and so, while email clients may take years adapting themselves to the changing html and CSS standards, it is us, programmers who will have to pull up our socks and find innovative solutions to design outstanding email newsletters that send the message across effectively and beautifully.<\/p>\n<p>Email services like Gmail, Lotus Notes &amp; Outlook 2007 are most restrictive and therefore it is imperative that we code for these clients first. If the newsletter renders consistently on each of these platforms, there\u2019s a high likelihood that it\u2019ll work on most other email clients too.<\/p>\n<p>Here are some of my top tips that I\u2019ve picked up \u2026 some through my experience, some from websites like Campaign Monitor and still others from forums and other blog posts:<\/p>\n<p><strong>HTML Coding<\/strong><\/p>\n<ul>\n<li>Use      table layouts instead of the div layout, since divs and floats are not      supported by all the email services.<\/li>\n<li>Always      nest the entire e-newsletter layout in a table cell.<\/li>\n<li>Each      table cell should specify width and height parameters to ensure they      render exactly the same on all the email agents.<\/li>\n<li>Specify      cell spacing, cell padding, padding and margins to all cells for      consistent looking designs on all email services.<\/li>\n<li>Avoid      colspans, since some older email services do not support these.<\/li>\n<\/ul>\n<p><strong>STYLES<\/strong><\/p>\n<ul>\n<li>Don&#8217;t      use styles in the head section, use <strong>inline      styles<\/strong> instead for every element.<\/li>\n<li>CSS      Shorthands do not work in an html email newsletter.<\/li>\n<li>Do      not use external style sheets with the link element. These do not work.<\/li>\n<li>Deprecated      HTML tags like &lt;font&gt; need not be used.\u00a0 The font styles work fine, so long as      they are applied inline to the elements.<\/li>\n<\/ul>\n<p><strong>IMAGES<\/strong><\/p>\n<ul>\n<li>Always      use <strong>display=&#8221;block&#8221;<\/strong> for all images, to avoid extra white spaces after the images which is a      common problem in Outlook.<\/li>\n<li>Always      specify <strong>height and width parameters<\/strong> for all images to avoid stretching of images.<\/li>\n<li>Always      give <strong>absolute paths<\/strong> (online      paths of images stored on a server) for images, email services like yahoo      do not display images on relative paths.<\/li>\n<li>Always      provide alt tags for images, to ensure that the newsletter is still      readable if images are blocked.<\/li>\n<\/ul>\n<p><strong>Email Services &amp; their quirks<\/strong><\/p>\n<ul>\n<li>Hotmail      auto-left aligns the table.\u00a0 To fix      this, add the following code to the head:<br \/>\n<em> .ReadMsgBody{ width: 100%;}<br \/>\n.ExternalClass\u00a0 {width: 100%;}<\/em><\/li>\n<li>To      add background images to a td, apply the image as a background on a new      HTML table that encases all of the table rows and columns that would      display parts of your background image. Here is how a background is      implemented to a table cell, courtesy Campaign Monitor.<\/li>\n<\/ul>\n<p><em>&lt;!DOCTYPE\u00a0html PUBLIC &#8220;-\/\/W3C\/\/DTD\u00a0XHTML\u00a01.0\u00a0Transitional\/\/EN&#8221;\u00a0&#8220;http:\/\/www.w3.org\/TR\/xhtml1\/DTD\/xhtml1-transitional.dtd&#8221;&gt;<br \/>\n&lt;html\u00a0xmlns:v=&#8221;urn:schemas-microsoft-com:vml&#8221;&gt;<br \/>\n&lt;head&gt;<\/em><\/p>\n<p><em>&lt;body\u00a0style=&#8221;margin:0;\u00a0padding:0;\u00a0width:100%\u00a0!important;&#8221;&gt;<\/em><\/p>\n<p><em> <\/em><\/p>\n<p><em>&lt;table\u00a0width=&#8221;600&#8243;\u00a0cellpadding=&#8221;0&#8243;\u00a0cellspacing=&#8221;0&#8243;\u00a0border=&#8221;0&#8243;&gt;<br \/>\n&lt;tr&gt;<br \/>\n&lt;!&#8211;\u00a0Backup\u00a0background\u00a0color\u00a0is\u00a0#DDDDDD\u00a0&#8211;&gt;<br \/>\n&lt;td\u00a0bgcolor=&#8221;#DDDDDD&#8221;\u00a0style=&#8221;background-image:\u00a0url(\u2018image path\u2019);&#8221;\u00a0background=&#8221;image path&#8221;\u00a0width=&#8221;600&#8243;\u00a0height=&#8221;120&#8243;\u00a0valign=&#8221;top&#8221;&gt;<br \/>\n&lt;!&#8211;[if\u00a0gte\u00a0mso\u00a09]&gt;<br \/>\n&lt;v:rect\u00a0style=&#8221;width:600px;height:120px;&#8221;\u00a0strokecolor=&#8221;none&#8221;&gt;<br \/>\n&lt;v:fill\u00a0type=&#8221;tile&#8221;\u00a0color=&#8221;#DDDDDD&#8221;\u00a0src=&#8221;image path&#8221;\u00a0\/&gt;&lt;\/v:fill&gt;<br \/>\n&lt;\/v:rect&gt;<br \/>\n&lt;v:shape\u00a0id=&#8221;theText&#8221;\u00a0style=&#8221;position:absolute;width:600px;height:120px;&#8221;&gt;<br \/>\n&lt;![endif]&#8211;&gt;<br \/>\n&lt;p&gt;If\u00a0you\u00a0can\u00a0see\u00a0this\u00a0over\u00a0the\u00a0image,\u00a0background\u00a0images\u00a0are\u00a0successful.&lt;\/p&gt;<br \/>\n&lt;!&#8211;[if\u00a0gte\u00a0mso\u00a09]&gt;<br \/>\n&lt;\/v:shape&gt;<br \/>\n&lt;![endif]&#8211;&gt;&lt;\/td&gt;<br \/>\n&lt;\/tr&gt;<br \/>\n&lt;\/table&gt;<\/em><\/p>\n<ul>\n<li>Yahoo! Mail also has a knack for picking keywords in emails and <a href=\"http:\/\/www.ethinos.com\/digitalmarketing\/social-media.html\">linking them to advertising popups<\/a> (look for the blue, dotted links). Unfortunately, there\u2019s\u00a0no known way to disable this behavior, despite it being potentially distracting or confusing to your subscribers.<\/li>\n<\/ul>\n<p>The only way to get around this is to style the links to colors that blend with your design. The class applied to these links is: \u2018yshortcuts\u2019. So, style these in the &lt;head&gt; section of your document like below:<\/p>\n<p><em>&lt;style&gt;<br \/>\n.yshortcuts { color: #CCCCCC } \/* Body text color *\/<br \/>\n.yshortcuts a span { color: #00FF00 } \/* Link text color *\/<br \/>\n&lt;\/style&gt;<\/em><\/p>\n<p><strong>GENERAL GUIDELINES:<\/strong><\/p>\n<ul>\n<li>Do      not use scripts as these are always disregarded by the Email clients.<\/li>\n<li>Avoid      too many images.<\/li>\n<li>Ensure      that the newsletter looks fine and makes sense even if the images are not      displayed.<\/li>\n<li>Always      provide an online HTML copy of the newsletter.<\/li>\n<li>Always      provide unsubscribe links for the user.<\/li>\n<li>Call      to action buttons should ideally be text and not images, to ensure it is      visible even if images are not displayed.<\/li>\n<li>The      general rule of thumb is to design mainly for Google &amp; Outlook since      these are most restrictive. If your newsletter renders fine on these      agents, chances are high that they will look good on most others too.<\/li>\n<\/ul>\n<p>While pixel perfect HTML newsletters that render exactly the same on every email client are a myth; given the restrictive email client support of the new <strong>HTML &amp; CSS Standards<\/strong>, most of the above steps result in some form of consistency in terms of display on different platforms and client services.\u00a0 It is always worthwhile however, to test the newsletter on different browsers to check for <a href=\"http:\/\/www.ethinos.com\/digitalmarketing\/branding-design.html\">browser compatibility<\/a> and then test them on various platforms and various email services.<\/p>\n<p>Similarly, it is worthwhile to note that while fancy HTML newsletters look great, it isn\u2019t worth the effort and resources spent, if it looks like that only to 10% of your customer base. A simple readable HTML that renders well and sends your message across to your target audience with a clear message and call to action is what makes the impact!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you\u2019re one of those who\u2019ve had the harrowing experience of coding an HTML E-newsletter, and spent hours trying to figure out what you\u2019ve done wrong that\u2019s causing the design to render differently on different<a class=\"moretag\" href=\"https:\/\/www.ethinos.com\/blog\/email-newsletters-decoded\/\"> &#8230;<\/a><\/p>\n","protected":false},"author":22,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[72,97,98],"class_list":["post-423","post","type-post","status-publish","format-standard","hentry","category-digital-marketing","tag-digital-marketing-strategy","tag-html-e-newsletter","tag-html-newsletters"],"_links":{"self":[{"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/posts\/423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/comments?post=423"}],"version-history":[{"count":6,"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/posts\/423\/revisions"}],"predecessor-version":[{"id":426,"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/posts\/423\/revisions\/426"}],"wp:attachment":[{"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/media?parent=423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/categories?post=423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ethinos.com\/blog\/wp-json\/wp\/v2\/tags?post=423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}