Email deliverability starts long before you hit “Send.” It begins with trust — specifically, how receiving email providers recognize and verify your sending domain. To help protect your campaigns and improve overall inbox placement, we’ve introduced mandatory DNS verification before campaigns can be sent.
What prompted this change?
We noticed that campaigns sent from unverified domains often ran into avoidable issues: emails landing in spam, inconsistent delivery, or being blocked entirely. In many cases, this wasn’t due to content quality, but missing or incomplete DNS authentication.
This update closes that gap by ensuring every campaign is sent from a domain that’s properly authenticated.
What’s changed?
When you register a new sending domain, you’ll now be required to:
-
Generate your DNS records
-
Configure SPF and DKIM correctly on your domain
If you attempt to send a campaign without completing this setup, the system will stop the send and display a clear message letting you know your DNS is not yet configured.
Once the records are correctly set up, campaigns will send normally — no extra steps required.
This behavior is consistent across:
-
The plain text editor
-
The template builder
What this means in practice
Before:
A campaign could be sent even if DNS wasn’t set up correctly, risking deliverability issues after the fact.
Now:
Campaigns are only sent when your domain is fully verified, protecting your sender reputation before any emails leave the system.
Why this matters to you
This change helps ensure:
-
Higher inbox placement
-
Better sender reputation
-
Fewer failed or flagged campaigns
-
More predictable campaign performance
If your domains are already configured correctly, you won’t notice any disruption. If not, this update ensures issues are caught early — before they affect your results.
