Email Deliverability & Domain Warmup: The Complete Guide

Why does email deliverability matter?

Deliverability decides whether subscribers get the chance to see, click, or buy from a message. When inbox placement falls, every downstream metric becomes harder to interpret. Protecting sender reputation is an operating discipline, not a one-time setup task.

You can write the best emails in the world. If they land in spam, none of it matters.

Problem	Impact
Inbox-placement drop	Fewer opportunities to earn an open, click, or order
Spam folder	Visibility and engagement fall sharply
Blacklisting	Can't reach subscribers
Damaged reputation	Recovery path depends on provider signals, infrastructure, and list quality

The short version

Set up the exact authentication records generated by your platform before marketing sends. For new or materially changed sending infrastructure, begin with engaged recipients, keep high-engagement flows under control, expand in measured cohorts, and stop expanding when complaints, bounces, clicks, conversions, or provider reputation deteriorate. Klaviyo’s current guidance treats the exact schedule as account-specific rather than a universal daily quota.

What determines whether your email lands in the inbox?

Inbox placement is influenced by sender reputation, authentication, audience quality, content, and recipient- and provider-specific signals. There is no universal weighting or fixed threshold that predicts every inbox. Use the factors below as an operating model, then inspect the signals available for your actual provider mix and cohorts.

Sender Reputation

Email Authentication

List Quality

Content

Sender Reputation. Your track record with email providers. You build it over time through consistent, engaged sending.

Email Authentication. SPF, DKIM, and DMARC records that prove you are authorized to send from your domain.

List Quality. Engagement rates, bounce rates, spam complaints. Low engagement means deliverability problems, fast.

Content. Spam trigger words, formatting, HTML quality. This matters less than reputation, but it still matters. If you are already seeing problems here, dig into why your emails land in spam.

How do you set up SPF, DKIM, and DMARC?

Configure authentication before the first marketing send. Use the exact records generated by your sending platform: values vary by account, sending domain, and provider, so generic DNS records should never be pasted into production. SPF authorizes senders, DKIM signs the message, and DMARC defines how receivers handle failed authentication. Follow the verification workflow in our canonical authentication guide, then confirm the sending domain shows as verified inside Klaviyo.

How do you warm up a new sending domain?

Use a conservative, signal-gated operating plan rather than a universal quota. Start with your most engaged audience and expand only while provider signals remain healthy. Large lists should add intermediate volume bands instead of jumping to the full database. A platform-led migration can require a different path because historic engagement, domain history, and infrastructure differ.

New domain, materially changed infrastructure, or a large volume increase? Build and verify a warmup plan before broad sending.

Process

Signal-gated sending-infrastructure warmup

01
Before the first campaignAuthenticate and establish the control plan
Verify the exact platform-generated records, preserve consent and suppression state, and define the engaged cohort and stop conditions.
02
Initial sendsStart with the most engaged recipients
Keep predictable cadence and include essential high-engagement flows in the total volume plan.
03
Each expansionWiden one cohort at a time
Add a less-recent engaged cohort only after delivery, complaints, bounces, clicks, conversions, and provider signals remain healthy.
04
InstabilityPause expansion and diagnose
Reduce exposure to weak cohorts, correct the cause, and resume only when the relevant signals recover.
05
Steady stateMaintain engaged sending
Continue to govern frequency, list hygiene, authentication, and audience quality after the initial ramp.

ZHS operating sequence informed by current Klaviyo warming guidance. It is a decision framework, not a fixed sender-volume promise.

Critical Warning

Do not treat a new or changed sending domain like a fully established one. A sudden expansion can create reputation risk; pause broad sending and follow the platform’s applicable warming or migration guidance when signals weaken.

What metrics should you watch during warmup?

Watch hard bounces, spam complaints, clicks, unsubscribes, conversions, and provider reputation while expanding the audience. Treat opens as a secondary trend, and pause expansion when negative signals deteriorate instead of following a fixed volume schedule blindly.

Use trend changes against comparable sends rather than one universal open or click threshold. Apple Mail Privacy Protection can inflate opens, and a healthy number changes with audience, inbox provider, product, and campaign purpose. Keep the spam-complaint operating standard separate, investigate material bounce changes, and slow expansion when signals deteriorate together.

Metric	What to compare	What should trigger investigation
Delivery and bounces	Same domain, provider, cohort, and send type	A material deterioration from the recent baseline
Complaints	Delivered-message denominator and trend	Approaching the canonical operating ceiling or a sudden spike
Clicks and conversions	Comparable audience and message job	Weakening response while audience volume expands
Opens	Directional trend only	A change that agrees with stronger signals, not a standalone verdict

How do you maintain sender reputation over time?

