Difference between revisions of "Email Marketing"
Jump to navigation
Jump to search
(cleanup and update some content) |
(adds another page in the Google help space for SMTP relaying) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
There are two related parts to email marketing: making sure that your content is in good form; and making sure that it is actually delivered which is purely technical in nature. | There are two related parts to email marketing: making sure that your content is in good form; and making sure that it is actually delivered which is purely technical in nature. | ||
| − | |||
| − | |||
| − | |||
They are related in that all major email service providers (GMail, HotMail, Yahoo!, Comcast, Verizon, etc) scan email '''content''' on the receiving side with some heuristics to determine a 'spam' score in addition to other more 'technical' measures. | They are related in that all major email service providers (GMail, HotMail, Yahoo!, Comcast, Verizon, etc) scan email '''content''' on the receiving side with some heuristics to determine a 'spam' score in addition to other more 'technical' measures. | ||
| − | + | == Audience == | |
| − | |||
| − | |||
| − | ==Audience== | ||
http://emailclientmarketshare.com/ shows that GMail, which only accounted for 4% of market share in early 2013, accounts for 15% at the end of 2015. Know your market. Know the current devices and technologies in use to read email. | http://emailclientmarketshare.com/ shows that GMail, which only accounted for 4% of market share in early 2013, accounts for 15% at the end of 2015. Know your market. Know the current devices and technologies in use to read email. | ||
| − | ==Content and Tools== | + | == Content and Tools == |
You want to do an email campaign. You need to know what works and what doesn't in email these days. Email is not the web. It's worse. | You want to do an email campaign. You need to know what works and what doesn't in email these days. Email is not the web. It's worse. | ||
| Line 21: | Line 15: | ||
But even with these great tools, you still need help. | But even with these great tools, you still need help. | ||
| − | #The email standards project http://www.email-[http://dev.email-standards.org/clients/ clients]" page that shows which email clients actually fare well in an ACID test, and those that don't (looking at you Gmail and Hotmail) | + | # The email standards project http://www.email-[http://dev.email-standards.org/clients/ clients]" page that shows which email clients actually fare well in an ACID test, and those that don't (looking at you Gmail and Hotmail) |
| − | #Campaign Monitor offers a number of [https://www.campaignmonitor.com/guides/ guides], including [https://www.campaignmonitor.com/css/ a complete breakdown of the CSS support for every popular mobile, web and desktop email client on the planet]. They also offer hundreds of free to use templates and design examples. | + | # Campaign Monitor offers a number of [https://www.campaignmonitor.com/guides/ guides], including [https://www.campaignmonitor.com/css/ a complete breakdown of the CSS support for every popular mobile, web and desktop email client on the planet]. They also offer hundreds of free to use templates and design examples. |
| − | #Premailer (http://premailer.dialect.ca/) is a cool service that will allow you to test your email content before you send it. It will convert CSS styles to inline style attribues. It gives you HTML and CSS warnings (including those from the Email Standards project). It will also generate the text-only version for you. Premailer is written in Ruby, with a lot of help from Nokogiri, Hpricot and the Sinatra framework (goodbye eruby). The [https://github.com/premailer/premailer source is available] on GitHub. As of 2014, there was discussion of making a 2.0 version, but it's 2015 now and there isn't a separate branch, so maybe the "new version" is just being incrementally built into the current. | + | # Premailer (http://premailer.dialect.ca/) is a cool service that will allow you to test your email content before you send it. It will convert CSS styles to inline style attribues. It gives you HTML and CSS warnings (including those from the Email Standards project). It will also generate the text-only version for you. Premailer is written in Ruby, with a lot of help from Nokogiri, Hpricot and the Sinatra framework (goodbye eruby). The [https://github.com/premailer/premailer source is available] on GitHub. As of 2014, there was discussion of making a 2.0 version, but it's 2015 now and there isn't a separate branch, so maybe the "new version" is just being incrementally built into the current. |
| − | #Putsmail (https://putsmail.com/) is another free option to test your email messages. It's owned by 'Litmus' (litmus.com) which is a paid service if you need more. And emailonacid.com is another paid service. | + | # Putsmail (https://putsmail.com/) is another free option to test your email messages. It's owned by 'Litmus' (litmus.com) which is a paid service if you need more. And emailonacid.com is another paid service. |
| − | ==Technical== | + | == Technical == |
This Rackspace article covers the 3 types of DNS records you need to know about for Email delivery: http://www.rackaid.com/blog/email-dns-records/ | This Rackspace article covers the 3 types of DNS records you need to know about for Email delivery: http://www.rackaid.com/blog/email-dns-records/ | ||
| − | |||
| − | + | Aside from domain SPF records, one option you have for sending is 'smart hosting' which is to say SMTP relaying your mail off to your service provider such as Google Apps. See [https://support.google.com/a/answer/176600?hl=en here] and/or [https://support.google.com/a/answer/2956491?hl=en here] for how to configure your Google Apps domain for SMTP relaying. If you are going to send larger volumes of email than surpass the limits of your Google Apps account, you will want to use the services of SendGrid, Dyn, MailChimp etc. SendGrid actually has a free service tier for < 17,000 messages per month. These services can not only handle the deliverability aspect, but also handle bounces on transactional email messages also. | |
| − | |||
| − | |||
| − | for | + | The documentation for CiviCRM has a fairly comprehensive guide to setting up your email. http://book.civicrm.org/user/current/advanced-configuration/email-system-configuration/ |
| − | + | === Postmaster === | |
| + | Comcast and others have their 'Postmaster' websites with tools and info for help | ||
| + | # http://postmaster.comcast.net/index.html | ||
| + | # https://postmaster.aol.com/ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Unfortunately, your hosting provider may be crippling your email service without even advertising the fact. https://warrenguy.me/blog/ipv6-digital-ocean-crippled | Unfortunately, your hosting provider may be crippling your email service without even advertising the fact. https://warrenguy.me/blog/ipv6-digital-ocean-crippled | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Email]] | [[Category:Email]] | ||
[[Category:Marketing]] | [[Category:Marketing]] | ||
[[Category:Standards]] | [[Category:Standards]] | ||
| − | |||
