Skip to main content

Essence of email deliverability - SPF, DKIM, DMARC and segmentation

[PLACEHOLDER]

Recently I attended a lively discussion on email deliverability hosted by Litmus, one of the leading providers of email marketing tools. As email marketers one of the core metrics we often rely on is email deliverability and the discussion was around how to improve the email deliverability in today’s world where our audiences are ever inundated with emails. In addition we often find ourselves operating in a very competitive landscape vying for these audiences' precious attention.

Photo by Ivan Samkov from Pexels
 

Hence it’s becoming increasingly important to ensure our emails are reaching our audiences’ inbox and driving engagement. This is why email clicks and engagement are strong indicators of the performance of our email campaigns instead of just the delivery rate of our campaigns partly thanks to Apple’s Mail Privacy Protection.

So let’s start with the distinction between email delivery and email deliverability. This is very well articulated by Dimiter Batmaziam in the Litmus webinar.

Dimiter describes email delivery as when email is successfully delivered to the receiving entity and a status code of 250 is received. This means that there weren’t any hard or soft bounces and the email was successfully delivered. However he also calls out that this doesn’t mean that the email has reached the recipient’s inbox! The email still has to go through various spam filters before it reaches the recipient inbox. This is where email deliverability comes into play

Email deliverability is when an email reaches the recipient’s inbox after passing through all the spam filters. Consequently email deliverability is always hard to measure as unlike the email delivery the mailbox provider does not share any status codes informing the Email Service Provider (ESP) if the email reached the recipient’s inbox.

This is why measuring email deliverability is not an exact science and relies more on the engagement metrics to identify the success of the email. Consequently it is very important to ensure the essence of email deliverability is embedded in your email marketing practice to ensure your emails reach the recipients inbox and drive engagement. 

There are two (2) facet to ensure email deliverability is high:

  1. Email authentication 
  2. Email segmentation

1. Let’s start with email authentication. There are three (3) pillars to email authentication:

  • SPF  (Sender Policy Framework): SPF allows the receiving entity, Mailbox Providers (MBPs) to verify that the email is received from an IP address which is authorized to send email. This is an authentication protocol that lists the authorized IP addresses in a DNS TXT record that are authorized to send emails on behalf of the email subdomain. 
  • DKIM (Domainkeys Identified Mail): DKIM is a digital signature included in outgoing email which lets the receiving entity verify that the message came from the authenticated sender. 
  •  DMARC (Domain-based Message Authentication, Reporting & Conformance): DMARC helps to specify to the receiving entity what to do if an email from the sender fails SPF or/and DKIM. This prevents unauthorized use of the email subdomain and also helps the sender to monitor all the emails which are using the sender subdomain.

You can learn more about the email authentications by referring to the links at the end of this post.

2. Here’s few things you can do to ensure your segmentation is at par:

  • At a very foundational level this means you send email to your audience with the right content, at the right time at the right frequency. The objective of this is to ensure your emails are relevant to your targeted audiences and result in continued engagement. This in turn fuels email deliverability.
  • You should allow the user to unsubscribe from your emails. This is never preferable however it’s better than allowing the user flagging your email as spam and impacting your deliverability.
  • You should allow the user to inform you which content they want, when they want and at what frequency they want. This can be achieved by providing the user with a preference centre. Then use the provided information to orchestrate your email campaigns.

In conclusion, email deliverability is becoming increasingly important to email marketers. High email deliverability fuels the effectiveness of the email campaigns. Hence getting the basic right will ensure all the hard work which is being put behind a creatively designed and curated email meets its potential. 


References:

Trending posts

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...

Designing Habit Forming Mobile Application

Mobile Applications have become an integral part of our daily lives - we use mobile apps as alarm clocks to wake us up in the morning, to create to do lists when we start our day, to communicate with our colleagues at work via apps like Skype. We even check reviews of restaurants to visit on apps like Yelp and we seek entertainment on apps like Netflix and spotify. So what drives us to use these apps so seamlessly in our daily lives? Why we prefer some apps over others? Is there a science behind designing successful mobile apps like Facebook?  Photo by Peter C from Pexels A study in US revealed that a user between the age of 18 and 44 visits the Facebook app on average 14 times a day [1]. This shows that using the Facebook app is a daily routine for many of its users. This makes Facebook a great example of a habit forming mobile app which is designed with human psychology in mind that encourages habit forming behavior in its users .   I recently attended a seminar ...

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...

Building MCP with TypeScript

MCP servers are popular these days. We’ve been researching and exploring a few code repos, some where missing modularity, others just not having pieces that we were looking for… therefore we decided to build our own, simple and foundational that could be a starting point for those trying to solve for the similar things we were… and we decided to share it with the community, via our public github. MCP host, server,data sources     Before we start.  Using Typescript and NodeJS was one of our requirements. This proved somewhat challenging because I don't code as frequently these days due to my leadership responsibilities, and I typically prefer working with C# or Python. Colleagues in my tech community have been working with their teams on some of their MCPs going the Python route. Therefore, I said, “I guess we are trying the other route” 😊. One of our reasons to go with TypeScript was due to the need of the integration with APIs, and based on the research, it seems t...

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed