Straight to your inbox
Get the best email and digital marketing content delivered.
Join 250,000 in-the-know marketers and get the latest marketing tips, tactics, and news right in your inbox.Subscribe
We’ve just put the finishing touches on a new demo movie for Campaign Monitor. We wanted to put something together that covered all the benefits of using Campaign Monitor in a few short minutes. Check it out now, you’ll need Flash installed to watch it. It’s always a tough call to work out what features to highlight and just as importantly leave out for a demo like this. We’re really happy with how it all came together in the end. What do you guys think, does it sum up the Campaign Monitor experience?
Ensuring your emails look awesome across every major email client out there can be a lot of work. To make your job that little bit easier, we’ve just put together 30 free email templates that look fantastic and have been tested in all the major email environments. Not even Outlook 2007 could stop these suckers looking great. The templates range from simple, single column emails through to more complex 2 column newsletters with different types of content. We’ve also been careful to keep the use of images to a minimum, so the templates look great even when images have been disabled. Changing the color scheme to suit your own brand is as simple as making a few simple tweaks to the code. What are you waiting for? Preview and download the templates now.
As image blocking in email continues to become the norm, one absolute must is to make sure you include the width and height attributes in your image tags. When most email clients (especially desktop based ones like Outlook) disable images, they show an empty image placeholder in its place. Because these email clients don’t actually download the images from the server, the only way they can figure out the dimensions of that placeholder is to look at the included width and height attributes. If none or only one is provided, they just take a guess, which in almost every case results in completely destroying what’s left of your design. Here’s a perfect example of this in action. Just this morning I received an email newsletter that only specified the height for most images in the email, and not the width. When Outlook displayed the email, it got the height right, but was way off on the width side. Here’s how the email looked when I first opened it: To see a comparison of how it’s supposed to look, here’s a screenshot of the email with images enabled: By not including the width attribute in any image tags, Outlook had no idea what width to use and its best guess was unfortunately way off. This made an otherwise readable email a complete nightmare that was almost impossible to get anything out of. To provide a comparison, I checked out the source and added the correct width attribute to each image to see what the new results would be. Here’s a screenshot of the new version that took about 5 minutes to update: The updated version that includes all width and height attributes is a big improvement over the initial version. It clearly resembles the intended design and I can easily scan the table of contents and start scrolling to read the rest of the content. The email is completely usable even with no images being visible. While there are certainly better examples of emails designed to look and work well with images disabled, the point is still very convincing. By ensuring width and height attributes are present for all image tags, we give our subscribers a much better chance of getting a usable email, even with images disabled.
After we posted an update to the CSS Support article last week, a few of you mentioned that the new PDF layout made it hard to make out the results when printed in black and white. Not only this, but it was also a challenge for anyone who was color-blind. About the same time, Martin Focazio from New York based Magnani Caruso Dutton approached us about taking the PDF version a step further (actually, about 5 steps further). Martin reworked the results to make it much clearer which CSS selectors and properties offered the best support across the board. These were then sorted into Safe, Risky and Poorly Supported to make it much easier to decide which properties to aim for. Download the spiffy new results in PDF (91kb) or Excel (80kb) To top it off, the new file also includes the percentage of support each email environment offers. We’ve also updated the original post to include the new version of the findings. A huge thanks to Martin for all his hard work, and to everyone else for giving us feedback on the original version. As usual, we’ll keep our eyes peeled for any changes in each environment moving forward. If you spot anything, let us know. Update: I’ve added the Excel version of the results so you guys can tweak it to your hearts content.
You have me sold! I have been searching for years on how I can offer stylish email newsletters to my clients, but no one wanted to part with that valuable information without a pricetag. If I knew it was going to be as simple as designing a webpage and uploading it to Campaign Monitor, I would have contacted you eons ago! Thanks for making something so wonderful available to everyone! Doris Cush, Owner, Fraidy Kat Design
We’re big Zeldman fans here at Campaign Monitor. His web standards work has been an important influence in our thinking as web designers and web application builders. So we were disappointed to read his recent post, E-mail is not a platform for design. The core of Jeffrey’s argument is this: But when I say HTML mail still sucks, I donâ€™t mean it sucks because support for design in e-mail today is like support for standards in web browsers in 1998. I mean it sucks because nobody needs it. It impedes rather than aids communication. Essentially Jeffrey seems to be making the mistake of equating the work of bad designers with the communication medium of email. Obviously we are going to be biased, but we’ve heard from enough of you guys, and your clients, to know that HTML email can be a great thing when done correctly. To say as a blanket statement that HTML email impedes communication is an extraordinary generalisation. There are many times when a well designed, and well laid out HTML email can be a lot clearer, easier to scan and overall better experience than the equivalent in plain text. As an example, check out the HTML email sent weekly by Threadless on the right. It’s a smart, simple layout that works in every email client out there. Instead of forcing their subscribers to click on a link to check out each new shirt via plain text, they can preview each design right in their email client. Not only is this a better user experience, but it’s also the reason more than half of their recipients click through to their web site each week. You see a design you like, you click it to find out more and make a purchase. Obviously, there is a lot of really over the top, poorly designed HTML emails being sent, but I suspect that the percentage of really badly designed websites would be pretty close to it. Should we say that all websites impede communication because most people don’t design well? Consider transactional emails, things like hotel bookings and purchase receipts. Every single instance should have a plain text alternative of course, but being able to give the key information like booking dates or serial numbers a bit of visual weight is exactly what designers should be doing – making the experience better for the person on the end. Zeldman goes on to explain: Your uncle thinks 18pt bright red Comic Sans looks great, so he sends e-mail messages formatted that way. You cluck your tongue, or sigh, or run de-formatting scripts on every message you receive from him. When your uncle is the “designer,” you “get” why styled mail sucks. It sucks just as much when you design it, even if it looks better than your uncle’s work in the two e-mail programs that support it correctly. I’m assuming that he is exaggerating for effect here because his earlier link to our CSS support in email in 2007 article clearly shows that it is possible to design emails that work well for almost everybody. For even simpler proof, checkout our gallery of email designs, many of which work in every major email client, desktop and web. Instead of trashing the concept of HTML email based on bad designers and personal preference, it would be much more constructive to continue the fantastic work on web standards in browsers and extend it to the email clients. In fact, the W3C has recently held a workshop on HTML email to investigate the issues and possibilities. We should be thinking about what is best for our readers, and not ourselves. Some people don’t want to receive HTML email, and of course, they should not be forced to. Many people prefer HTML for some uses; who are we to tell them they should not want it? Spam is bad. Shoddy design is bad, and no arguments from us. Saying all HTML email sucks based on particular usages and personal preference is also bad. We should all have learnt by now that we as web designers are not in charge of what technology is going to be used for, it’s the people at the end of the chain who get to decide that. 5 steps to better HTML emails Always send a plain text alternative. Choose “HTML and plain text” as your campaign format. Design differently for email. Good design understands the context it will be seen in. Don’t just paste in your 3 column homepage Test in different email clients. Make sure your message can be read by everyone More copy, less images. You can’t rely on images being seen in emails. Listen to your readers. Don’t base your decisions on what Zeldman tells you, or what we tell you. Listen to your customers, they will tell you what they like and don’t like. Email is not a ‘platform for design’. Email is a communication tool, and sometimes HTML can communicate better than plain text. [UPDATE] Jeffrey Zeldman has responded to our concerns with a well thought out and much more moderate post, Eight points for better e-mail relationships. It’s definitely worth reading.
If you or your clients are targeting small to medium businesses, a recent survey entitled “Optimizing Email Newsletters for Small/Medium Businesses” has some useful information for you. According to the study of over 300 executives, email newsletters rank highly as sources of information, beating out websites and blogs, and matching print media for importance. A weekly or monthly newsletter was the preferred frequency, and ‘how to’ and product information the top content areas requested. This is some more valuable information you can use to explain the benefits of email marketing to your clients. Although the study specifically focused on small to medium (less than 500 person) businesses, it would be safe to extrapolate that out to most businesses and consumers. We’d be interested to know how often you or your clients send your newsletter – have you had the best results with monthly news, or weekly? Or something completely different?
A while back we wrote about 5 ideas you can use when pitching your email marketing services to your clients. These covered ideas like showing them how easy it is to measure the results and how targeted it can be. All very useful stuff, but probably not enough focus on the most important thing in your customers minds. How will it help me grow my business? Today, one of my favourite email marketing blogs pointed me to this great article by Loren McDonald on this exact topic. While the article is penned from the perspective of selling the benefits of email marketing internally, it’s just as useful when read from the perspective of designers and marketers pitching email to their clients. Instead of focusing your next pitch on the pretty reporting interface you can offer, or how you handle unsubscribes automatically, take it from an ROI angle. Drive home how you plan to use email to drive more sales, increase conversions or achieve some other tangible benefit. Something tells me you’ll be improving your own conversion rate in the process.
I couldn’t be happier with your product. I run my own design and communications company in Boston and my clients have been clamoring for a product like Campaign Monitor. Your pricing model is spot on and a huge improvement over your competitors, plus your interface is top notch. Keep up the *great* work. Karl Stier, Watershed Media
As part of a check up on our updated guide to CSS support we released around 6 weeks ago, I’ve just done a quick re-test in some of the major web-based email clients to make sure the results are still spot on. Well, my first test in and I spotted some discrepancies. Turns out Windows Live Mail’s recently noted decline continues with the e:link, e:active and e:hover CSS selectors no longer being supported. These changes make it much harder to style any links in your email, and because they can only be declared through the selector, can’t be solved by going the inline CSS route. We’ve updated the original article to reflect these changes, as well as the PDF summary, which you can re-download below: Download the updated 2007 results for all email environments (52kb) We’ll keep checking each environment on a regular basis to stay on top of any minor changes, and if you guys ever spot anything amiss, don’t hesitate to let us know.
If you’re used to coding your email newsletters for Gmail, you’re probably an expert on inline CSS by now. As our recent CSS research highlighted, Gmail doesn’t support the <style> or <link> element. This means if you want your links to be in a size 11 font and a light blue color, you’ll need to code something like… <a href="https://www.campaignmonitor.com" style="font-size:11px;color:#4fb5e9;">Visit the web site</a> to find out more OK, kind of annoying but it works. But what about our automatically generated links for unsubscribing, linking to a web-based version and adding a forward to a friend link. As you know, these are generated after you import your design from the tags present in your HTML, such as <unsubscribe> and <webversion> and up until now you couldn’t add your own inline CSS to them. Well, not until today anyway. Introducing the style=”” attribute By adding a style="" attribute to the unsubscribe, webversion and forward a friend tags, we’ll automatically add that inline CSS to the personalized links we create for each recipient. Using our example above, let’s say we want to make our unsubscribe link at the bottom of the email blue and in size 11 font. <unsubscribe style="font-size:11px;color:#4fb5e9;">Unsubscribe</unsubscribe> from our monthly newsletter list We’d get <a href="http://www.unsubscribeaddress.com" style="font-size:11px; color:#4fb5e9;">Unsubscribe</a> from our monthly newsletter list You can use exactly the same technique for the web version and forward to a friend tags too, such as <forwardtoafriend style=""></forwardtoafriend> and <webversion style=""></webversion>.
Join 250,000 in-the-know marketers and get the latest marketing tips, tactics, and news right in your inbox.Subscribe
With our powerful yet easy-to-use tools, it's never been easier to make an impact with email marketing.Try it for free