Matt posted a discussion of the portability of IP reputation over at his EmailKarma blog.
I have heard about Hotmail/MSN’s claim that if you add your new IPs to your SPF/SenderID record and send from your old IPs that your old IP reputation will transfer to your new IPs. I’ve not heard it working in practice, but it really can’t hurt to add your new IPs to your records as soon as you know what they are.
A few months ago I was working on a deliverability problem with a new client. They are a social networking site heavily branded with black background and pink text. One of the questions they asked me during the course of troubleshooting their delivery problems was if sending pink and black branded emails to match their site branding would decrease their deliverability.
That was actually a more interesting question than many I have received and led to the following analogy. A website is your showroom on the web. It is the equivalent of a brick and mortar store where people visit you and come to see what you have to offer for sale. Heavily branding the store is the right thing to do.
An email, be it marketing, transactional or relationship, is the equivalent of sending a traveling salesperson to someone’s house. That sales person is entering the customer’s space. In this case overly branding your presence in the customer’s space which can annoy or completely turn off your customers.
Branding emails to customers is a good thing; it builds brand recognition and customer relationships. Just remember, though, that you’re entering the customer’s space. Be respectful of that space.
As an aside, I did actually ask AOL about the color of email would decrease delivery. The nice folks over there did reply “AOL SAYS NO PINK!” But I’m fairly sure they weren’t serious.
Goodmail made a splash on the email marketing and ISP industries a few years ago by announcing their CertifiedEmail program. They guaranteed that using their certification would result in email going directly to the inbox, and all images in the email would be displayed by default. Senders using Goodmail would pay money, per message, and Goodmail would split that money with the receiving ISP.
This sounds very much like a situation where everyone wins. The senders get their mail to the inbox with images turned on. The receiving ISPs get a little money to deliver email and offloads some of their sender screening onto a third party. Individual recipients know that this email is certified and that it’s safe to click on links in the email.
In the time since CertifiedEmail has been announced, however, there seems to be very little adoption. Sure, receivers do seem to be signing up, a little. AOL and Yahoo have been using CertifiedEmail for a while. In summer 2007, a number of cable providers announced they would be using CertifiedEmail as well.
Senders, on the other hand, don’t seem to be adopting this as fast as Goodmail might like. The Federal Government recently announced they would be sending email signed by Goodmail and some large online companies, Overstock.com among them, are also sending with certified email. In order to get more companies to sign up for CertifiedEmail, Goodmail announced in August 2007 that they had partnered with CheetahMail, Episilon and Axciom Digital to provide free CertifiedEmail to qualifying customers of those ESPs.
Why might companies not be adopting CertifiedEmail? I have a couple of thoughts.
Before I can talk about permission and how a mailer can collect permission from a recipient to send them email I really need to define what I mean by permission as there are multiple definitions used by various players in the market. Permission marketing was a term coined by Seth Godin in his book entitled Permission Marketing.
The underlying concept beneath permission marketing is that all marketing should be “anticipated, personal and relevant.” Others have defined permission marketing as consumers volunteering or requesting to be marketed to.
When I talk about permission in the email marketing context I mean that the recipient understood *at the time they provided the sender with an email address* that they would receive email from that sender as a result.
Let’s look at some of the relevant parts of that definition.