Best practices or required practices

What really are the best practices for email?

A year ago I wrote a post about best practices and how most of my best practices were different from what other people recommend. I don’t talk about rules for frequency or subject line length. I don’t focus on best practices for bounce processing or content length.
BestPracticesBallMy best practice recommendations are really about process.

  • Send only opt-in mail.
  • Send mail correctly.
  • Identify yourself in email.
  • Honor unsubscribe requests.

The rest is all about the relationship between senders and their recipients.

But what does that mean?

It means that every sender should know who their audience is. Send mail that audience wants. If they want mail daily? Send daily. If they want mail weekly, send weekly. You’re the expert on who your audience is. Without knowing more about that audience no one should be giving you advice on anything like content or cadence or call to action or subject line length or whatever. Those are really specific to each program.

That sounds complicated.

Well, it’s not intro level deliverability that’s for sure.
Really knowing your audience isn’t something every company can, or even should, do. For many companies email is a part of their business, but isn’t really what they do. Email is a tool, and as long as that tool is working and deliverability is good there doesn’t need to be a commitment to really figuring out how to use it. Other companies, though, are built around email. Email is vital to their sales process or their customer communication process. In these cases, it is a good idea to commit the resources to improving delivery and email processes to get the best results.

Does it work?

It does! Look at what Louis C.K. did with his marketing. He broke all the rules, but made his audience happy. He knows his audience and he knows his brand and he carries that into his email campaigns. Other folks who “broke the rules” include Groupon and other daily deal sites. They broke the “rule” of no daily email except those users want the daily emails. Do daily emails work for everyone? Nope. But they work for some.
Lately I’ve been working with clients who start out with good deliverability, but are looking for some assistance with tweaking their strategy. It’s a challenge to think about what tweaks we can do to make a good program better. I’ve also been talking with other experts in the field and realizing that there is a place for advanced deliverability recommendations. What works in one vertical may not work in another. In some cases, other restrictions (privacy laws in some jurisdictions) may make common best practices not work or a worst practice.

How are you going to help?

We’ve always had a lot of plans for sharing more information. The blog is a big part of that, but we’re looking at other channels and things. I think some good things are going to come out of this and am excited to share them with you over the coming year.
 

Related Posts

Delivery challenges increasing

Return Path published their most recent Global Deliverability report this morning. (Get the Report) This shows that inbox placement of mail has decreased 6% in the second half of 2011. This decrease is the largest decrease Return Path has seen in their years of doing this report.
To be honest, I’m not surprised at the decrease. Filters are getting more sophisticated. This means they’re not relying on simply IP reputation for inbox delivery any longer. IP reputation gets mail through the SMTP transaction, but after that mail is subject to content filters. Those content filters are getting a lot better at sorting out “wanted” from “unwanted” mail.
I’m also hearing a lot of anecdotal reports that bulk folder placements at a couple large ISPs increased in the first quarter of 2012. This is after the RP study was finished, and tells me increased bulk folder placement is more likely to be a trend and not a blip.
One of the other interesting things from the RP study is that the differences are not across all mail streams, but are concentrated in certain streams and they vary across different regions.

Read More

June 2014: The month in email

Each month, we like to focus on a core email feature or function and present an overview for people looking to learn more. This month, we addressed authentication with SPF.
We also talked about feedback mechanisms, and the importance for senders to participate in FBL processes.
In our ongoing discussions about spam filters, we took a look at the state of our own inboxes and lamented the challenge spam we get from Spamarrest. We also pointed out a post from Cloudmark where they reiterate much of what we’ve been saying about filters: there’s no secret sauce, just a continuing series of efforts to make sure recipients get only the mail they want and expect to receive. We also looked at a grey area in the realm of wanted and expected mail: role accounts (such as “marketing@companyname.com”) and how ESPs handle them.
As always, getting into the Gmail inbox is a big priority for our clients and other senders. We talked a bit about this here, and a bit more about the ever-changing world of filters here.
On the subject of list management, we wrote about the state of affiliate mailers and the heightened delivery challenges they face getting in the inbox. We got our usual quota of spam, and a call from a marketer who had purchased our names on a list. You can imagine how effective that was for them.
And in a not-at-all-surprising development, spammers have started to employ DMARC workarounds. We highlighted some of the Yahoo-specific issues in a post that raises more questions.
We also saw some things we quite liked in June. In the Best Practices Hall of Fame, we gave props to this privacy policy change notification and to our bank’s ATM receipts.
We also reviewed some interesting new and updated technology in the commercial MTA space, and were happy to share those findings.

Read More