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
The best digital and email marketing content by Campaign Monitor.
As far as we’re concerned, your clients never need to know you use Campaign Monitor to send their email campaigns. We never touch your email content, let you add your own confirmation pages and generally avoid mentioning campaignmonitor.com like the plague. There was however always one thing that bothered us – our generic confirmation pages. If you don’t provide your customers with their own landing page for new subscribers, unsubscribers, etc, we provide generic pages as a fallback. Only problem is, these pages were referencing the campaignmonitor.com server. No more! From today, your generic landing pages will be referenced at your customized sub-domain. For example, your client ABC Widget’s unsubscribe confirmation page will now sit at http://abcwidgets..com/ If you guys can think of anything else we can tweak so we don’t blow your cover, please let us know.
Whoah! We just found out that we’ve been selected as finalists for Creative Good’s 2006 Copernican Award. Here’s what they’re all about: “The Copernican Awards are awarded annually to top companies and organizations that succeed by putting customers at the center of their ‘business universe’.” It’s an honor to be in the same company as the 16 other amazing finalists, such as Google, Threadless and del.icio.us. It’s been an amazing 18 months since we launched Campaign Monitor. We’ve made loads of friends around the world, helped almost 10,000 customers with their email marketing and even contributed to a book or two. We’re heading to New York in a couple of weeks for the awards dinner, and we look forward to catching up with plenty of you guys while we’re over there. You can check out more about the award here.
Update: This study has since been superceded by the new and improved 2008 Edition Since the rise of Internet Explorer, web designers have had to test their designs across multiple web browsers. No one likes it, but we’ve all copped it on the chin, written a few hacks and moved on with our lives. After all, 3 to 4 browsers aint that bad – and they finally seem to be getting their act together. If Internet Explorer is the schoolyard bully making our web design lives a little harder, then Hotmail, Lotus Notes and Eudora are serial killers making our email design lives hell. Yes, it’s really that bad. Inspired by the fantastic work of Xavier Frenette, we decided to put each of the popular email environments to the test and finalize once and for all what CSS is and isn’t supported out there. We’ll dig straight into our recommendations based on what we found, followed by the results themselves with a few more details about our findings. Recommendations Because of the huge variation of support across each email environment, there really isn’t any one design approach that will guarantee consistency. Instead, you should take a couple of things into account. 1. The consistency demands of your client If you have a client who understands the challenges you face and realizes that some email environments are just plain old broken (we can always dream), I recommend going for broke and following Mark Wyner’s recent article on CSS design in email (we even include a free template to get you started). This allows you to code your email using moderns standards based design that degrades gracefully for these “broken” email environments. On the other hand if your client demands consistency no matter what, or the CEO’s using Lotus Notes, you’ll have to dull down your design, stick with tables for layout and use only basic text formatting via CSS. You may even have to go down the inline CSS route. 2. The potential email environment of your recipients You’ll probably need to generalize a little here, because most of us have no idea what email environment each recipient is using. Business to Business If you’re sending Business to Business (B2B) emails, you’re definitely going to have to support Outlook and to a lesser extent Lotus Notes. In a recent survey of B2B readers, EmailLabs found that more than 75% use a version of Outlook and a further 9% use Lotus Notes. The good news is that Outlook’s support for CSS is quite good, but Notes’ certainly isn’t. You’ll need to weigh up the trade-offs yourself there. Business to Consumer If you’re sending Business to Consumer (B2C) campaigns, then you’ll definitely need to have Yahoo!, Hotmail and possibly AOL covered. Gmail’s still purring under 5% total penetration, but if you’re targeting early adopters then this percentage will likely be significantly higher. Yahoo and AOL offer very respectable CSS support. Hotmail isn’t too painful provided you include your <style> element in the <body> and not the <head>, while Gmail gives you no choice but to use inline styles only. Further to these concerns, there’s also the issue of image blocking and preview panes, but that’s a whole other article. Results Down to the nitty gritty. To cover each email environment, we’ve split our results up into web-based, PC and Mac email software. Use the links below to jump straight to the respective findings. Web-based results – Gmail, Hotmail, Yahoo! and Windows Live Mail PC results – Outlook 2003 and Outlook Express, Lotus Notes, Thunderbird Mac results – Mac Mail, Entourage, Eudora Web-based Xavier covered the web-based email environments perfectly, but we decided to throw Microsoft’s new Windows Live Mail into the mix to gaze into the crystal ball and see if Hotmail may have a brighter future. The biggest improvement we found being support for the <style> element in the <head> of your page. The <style> element The standard place for the style element is in the <head> of the document, but to ensure the styles appear in Hotmail, you can also insert them within the <body>. We tested both, just to make sure. Web-based support for the <style> element Gmail Hotmail Yahoo! Mail Windows Live Mail <style> element in the <head> No No Yes Yes <style> element in the <body> No Yes Yes Yes The <link> element The <link> element is used to reference a separate CSS file. Web based email environments offer no support for this element, so I recommend playing it safe and sticking with the <style> element for your CSS. Web-based support for the <link> element Gmail Hotmail Yahoo! Mail Windows Live Mail <link> element in the <head> No No No No <link> element in the <body> No No No No CSS Selectors Selectors are used to “select” specific elements on a page so that they can be styled. Besides Gmail, most web-based email environments offer pretty good selector support. Web-based support for CSS Selectors Gmail Hotmail Yahoo! Mail Windows Live Mail * No Yes Yes Yes e No Yes Yes Yes e > f No No Yes No e:link No Yes Yes Yes e:active, e:hover No Yes Yes Yes e:focus No No Yes No e+f No Yes Yes No e[foo] No Yes Yes No e.className No Yes Yes Yes e#id No Yes Yes Yes e:first-line No Yes Yes Yes e:first-letter No Yes Yes Yes CSS Properties CSS property support ranges from very good (Yahoo!) down to so-so (Gmail). If you want results in Gmail, you’ll need to do your styles inline (<p style="...">this is pretty now</p>) rather than via the <style> element. Web-based support for CSS Properties Gmail Hotmail Yahoo! Mail Windows Live Mail background-color Yes Yes Yes Yes background-image No Yes Yes No background-position No No No No background-repeat No Yes Yes No border Yes Yes Yes Yes border-collapse Yes Yes Yes Yes border-spacing Yes No Yes No bottom No Yes Yes No caption-side Yes No Yes No clear No Yes Yes Yes clip No Yes Yes No color Yes Yes Yes Yes cursor No Yes Yes Yes direction Yes Yes Yes Yes display No Yes Yes Yes empty-cells Yes No Yes No filter No No Yes Yes float No Yes Yes Yes font-family No Yes Yes Yes font-size Yes Yes Yes Yes font-style Yes Yes Yes Yes font-variant Yes Yes Yes Yes font-weight Yes Yes Yes Yes height No Yes Yes Yes left No Yes Yes No letter-spacing Yes Yes Yes Yes line-height Yes Yes Yes Yes list-style-image No Yes Yes No list-style-position Yes No No Yes list-style-type Yes No Yes Yes margin Yes No Yes No opacity No No Yes Yes overflow Yes Yes Yes Yes padding Yes Yes Yes Yes position No No No No right No Yes Yes No table-layout Yes Yes Yes Yes text-align Yes Yes Yes Yes text-decoration Yes Yes Yes Yes text-indent Yes Yes Yes Yes text-transform Yes Yes Yes Yes top No Yes Yes No vertical-align Yes Yes Yes Yes visibility No Yes Yes Yes white-space Yes Yes Yes No width Yes Yes Yes Yes word-spacing Yes Yes Yes Yes z-index No Yes Yes No PC Aside from Lotus Notes, all our PC-based email clients behaved very well. All versions of Outlook, Outlook Express and AOL 9 use Internet Explorer to render their emails, so some selectors weren’t supported. This also means you’ll still need to allow for the range of CSS problems IE introduces. Thunderbird scored beautifully. The <style> element Perfect support except for Lotus Notes, which ignores the <style> element altogether. PC support for the <style> element Outlook 2003/OE AOL 9 Lotus Notes Thunderbird <style> element in the <head> Yes Yes No Yes <style> element in the <body> Yes Yes No Yes The <link> element The <link> element is very well supported on the PC, the only shortfall being that your remote CSS file will not be loaded if images are also disabled. Once images are enabled, your CSS will also load correctly. PC support for the <link> element Outlook 2003/OE AOL 9 Lotus Notes Thunderbird <link> element in the <head> Yes Yes Yes Yes <link> element in the <body> Yes Yes Yes Yes CSS Selectors Thunderbird scored highly, but because the majority use IE to render your email, selector support is limited. PC support for CSS Selectors Outlook 2003/OE AOL 9 Lotus Notes Thunderbird * Yes Yes No Yes e Yes Yes No Yes e > f No No No Yes e:link Yes Yes No Yes e:active, e:hover Yes Yes No Yes e:focus No No No Yes e+f No No No Yes e[foo] No No No Yes e.className Yes Yes No Yes e#id Yes Yes No Yes e:first-line Yes Yes No Yes e:first-letter Yes Yes No Yes CSS Properties You can have a field day as long as you’re not sending to Notes. It offers dismal property support that includes only very basic text manipulation. PC support for CSS Properties Outlook 2003/OE AOL 9 Lotus Notes Thunderbird background-color Yes Yes No Yes background-image Yes Yes No Yes background-position Yes Yes No Yes background-repeat Yes Yes No Yes border Yes Yes No Yes border-collapse Yes Yes No Yes border-spacing No No No Yes bottom Yes Yes No Yes caption-side No No No Yes clear Yes Yes No Yes clip Yes Yes No Yes color Yes Yes Yes Yes cursor Yes Yes No Yes direction Yes Yes Yes Yes display Yes Yes Yes Yes empty-cells No No No Yes filter No No No No float Yes Yes No Yes font-family Yes Yes Yes Yes font-size Yes Yes Yes Yes font-style Yes Yes Yes Yes font-variant Yes Yes No Yes font-weight Yes Yes Yes Yes height Yes Yes No Yes left Yes Yes No Yes letter-spacing Yes Yes No Yes line-height Yes Yes No Yes list-style-image Yes Yes No Yes list-style-position Yes Yes No Yes list-style-type Yes Yes Yes Yes margin Yes Yes No Yes opacity No No No Yes overflow Yes Yes No Yes padding Yes Yes No Yes position Yes Yes No Yes right Yes Yes No Yes table-layout Yes Yes No Yes text-align Yes Yes Yes Yes text-decoration Yes Yes Yes Yes text-indent Yes Yes No Yes text-transform Yes Yes No Yes top Yes Yes No Yes vertical-align Yes Yes No Yes visibility Yes Yes No Yes white-space No No No Yes width Yes Yes No Yes word-spacing Yes Yes No Yes z-index Yes Yes No Yes Mac While Mac Mail and Entourage offer fantastic support across the board, I wasn’t surprised to find that Eudora refused to come to the party. Basically, Eudora sucks. The <style> element Go for it, just ignore Eudora. Mac support for the <style> element Mac Mail Entourage Eudora <style> element in the <head> Yes Yes No <style> element in the <body> Yes Yes No The <link> element Same old story, no Eudora. Mac support for the <link> element Mac Mail Entourage Eudora <link> element in the <head> Yes Yes No <link> element in the <body> Yes Yes No CSS Selectors Mac Mail support was fantastic and Entourage was a close second. Mac support for CSS Selectors Mac Mail Entourage Eudora * Yes Yes No e Yes Yes No e > f Yes Yes No e:link Yes Yes No e:active, e:hover Yes Yes No e:focus Yes Yes No e+f Yes No No e[foo] Yes No No e.className Yes Yes No e#id Yes Yes No e:first-line Yes Yes No e:first-letter Yes Yes No CSS Properties Property support was also top notch, except for Eudora, with no property support whatsoever. Mac support for CSS Properties Mac Mail Entourage Eudora background-color Yes Yes No background-image Yes Yes No background-position Yes Yes No background-repeat Yes Yes No border Yes Yes No border-collapse Yes No No border-spacing Yes No No bottom Yes Yes No caption-side No No No clear Yes Yes No clip Yes Yes No color Yes Yes No cursor Yes No No direction Yes No No display Yes Yes No empty-cells Yes No No filter No No No float Yes Yes No font-family Yes Yes No font-size Yes Yes No font-style Yes Yes No font-variant Yes Yes No font-weight Yes Yes No height Yes Yes No left Yes Yes No letter-spacing Yes Yes No line-height Yes Yes No list-style-image Yes Yes No list-style-position Yes Yes No list-style-type Yes Yes No margin Yes Yes No opacity Yes No No overflow Yes No No padding Yes Yes No position Yes Yes No right Yes Yes No table-layout Yes Yes No text-align Yes Yes No text-decoration Yes Yes No text-indent Yes Yes No text-transform Yes Yes No top Yes Yes No vertical-align Yes Yes No visibility Yes Yes No white-space Yes Yes No width Yes Yes No word-spacing Yes Yes No z-index Yes Yes No We hope you find these results helpful. Let’s hope that as browsers move forward, ISP’s and email client developers follow suit. It’s our sanity at stake here, right? UPDATE: After an oversight pointed out by Lachlan Hunt, we’ve scaled back Eudora’s CSS support to nil, zilch, zero.
While we make it very easy to export your unsubscribed and active subscribers out of your subscriber lists, itís always been a challenge to extract that data on a per-campaign basis. We just pushed an update live that now allows you to export any part of the Recipient Activity Report. To refresh your memory, this is a pretty sweeping report that lets you access information on recipients who: Opened the campaign Did not open the campaign Clicked a link Did not click a link Unsubscribed Now you can export any one of these reports into a Comma Separated Values (CSV) or tab delimited text file with the click of a button. This one’s been pretty high on the wish list for lots of customers, so we hope you find it useful.
This has been a heavily requested feature for a while now and it’s great to get it out the door. From today, you can easily personalize your subscribe confirmation emails. If you’re using a single opt-in list, you can add your subscriber’s first name, last name, full name or email address to their optional confirmation emails. If you’re using a double opt-in list, you can personalize both the initial verification email (where the subscriber needs to click a link) as well as the optional confirmation email. Verification and especially confirmation emails can be very effective in getting off on the right foot with your new subscribers. Here are a few ideas you can try: Start by welcoming your new subscribers (by name if possible) and encourage them to add your sending email address to their address book. This can dramatically increase the chances of it being delivered and displaying as intended. A great way to encourage new people to join your list is by offering a free white-paper or other resource. By sending a confirmation email, you can qualify their email address and send them the link to their reward from the confirmation email. Develop that relationship a little further. Remind each subscriber why they signed up and let them know they should be looking forward to when they receive your next newsletter. As usual, you can also provide fallback terms if we don’t have your subscriber’s name on file.
Just a quick one. A few customers have had problems recently trying to import rare email addresses that have strange characters, such as the plus (+) and forward slash (/). After running a few tests to ensure these characters are widely supported, we’ve just updated our email address filters to allow both of these kinds of addresses to be imported.
Now that you can set pre-defined options for your custom fields and create segments based on those options, the next logical step is to make it easy for you guys to create subscribe forms to capture this data. When you create a subscribe form with pre-defined custom fields, you now have the option of specifying which type of form element you’d like to use. If a subscriber can select more than one option, such as their interests or their email format preference, you can use either checkboxes or a multiple-select list. If a subscriber can only select one option, like star sign or state, you can use either a single-select list or radio buttons. As usual, we still generate 3 types of HTML code for you – basic, CSS based and tabled based formatting options.
We’ve made it very simple to create a form on your web site where new subscribers can sign up to your list (we provide the code, you just have to copy and paste). But what about when you’ve already got a form, and you simply want to add a checkbox where customers can opt-in to your newsletter? This isn’t quite a copy and paste job, but it’s not far off. Lets take a look at a simple example. Your client’s site has a ‘Contact Us’ form, which sends an email to your client with the details of a customer enquiry. They’ve just decided that they want to add a little ‘Subscribe to our newsletter’ checkbox. How are you going to integrate this with Campaign Monitor? Here’s a few ways: 1. Use an extension or plugin This is the simplest of all if you happen to be using a suitable CMS or shopping cart. We’ve got a bunch of downloadable plugins, extensions and modules for systems like Expression Engine, Joomla and FoxyCart. Over on the right of this page you’ll see direct links to some of them. Check there first because it may be someone has already done the hard work for you. 2. Using the API Lots of you already know about (and use) the API, and this is the obvious way you can achieve this. In our example, when a user submits the contact form on your clients web site, your already going to have some code in place to gather the contents of the form, and send them off to your client in an email (usually in something like PHP, ASP.NET, Perl etc). We just need to make a slight addition to this. Using your programming language of choice you can check to see if the user has checked the ‘Subscribe to our newsletter’ checkbox, and if they have, make a call to our API to save this person to your subscriber list. And don’t worry if they’re already in there – we won’t add them twice. 3. Redirecting to specific URL’s If your not too keen on the idea of calling our API, there’s another method you can use, which works by redirecting to a URL on our server which will save the user to the list, then send them back to your server. So just like before, you gather the contents of your form, and send the email to your client. Now, to get the users name and email address into Campaign Monitor, we need to redirect the user to a specific URL. What this redirect stuff you keep mentioning? All server side languages should have an easy way to send the user to another URL. In PHP you would use something like: header( "Location: hhttp://www.urlhere.com" );and in ASP.NET it would look likeResponse.Redirect("http://www.urlhere.com"). So let’s get down to specifics. The URL that we need to send the user to, is the same URL that we use in the Create a Subscribe Form code. Check out this code and you’ll see something like: <form action="http://myclient.thisapp.com/p/a/t/tos/" method="post">. The action URL is what we’re after, so in this case http://myclient.thisapp.com/p/a/t/tos/. We’re almost done, but when we redirect the user to the URL we need to include their email address (and optional name). We do this by adding them to the URL in a format like this:?firstname.lastname@example.org&cm-name=Joe+Bloggs. So the full code in PHP would beheader( "Location: http://myclient.thisapp.com/p/a/t/tos/ ?email@example.com&cm-name=Joe+Bloggs" );. The important points to note are the question mark (?) to show the start of the variables, the ampersand (&) to separate the values we’re passing in, and the plus sign (+) which should be used to replace any spaces in the name. Of course, you’ll need to grab the name and address values from your existing form, and plug those in where we have firstname.lastname@example.org for example. When the user is redirected to the above URL, they will be added to your list, but what happens next? Well, hopefully you’ve added a custom subscribe page (and if you haven’t, just jump into the “Create a Subscribe Form” options in your list and add one), and the user will be redirected back to the subscribe confirmation page you’ve specified. The best part is, both of these approaches happen so quickly the user won’t notice a thing.
As part of our recent segmentation and custom field update, we’ve just updated the subscriber exporting tool. From today, you can now easily export all your custom field information for each subscriber, including custom fields with multiple values. We have separated each of the multiple values by a comma, so it should be very easy to re-import this data into another application or database.
A few customers were recently having a problem using Japanese in the subject line of their campaigns. Testing for problems with a language you don’t speak is always going to be a little tricky, so I want to give a big thanks to Jeremy Hedley who’s been extremely helpful in nailing a few issues with Japanese campaigns (even going as far as testing the results across multiple platforms and email clients). So, thanks to Jeremy’s help, subjects with Japanese characters should work fine now – but please be cautious, a number of email clients won’t handle the characters properly. Based on the results of our tests using default settings, the following email clients DO NOT display Japanese correctly in the subject line: Outlook Outlook Express Hotmail (basic US account) Yahoo! Mail (basic US account) Eudora (PC version only) Lotus Notes The following email clients DO support Japanese characters in the subject line: Gmail Mac Mail Eudora (Mac only) Microsoft Entourage Mozilla Thunderbird Unfortunately the problem isn’t going to go away for good until support for these characters is added to many of the popular email platforms.
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