Solving delivery problems


“The only solution to our delivery problems isn’t double opt-in, is it?” A question I get quite frequently from clients and potential clients. In the vast majority of cases the answer is no, confirmed (double) opt-in [1] is not the only solution to delivery problems. In fact, there are delivery issues that confirmed opt-in will do nothing to solve.
Many other delivery sites and deliverability experts will tell clients that the solution to their deliverability problems is to switch to confirmed opt-in as a method to collect email addresses. This overly simplistic solution only treats one possible source of delivery problems, the collection of addresses. It does not address data hygiene issues, technical delivery issues or complaints.
While address collection is important, the best address collection processes on the planet cannot fix sloppy data handling, failure to unsubscribe recipients, or non-existent bounce handling. All of these factors play a role in delivery. It is critical to identify the underlying source of delivery problems before advising anyone on how to fix it.
Over the course of the next few blog posts, I am going to take a look at the various issues that affect delivery: permission, data hygiene, bounce handling, complaints and authentication. I’ll talk about what is important and what senders need to look for and be aware of when they’re trying to troubleshoot delivery issues.
[1] There is some disagreement between senders and anti-spammers about the correct terminology to use. Senders use double opt-in to describe the process, anti-spammers use confirmed opt-in. I am using both terms here to mean the same process.

About the author

Add comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By laura

Recent Posts


Follow Us