Research has shown that one out of every six marketing emails never reaches the inbox because it is mistakenly blocked by a spam filter.
Surprisingly, the sender—not the email service provider (ESP)—has the greater influence on deliverability.
Even though your email solution provider might have an impeccable reputation, your emails may never reach the inbox if your mailing list or content has issues. No software can solve email content or list problems, period. And even the world's most beautiful email is useless if it is blocked or it lands in the junk folder.
Implement the following 10 tips for minimizing deliverability problems, and then compare your results with pre-implementation metrics. You're sure to see a positive effect on your email program and the conversions it generates.
Add a Comment
Comments
Point 4 (Slide #5): So what was the result? Did newsletter@ or support@ get a better delivery rate?
Great post Maciej! Data hygiene problems are often more complicated than avoiding purchased lists. Consumers often mistype their email address when signing up for a newsletter, and if you are running Cost Per Lead media programs there is potential for Lead Fraud. There are services available for integration directly into your registration form, to validate email addresses in real-time. Consider that "Unknown Users" or dead emails are frequently the biggest cause of deliverability problems.
@Anthony: In this particular case, support@ generated a higher inbox placement, but only because it was used extensively in the past by this Customer and it built up a nice reputation.
When it comes to FROM fields, it's all about using a recognizable address and using it consistently across your mailings. If you swap them frequently, or associate them with emails that generate negative feedback (such as increased spam complaints), you might experience deliverability issues.
@Craig: Thanks for the kind words! That's a good point. The market for the companies you mentioned is growing and it's absolutely justified. Moreover, there's also a matter a data digitalization. If you take a supermarket chain that processes thousands of printed requests filled out by the store visitors, there's always a risk of inputting lots of bad data and typos into the sytem.
I use ConstantContact and have over 100 rejects from an 800+ email blast. Most are due to spam guards at the recipients.
I am contemplating forwarding the email blast from my personal email address to the 100+ rejects in hopes of getting around the anti spam measures.
Any opinions on this approach?
@Lynn: I'm experiencing the same thing with Constant Contact. I have a feeling its because of the rapid expansion of CC and using the same IP for many clients, everyone is being penalized. I'm sure if you ask, they ask if your following best practices. I'm planning to switch to a lesser known service or bring it in house.
I don't think forwarding from your email will be beneficial.
a. All of the tracking info is specific to the contact in CC. You won't be able to tell who opens it, who clicks through, who blocked it, etc. All of that data will be linked to your name. If someone clicks on the unsubscribe link - your email is going to be unsubscribed!
b. It will be a headache managing that secondary list. (removing addresses, updating emails, adding new ones, etc.)
c. You personal email won't like a 800 email blast out of no where. You risk looking like your account was hacked by a spammer and can get your entire domain's email shutdown.
@Lynn: Are your subscribers more in the B2C or B2B sector? It seems to me that it's the second option and in this case your Email Service Provider (ConstantContact) should work with you on an individual basis to solve out these issues.
At GetResponse, this is handled by a dedicated team of deliverability experts who work with spam filters representatives and mailbox providers in order to troubleshoot any delivery issues.
The deliverability from your personal account may vary and be even better, but then again you lose all the feedback, tracking, data, segmentation options, etc. so I think it's a not a way to go here.
@Anthony: Couldn't agree more. Let me know if I can help here.