Deliverability session at Connections 2016
If you’re at Connections 2016 stop by our session at 3:00 in the Sidney Marcus Auditorium. Bring your pressing deliverability questions.
If you’re at Connections 2016 stop by our session at 3:00 in the Sidney Marcus Auditorium. Bring your pressing deliverability questions.

Tomorrow I head off to New Orleans to the EEC conference. It’s my first one and I’m really looking forward to meeting some of the people I only know online.
I’ll be speaking on two panels on Friday:
All You Ever Wanted to Know about Deliverability (But Were Afraid to Ask) at 10:50. This is your chance to ask those questions of myself and other experts in the field. I always enjoy Q&A panels and actually hearing from folks what their big deliverability questions are. (and remember, if you have a question, you can always send one to me for Ask Laura)
and the closing Keynote panel
ISP Postmasters & Blacklist Operators: Defending Consumer Inboxes at 1:10. I’m on a panel with various ISP postmasters, blacklist operators and we’ll be talking about what it’s like dealing with the deluge of mail. For instance, there is a huge outbreak of bot-spam at the moment, and a lot of the filters are struggling to keep up. In fact, I’m a last minute replacement for one filter company as they are in all-hands-on-deck firefighting mode to keep their customers safe.
Hope to see you there!
Most deliverability problems don’t start where many people think they do. So very often people call looking for deliverability help and tell me all about the things they’re doing to reach the inbox. They’ll tell me about content, they’ll tell me about bounces, they’ll talk about complaints, engagement, opens and clicks. Rarely will they bring up their list source without some prompting on my part.
The reality is, though, that list source is to root of deliverability success and deliverability problems. Where did those addresses come from and what do the people who gave them think you’re going to do with them?
Outsourcing collection to a third party can cause significant issues with delivery. Letting other people collect addresses on your behalf means you lack control over the process. And if you’re paying per address, then there monetary incentive for that company to pad the list with bogus addresses.
Sometimes there are even issues with having your own employees collect addresses from customers. For instance, a retailer requires sales associates collect a minimum percentage of addresses from customers. The company even ties the associates’ evaluations to that percentage. Associates have an incentive to submit addresses from other customers. Or a retailer will offer a discount for an address and customers want the discount but not the mail, so they give a fake address.
All of these things can affect deliverability.
Address collection is the key to delivery, but too many companies just don’t put enough attention to how they’re collecting addresses and entering into the relationship with subscribers. This is OK for a while, and delivery of small lists collected like this can be great. But as lists grow in size, they come under greater scrutiny at the ISPs and what used to work doesn’t anymore.
The first step to diagnosing any delivery problem is to look at the list. All of the things ISP use to measure reputation measure how well you’re collecting addresses. Changing IPs or domains or content doesn’t change the reason mail is being filtered. It just means the filters have to figure out something new to key on.
Want great deliverability? Start with how you’re collecting addresses.
Want to fix deliverability? Start with how you’ve collected addresses, how you’ve stored them and how you’ve maintained them.
One of the things I miss about being in science is the regular discussions (sometimes heated) about data and experimental results. To be fair, I get some of that when talking about email stuff with Steve. We each have some strong view points and aren’t afraid to share them with each other and with other people. In fact, one of the things we hear most when meeting folks for the first time is, “I love it when you two disagree with each other on that mailing list!” Both of us have engineering and science backgrounds, so we can argue in that vein.
One of the challenges of seemingly contradictory data is figuring out why it seems to disagree. Of course, in science the first step is always to look at your experimental design and data collection. Did I do the experiment right? (Do it again. Always do it again.) Did I record the data correctly? Is the design right? So what did I do differently from what you did? For instance, at one of my labs we discovered that mixing a reagent in plastic tubes created a different outcome from mixing the reagent in glass vials. So many variables that you don’t even think of being variables that affect the outcome of an experiment.