Lifecycle Retention · Deliverability
Authentication, sender reputation and list hygiene, set up correctly and monitored every week, so your flows and campaigns land in the inbox instead of spam.
Why it matters
If messages land in spam, nothing else on the email side matters: not the copy, not the segmentation, not the offer. Deliverability problems rarely announce themselves. Revenue per send drifts down, engagement looks a little weaker, and the cause sits in a DNS record, a sending habit or a list that hasn't been cleaned. We treat inbox placement as infrastructure: configured once, checked every week.
Authentication, explained
| Record | What it does | What we check |
|---|---|---|
| SPF | Lists the servers allowed to send mail for your domain | Your ESP and other senders are included, with no duplicate records and no lookups over the limit |
| DKIM | Signs each message with a key published in your DNS | Signing with your own domain, not only the ESP's shared domain |
| DMARC | Tells mailbox providers what to do when SPF or DKIM fails, and sends you reports | A published policy, reporting address, and a plan to move from p=none toward enforcement |
| Alignment | Checks that the domain in your From address matches the SPF or DKIM domain | A branded sending domain set up in Klaviyo or your ESP so DMARC passes on alignment |
| Reverse DNS and TLS | Confirms the sending IP and encrypts mail in transit | Usually handled by your ESP; verified, not assumed |
Mailbox provider rules
Since February 2024, Gmail and Yahoo have enforced stricter requirements for bulk senders. Google defines a bulk sender as one that sends close to 5,000 or more messages a day to personal Gmail accounts, and many growing eCommerce brands cross that line on campaign days. The core requirements:
Microsoft introduced similar authentication requirements for high-volume senders to Outlook.com, Hotmail and Live addresses in 2025. The full rules are in Google's email sender guidelines. U.S. law adds CAN-SPAM basics: a working unsubscribe honored within 10 business days, a valid physical postal address and no deceptive headers or subject lines. We implement these technically; confirm compliance with counsel.
Reputation and list hygiene
Recently engaged subscribers get most campaigns. Less engaged ones get fewer, better-targeted sends.
Long-unengaged contacts get a short re-engagement path, then stop receiving campaigns. A smaller list that reads beats a large one that doesn't.
No purchased or scraped lists, confirmed opt-in where it makes sense and bot protection on signup forms, which keep spam traps and fake sign-ups out.
Hard bounces suppressed automatically; complaint spikes traced to the segment, message or source that caused them.
A new domain, IP or ESP starts with your most engaged subscribers and grows volume gradually, before full-list campaigns.
Apple Mail Privacy Protection inflates opens, so we define engagement with clicks, site activity and orders too.
How we work
DNS records, alignment, sending domains, list sources, engagement tiers, bounce and complaint history, and Google Postmaster Tools data.
SPF, DKIM and DMARC corrected with your IT or domain admin, and a branded sending domain set up in your ESP.
Engagement tiers built as live segments, so every campaign in the calendar respects them.
A volume plan for new domains, IPs or a platform move, adjusted daily from placement and complaint data.
Spam rate, bounce rate, domain reputation and DMARC reports reviewed weekly, with alerts on anything that moves.
Where placement shows up in revenue
When placement slips, revenue per subscriber is usually the first business number to fall. Check yours with the free Revenue per Subscriber Calculator. Deliverability also depends on what you send: lighter, live-text templates and well-targeted flows earn the engagement that keeps a sender's reputation strong.
FAQ
An audit of your authentication (SPF, DKIM, DMARC and alignment), sending domains, list sources, engagement and complaint data, followed by fixes and ongoing monitoring. That means correcting DNS records, setting up a branded sending domain, building engagement-based segments and sunset policies, planning warm-up when needed and reviewing spam rate and domain reputation every week.
The usual causes are missing or misaligned authentication, a spam complaint rate that's too high, sending to unengaged or old contacts, a sudden jump in volume, or list sources that bring in fake or trap addresses. Content plays a smaller role than most people think. We start with the technical setup and the data in Google Postmaster Tools, then look at sending habits.
DMARC passes only when the domain in your visible From address matches the domain that passed SPF or DKIM. If your ESP signs with its own domain while you send from yourbrand.com, authentication can pass while alignment fails. A branded sending domain in your ESP fixes that, and it's one of the Gmail and Yahoo bulk sender requirements.
Most brands don't. Shared IPs at a good ESP are managed for reputation, and a dedicated IP needs steady, high volume to build and keep its own. Your domain reputation matters more for most senders. We recommend a dedicated IP only when your volume and consistency justify it, and plan a careful warm-up if you move.
Start with your most engaged subscribers and recent buyers, send at modest volume and increase gradually while watching bounces, complaints and placement. Flows can usually move first, then campaigns expand from engaged segments outward. The pace depends on your list size and results, so we adjust daily during the warm-up rather than following a fixed schedule. See our Klaviyo review for platform specifics.
The Free Profit Audit flags deliverability risks alongside flow and signup gaps, with a prioritized plan. Or book a call to review your setup with a strategist.