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

Apple's App Tracking Transparency sealing Meta's fate

If you have been following the recent news on Meta (formerly Facebook) you may have read that Meta recently projected their ad revenue will be cut by a staggering $10 billion in 2022 due to Apple’s new App Tracking Transparency feature (also known as ATT). This has resulted in Meta’s stock to plummet by over 20%. Photo by julien Tromeur on Unsplash - modified by Beolle So what is Apple’s ATT and how does it impact ad revenue? Apple has been releasing multiple privacy features for the last few years. This included Apple’s Mail Privacy Protection and Apple’s App Tracking Transparency feature. You can learn more about Apple’s Mail Privacy Protection in our earlier post by clicking here .  Apple’s App Tracking Transparency (ATT) was launched in iOS 14.5 and iPadOS 14.5 where it prompted users to select if they wanted the app to track their activities across other apps on the device. The prompt is displayed when the user opens an app like Facebook or Instagram for the first time o...

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...

SLA-SLO-SLI and DevOps metrics

Companies are in need of the metrics that will allow them to stay in business by making sure they meet the expectations of their customers. The name of the game is higher customer satisfaction by winning their trust and loyalty. To do so, you want to provide good products and services. Therefore you need to find ways to monitor performance, drive continuous improvements and deliver the quality expected by the consumer in this highly competitive market. Photos from AlphaTradeZone via Pexel and Spacejoy via Unsplash SLAs, SLOs and SLIs are a good way to achieve the above. They allow clients and vendors to be on the same page when it comes to expected system performance. If we go one level deeper, vendors/providers work on NFRs (Non-Functional Requirements) when working on their solutions. NFRs define the quality attributes of a system. I bring them up because the relationship between them and the SLAs is that they provide, in a way, foundational aspects for the SLA-SLO-SL...

SRE, DevOps and ITOps

 If you are wondering what the differences between the SRE and DevOps are, as well as how these roles work with ITOps within an organisation then you are not alone; and best of all you are on the right blog post. Often enough business units in a company get confused, assigning the ServiceNow or Jira tickets or any other ticketing system of your preference, to the wrong group, and even having the incorrect expectations when doing resourcing. Let us go through definitions, insights and scenarios that will help you understand the difference. DevOps software development operations - AI Generated When it comes to DevOps and SRE, then you might be wondering which practice came first. While SRE may have originated a bit earlier, internally at Google, DevOps came first publicly as a practice and started to be used by companies. A few years later was when Google decided to open SRE to the world after the publication of the "Site Reliability Engineering" book. Therefore, technically sp...

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