When best practices don’t work

I started out with the best intentions to get back into the swing of things with blogging more regularly. But between MAAWG recovery, COVID recovery and life it’s not worked out that way.

This is an excerpt of something I wrote over on slack to explain why someone was still struggling with delivery even though best practices weren’t working. Hope it will be helpful for some folks. (and now I’m off to my next call…)

When the issue is a mailstream that has problems that aren’t being addressed by common best practices. In order to address that we need to understand more about why the common best practices aren’t working. They may not be zebras, but they might be donkeys.

So I started with listing “these are the problems I’ve seen with mailstreams of your type and why those problems aren’t being resolved by the normal practices.”

Email delivery really boils down to that everything we do about email reinforces the idea that the email address owner / user has control over that address. They get to choose what they want to receive. Filters are using the data they collect from the users to try and sort out which mail has permission and which doesn’t. A lot of the hygiene is (quietly) trying to remove data inputs that are going to indicate that the mail is unwanted and make it more likely that the mail looks wanted / permissioned.

In cases like this, where we’ve done all the standard things and delivery is still getting worse we need to think about how we model our audience. For instance, a lot of folks will sign a petition, but they don’t often want a lot of follow up mail about the petition they signed. So the mail is not really wanted by the folks who gave their addresses – and in a lot of cases depending on the petition site they might be told they won’t receive mail as a result of signing up only to discover that the privacy policy is out of date (I’ve investigated these sites and found multiple contradictory privacy policies / terms of use / what to expect).

Overall, the underlying problem here is, in my experience, likely that the recipients are assuming one thing about what’s going to happen when they sign and the sender is assuming a different thing about what is happening. And, in this case, the recipients who signed but don’t want the mail are a large enough group of recipients that it’s causing data problems.The trick will be to find those folks who actually do want the followup mail and who do want to participate in a broader political action and to drop those folks who just want to do the easy thing. This isn’t going to be done with a third party tool or data hygiene provider. It’s going to need a lot more investment in developing the audience that’s going to support the inbox delivery that the sender wants.

Make your mailing look like it’s wanted / asked for by more folks than don’t want it is the ‘one secret trick to inbox delivery’ … easy to say but in some cases requires real thought about who your target market is.

Related Posts

Deliverability Help: Information checklist

When asking a for assistance with email delivery, there are some pieces of information that are required before anyone can help. Be prepared with the information so you can get timely assistance. This advice is true whether you’re looking for help from peers or working with paid deliverability consultants.

Read More

ESPs and deliverability

There’s an ongoing discussion, one I normally avoid, regarding how much impact an ESP has on deliverability. Overall, my opinion is that as long as you have a half way decent ESP they have no impact on deliverability. Then I started writing an email and realised that my thoughts are more complex than that.

Read More

Wildfires and deliverability

A few weeks ago we took a drive down I5 to attend a service at Bakersfield National Cemetery. Amid the acres and acres of almond farms there were patches of black from recent grassfires. Typical but boring California landscape. Wildfires are a hugely destructive but continual threat in California. Growing up on the east coast, I never really understood wildfires. How can acres and acres and square miles just burn?
Having lived in California for almost as long as I lived on the east coast, I understand a bit better. In some ways, I have to. Even living right on the bay, there’s still some risk of fire. Like the grass fire a few miles from here across the street from the FB headquarters a few years ago. Further up the hills, there’s an even bigger risk of fire. Every driver can see the signs and precautions. Fields have plowed firebreaks around the edges. CAL FIRE posts signs alerting the public to the current fire risk status.
Fire Danger
What do wildfires have to do with deliverability?
I associate wildfires and deliverability together because of a radio show I did a few years ago. It was pitched as a “showdown” between marketers and deliverability. I was the representative of deliverability. During the conversation, one of the marketers mentioned that deliverability people were too focused on the worst case scenario. That we spoke like we expected a fire to break out at any moment. His point was that deliverability spent too much time focused on what could happen and not enough time actually just letting marketers send mail.
His overall point was deliverability people should put out the fires, rather than trying to prevent them in the first place.
I thought about that conversation during the long drive down I5 the other day. I saw the firebreaks plowed into fields at the side of the road. And I saw the patches of blackness from fires reach along the highway where there were no firebreaks.
There are a group of marketers who really hate the entire concept of deliverability. Their point of view is that deliverability is hampering their ability to make money. I’ve even heard some of them assert they don’t care if 70% of their mail goes to the bulk folder. They should be allowed to send blasts of mail and deliverability shouldn’t tell them what they can do. Deliverability, so the complaint goes, is simply out to hurt marketers.
The only good deliverability is that which gets them unblocked when their behavior triggers IP based blocks. When the field is burning down, they’d like us to come spray water on it. And then go away and let them keep throwing lit cigarettes out their car windows.
But that’s not all that firefighting is about. Much of the work is preventing fires in the first place.  In the US, a lot of that work is done through building codes. There are mandates like smoke detectors, fuel free spaces around dwellings, and sprinklers for some buildings. Monitoring local conditions and enforcing burn bans are also a large part of what the fire service does.
I like the fire fighter motif a lot. Much of what deliverability does is actually about preventing the block. ESPs have building code like standards for what mail is good and what is bad and what can be sent on their networks. Many of us publicly speak and educate about good practices and preventing blocks in the first place.
Fire prevention is about risk management and understanding how little things add up. Deliverability is similar. All the little things senders do to improve their deliverability adds up to a lower risk of fire. Yes, things like listbombing happen where even the best deliverability advice wouldn’t have prevented it. But, overall, deliverability wants to help senders get their mail in front of the people who can act on it. Some of that advice, though, takes the form of risk management and saying no.

Read More