To improve the deliverability of your email marketing campaigns, Campaign Connex always automatically authenticates your campaign with DKIM. This type of authentication is crucial to ensuring deliverability, as it is known as a sender identification tool, designed to protects bulk email senders and their recipients from spam, forgery, and phishing.
Why Authentication Matters
Authentication is crucial to ensuring the delivery of your campaign, by providing a trackable ID that will demonstrate to your subscribers’ email service provider that you are a legitimate sender, not a spammer. This therefore helps to ensure that your campaign will arrive in the inbox as planned, rather than being diverted to junk or spam boxes.
There are two important types of authentication to consider when sending mass marketing email campaigns: DomainKeys Identified Mail (DKIM) and Sender Policy Framework (SPF). Campaign Connex provides DKIM for all our users’ accounts, giving everyone the same access to a range of benefits. We do however also provide the option for you to do this for yourself, which can have even more benefits, depending on the type of campaigns you are running.
Benefits of Campaign Connex’s Default Authentication
- You automatically get DKIM authentication on all your campaigns.
- Since our authentication is enabled by default, you will not have to edit any advanced settings like DNS records, it’s all already set up out of the box.
- As you will have this authentication added to your emails, it will ensure higher deliverability of your campaigns
- Our sending domains are pre-warmed, meaning that they will deliver to inboxes quicker and more easily than a newly authenticated sending domain.
The downside of using our standard authentication options however, is that your “from email address” will be changed to reflect our sending domain, and you will be unable to use your own domain in the from address.
So if you are email@example.com, you will be given the choice as to whether your email will be delivered as firstname.lastname@example.org or email@example.com as firstname.lastname@example.org will not be a viable option for you, using default authentication.
Depending on the provider, will depend on whether your edited “from email address” is likely to be seen – for example in Apple Mail screenshot outlined below, the subscriber would need to look for the “from email address”, seeing only the from name, and reply-to email address as standard. In contrast, it will be shown clearly if the campaign is received in Gmail, as outlined below.
Apple Mail View:
Gmail View (Same Campaign):
It’s not possible to turn off this default authentication. However, you can set up your own authentication instead, which provides some additional deliverability benefits, as well as allowing you to use any ”from email address” from an authenticated domain as you want.
Setting up Your Own Custom Domain Authentication
If you want to use your own email domain for sending, this is perfectly possible, but you will have to verify it first, so that we can be sure you own the domain and are not attempting to use apple.com for example, in order to spam people.
To that end we’ve made it easy to verify your domain, by simply having an email sent to either your abuse@ or postmaster@ email accounts with a link to click that will verify your ownership of that domain.
We’ve also however included the option to set up your own DKIM authentication via your DNS records, which will add additional deliverability benefits for your account and make it easier for your campaigns to hit inboxes and avoid spam filters. For step-by-step instructions on this, Click here
Where possible we recommend doing both the email route for authentication, and the DNS route, in order to maximize your chances of securing the results you’re looking for from your email campaigns. Once you have authenticated your domain you’ll be permitted to display your domain’s information in your email header (from email address), which will also help to make your campaigns look more professional.
Benefits of Opting for Custom Domain Authentication
- It allows you to use any “from email address” associated with an authenticated domain to send your campaigns
- It removes the default Campaign Connex authentication information that can show up next to your campaign’s From name in certain email clients.*
- It causes email clients like Gmail to automatically load your emails’ images, rather than asking your subscribers to allow them every time.
- It can help your campaigns arrive in subscriber inboxes more easily, rather than sending them to spam or junk folders.
- It gives your subscribers and your email service provider more faith that you intend to treat your audience with respect and not spam them.
*While this is the case for most email clients, some email clients, like Outlook, may still display the authentication information even after custom DKIM is set up. This is specific to each email client though and isn’t something we can prevent.
Do I need custom domain authentication?
Before you decide whether to continue using our default authentication, or start working on trying to setup your own custom domain settings, just review these quick questions to see if custom domain authentication is the right approach for your email marketing needs:
- Is your “From email address” associated with your own email domain, rather than someone else’s, or a public webmail address like gmail.com or hotmail.com?
- Do you have access to your company’s abuse@ or postmaster@ email accounts?
- Are you or your IT team able to access your domain’s cPanel or Zone editor to edit DNS records?
- Do some email clients automatically block images in your campaigns?
- Do your delivered campaigns show a default Campaign Connex “from email address” in the sender details section? Do you want to change this?
If you answered yes to all or most of these questions, then it seems like custom domain authentication could be a good fit for you. If you answered no to most of these questions, then it’s probably better for you to keep using the default authentication that’s already set up on your account.
If you answered yes and are now looking at custom domain authentication seriously, the only question left then, is whether to go for the easy route by sending emails to abuse@ and / or postmaster@ for verification, or going the whole way with DKIM and authentication to give your emails their best shot of reaching your audience.
(For a step-by-step guide on DKIM and SPF authentication click here Click here)