Maintain sender reputation with list hygiene, engagement management, and clear message construction. Let the platform suppress hard bounces, move persistently unengaged profiles through a defined sunset policy, make unsubscribe easy, and investigate complaint spikes. Use accessible live text, a consistent From name, and honest subject lines.

List Hygiene:

Confirm hard bounces are automatically suppressed by the ESP
Run inactive profiles through the sunset flow, then suppress rather than delete
Verify any imported list before you import it

Engagement Management:

Segment by engagement level
Make the unsubscribe easy to find
Use the canonical complaint-rate operating target above and investigate adverse trends before broadening sends
Send content people actually want

Content:

Skip spam triggers like "FREE!!!" and excessive caps
Keep a healthy text-to-image ratio

Apple Mail Privacy Protection changes the signal

Apple can preload tracking pixels, which makes opens less reliable for some recipients. Use clicks, purchases, recent site activity, and provider-level delivery signals alongside opens when expanding warmup audiences or defining engagement tiers.

Should automated flows run during warmup?

Keep essential, behavior-triggered flows live when they use the authenticated sending domain and target people who just opted in or took a high-intent action. Their audience is naturally engaged, but their volume still counts. Include projected flow volume in the daily plan, monitor it separately from campaigns, and pause nonessential reactivation or broad backfill automations until reputation is stable.

For a migration, authenticate and test the new account first, preserve suppression and consent state, and avoid switching every campaign and historical automation on at once. Use the Mailchimp-to-Klaviyo migration runbook for the full sequence.

Include a plain text version
Keep one consistent "From" name

How do you recover from a spam folder problem?

Recovery duration is account-specific. First stop the behavior causing the decline and send only to a trustworthy recent-engagement cohort. Then reconcile invalid addresses, route dormant profiles through the canonical sunset policy, and suppress persistent inactivity rather than deleting profiles. Re-expand only when provider, click, conversion, bounce, and complaint signals support it.

Already in spam? Here is the plan.

Contain the issue. Pause broad expansion, identify the affected provider or cohort, and keep only the highest-confidence essential messaging running where appropriate.

Repair the audience and infrastructure. Confirm authentication, preserve suppression state, investigate invalid-address and consent problems, and route 90+ day dormant profiles through the canonical reactivation/sunset policy.

Reintroduce deliberately. Resume with a recent-engagement cohort, expand one cohort at a time, and use stronger signals than opens alone to decide whether to continue.

Keep monitoring. Use provider tools, platform reporting, and a documented change log so a future decline can be tied to a measurable change rather than guesswork.

What tools should you use to monitor deliverability?

Use a provider-reputation surface, your ESP analytics, and DNS/blacklist diagnostics together. Google Postmaster Tools can surface Gmail-domain signals when its reporting is available. Your ESP can centralize send, bounce, complaint, click, and conversion data. A DNS and blacklist diagnostic can help verify records and surface infrastructure issues. During warmup or recovery, ZHS reviews the relevant signals before each planned expansion; steady-state monitoring cadence should match sending volume and risk. Build the wider operating practice in monitoring your deliverability.

Google Postmaster Tools. Review the Gmail-domain signals that are available for your verified domain.

Your ESP Analytics. Compare delivery, bounces, complaints, clicks, conversions, and audience cohorts under consistent definitions.

DNS and blacklist diagnostics. Check authentication records and investigate an infrastructure signal; treat a result as a diagnostic, not proof of inbox placement.

Should you use a branded or shared sending domain?

Klaviyo accounts can use platform-shared infrastructure or a branded sending domain. A branded domain aligns the visible sending identity with the brand and lets the platform verify the account-specific authentication setup; it is not the same thing as a dedicated IP, and it does not guarantee inbox placement. The right choice depends on current platform eligibility, sending pattern, authentication needs, migration state, and provider guidance, not one monthly-volume threshold. Use the platform’s current setup workflow and confirm the record set it generates for your account.

Platform-shared sending domain

Platform-managed shared infrastructure
Easier to set up
Infrastructure and eligibility are governed by the platform
May suit accounts whose current platform setup does not require a branded domain

Branded sending domain

Aligns the visible sender identity with your brand
Uses account-specific authentication records from the platform
May require an account-specific warming or migration plan
More technical to set up
Useful when brand identity, domain alignment, or infrastructure control warrants it

Checklist

One-Time Setup:

Ongoing:

Review provider, delivery, complaint, bounce, click, and conversion signals before each warmup expansion
Set a documented steady-state monitoring cadence that matches sending volume and risk
Reassess dormant-profile policy when acquisition, product cycle, or deliverability signals change
Recheck authentication and infrastructure diagnostics after domain, provider, or platform changes

Get Expert Help

Deliverability problems cost you real revenue, every send. Our team diagnoses and fixes them as part of our retention work.

See our pricing | Apply to work with us