Why are my Klaviyo preview emails not showing up in my inbox?
Updated on 6 Oct 2026: We clarified how to send Klaviyo test emails and trace missing previews.
If your Klaviyo preview email is not in the inbox, Promotions tab, spam, Trash, or any other folder, first confirm that you sent a test email, then check the account's preview email limit and the exact recipient address. If those checks pass, determine whether Klaviyo generated and handed off the message or the receiving system filtered it before it reached a visible folder.
Separate two questions: did Klaviyo have preview allowance available and hand off a test email, and did the receiving side accept it into a mailbox? The Klaviyo preview guide explains the preview path and account limits, but an in-app success message does not prove that your corporate gateway, Microsoft tenant, Google Workspace rules, or mailbox provider placed the email in a visible folder.
Fast answer
Check for an exhausted preview allowance, a recipient mistake, a test email that Klaviyo did not hand off, or destination-side filtering. Opening the visual preview alone does not send an email. Check those causes before changing DNS or rebuilding the template.
- First check: Confirm the account has preview sends left in the current billing cycle.
- Best comparison: Send the same preview to a second mailbox on a different provider.
- Escalation point: If allowance remains and no destination receives it, ask Klaviyo support to confirm the message ID, sender, and handoff result.
Why Klaviyo preview emails go missing
A Klaviyo preview send is only one part of the delivery path. The account must have preview allowance available. Klaviyo then has to render and create the message, apply the sender settings and authentication, and attempt delivery to the receiving system. The recipient side evaluates authentication, reputation, content, internal policy, and mailbox rules. Failure at any of those points creates the same symptom: no message in the inbox.
Klaviyo side
- Preview limit: The account has used its preview allowance for the billing cycle.
- Wrong recipient: The preview was sent to an address you did not intend to test.
- Preview context: The selected profile or event does not contain the data needed to render the expected content. Check this when the preview content is blank or incorrect.
- Template error: A broken block, invalid personalization tag, or unsupported content prevents the preview from rendering correctly.
Recipient side
- Gateway block: A corporate email filter accepts the message and holds it outside the mailbox.
- SMTP rejection: A mailbox provider rejects the test before placing it in spam.
- Reputation block: A sending IP, domain, link domain, or shared asset has poor reputation.
- User rules: Mailbox filters, forwarding rules, or quarantine policies move it before you see it.
This is why a Klaviyo community case about a missing test email can look simple at first and still need message-path evidence. The user sees nothing, but the cause can be an account limit or a failure between Klaviyo and the final mailbox.
Klaviyo Preview and test panel with recipient and profile fields.
Find the test email option in Klaviyo
The visual preview and the test email are separate actions. Klaviyo's preview controls depend on whether you are editing a saved template, a campaign email, or an individual flow email.
- Open the campaign email or individual flow email, then enter its email editor.
- Open Preview or Preview & test, depending on the editor view.
- Choose the profile or event used to populate personalization. This choice supplies preview data; it is separate from the test recipient address.
- Use the test email action, such as Send test, enter the destination address, and confirm the send.
If the send option is missing, record which editor view you are using and check the Klaviyo preview guide or flow testing instructions. A missing button or blank editor needs an editor check before an inbox delivery investigation.
Check the preview email limit
Klaviyo applies a preview email limit per account and billing cycle. This allowance is separate from the maximum of 30 recipients that you can enter for one preview. Check Billing under Profiles + email to confirm the plan size, then compare it with the limits in the Klaviyo preview guide. The allowance is shared across account users. If preview usage is not visible in your account, ask Klaviyo support to confirm it.
|
|
|---|---|
0-250 contacts on free plan | 100 preview emails |
251-500 contacts | 500 preview emails |
501 or more contacts | One-tenth of plan sending capacity |
Klaviyo preview limits per billing cycle.
Preview send or live test
The Send test action in the editor uses the preview allowance. A live campaign sent to a small preview list follows campaign rules instead, so suppressed recipients, Smart Sending, skips, and bounces can affect delivery. For a live test, inspect campaign analytics and Recipient Activity before treating the problem as a preview failure.
For a live flow test, also check the message's Live status, trigger qualification, time delays, Smart Sending, and flow or trigger filters. Inspect Recipient Activity for skips and bounces. The Klaviyo flow troubleshooting discussion covers automation causes; these are separate from delivery of an editor test email.
Troubleshoot missing Klaviyo test emails
The fastest path avoids guessing from the inbox alone. A blank inbox does not prove that Klaviyo failed to send. It proves that your mailbox did not show the message. Use this sequence to isolate the account allowance, Klaviyo handoff, destination mailbox, and domain setup.
- Check preview allowance: Confirm the account has not reached its preview email limit for the billing cycle.
- Confirm the address: Copy the exact preview recipient, including aliases, plus-addressing, and spelling.
- Search everywhere: Search all mail folders by the exact subject and sender address. Check Promotions, spam, Trash, and archive folders, then review mailbox rules.
- Change destination: Send the same preview to a personal mailbox and a work mailbox.
- Check preview data: Choose a profile with the required profile fields, or the matching trigger event for event-based content.
- Reduce content: Duplicate the template, remove complex dynamic blocks, and send a simple version with realistic subject text and content.
- Ask for logs: If allowance remains and no test destination receives it, ask Klaviyo support for message evidence.
|
|
|
|---|---|---|
No mailbox receives it | Preview limit, send issue, or filtering | Check the test action and allowance, then request a trace |
Only work mailbox misses it | Gateway quarantine or mailbox rules | Check admin quarantine and recipient rules |
Only Microsoft 365 misses it | Tenant filtering or rejection | Ask IT for a message trace and quarantine search |
Tester receives it | A different outcome at the original destination | Trace the send to the original recipient |
Authentication fails | Sender configuration or domain mismatch | Inspect received headers and the account DNS records |
Use the symptom to choose the next check.
If the missing previews are specific to Microsoft mailboxes, the workflow is similar to Outlook test delivery: prove the message exists, compare receiving providers, then inspect authentication and filtering.
Compare delivery across test inboxes
One inbox is not enough evidence. Send the same Klaviyo preview to a controlled testing address to see whether that copy arrives and inspect its received headers. Suped's email tester provides authentication results and content checks for the copy it receives.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
If the tester receives the preview but your normal mailbox does not, Klaviyo delivered the tester's copy. Request a trace for the separate send to your normal address and check quarantine, tenant policy, mailbox rules, or provider filtering. If neither destination receives it after you confirm the test action and preview allowance, ask Klaviyo support to trace both attempts.
If the test recipient is also the From or Reply-To address, try a different mailbox. Klaviyo documents this self-addressed pattern as a cause of Gmail spam placement in its preview spam guidance. Use realistic test content and mark a legitimate preview as not spam when you find it there.
Do not stop at one inbox
A company inbox can hide a message before spam filtering is visible to the user. Admin quarantine, URL scanning, data loss rules, and inbound allow or deny lists can all prevent a preview from appearing anywhere in the mailbox interface.
How to read the test result
Use the destination pattern to choose a follow-up check, rather than assign a delivery risk score.
All destinations receive
Mailbox checks
Review where the messages landed and whether delays or mailbox rules explain the original search.
Some destinations receive
Recipient trace
Trace the separate send to the missing destination and check its filtering rules.
No destination receives
Send trace
Confirm the test action and preview allowance, then ask Klaviyo to trace the attempts.
Check authentication and sender setup
Authentication failures increase the chance of filtering. Check that the branded sending domain Klaviyo uses is verified and active and has the exact DNS records shown in your account. Inspect SPF, DKIM, and DMARC results in a received copy. Suped's domain health checker checks published records, while ongoing DMARC monitoring shows authentication patterns reported by participating receivers.
Illustrative received headers, not DNS recordstext
From: Brand <news@example.com> Authentication-Results: mx.receiver.example; spf=pass smtp.mailfrom=return.example.net; dkim=pass header.d=example.com; dmarc=pass header.from=example.com
In this illustrative example, SPF passes for a different domain, while DKIM passes for the visible From domain, so DKIM supports the DMARC pass. DMARC needs one passing mechanism with the required domain relationship: the same organizational domain in relaxed mode, or an exact match in strict mode. The DMARC domain matching rules define that distinction. Passing authentication does not guarantee inbox placement.
Use the DNS values shown in your Klaviyo account instead of copying generic SPF includes or DKIM selectors. Klaviyo normally manages SPF through its Return-Path domain, so adding a root-domain SPF record is not a routine fix for missing previews. Follow Klaviyo DNS guidance for your sending setup.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
A missing List-ID header does not establish why a preview is missing. List-ID identifies a mailing list for mailbox clients; it is separate from sender authentication. Prioritize preview allowance, send evidence, recipient filtering, authentication, and reputation before treating that warning as the cause.
Look for gateway and reputation blocks
If a personal mailbox receives the preview but your company mailbox does not, treat the corporate mail system as the prime suspect. Many companies run inbound filtering that quarantines marketing-style test messages before they hit the user-visible spam folder. Your IT team can search quarantine by sender, recipient, subject, timestamp, message ID, and sending IP.
Reputation also matters. If a sending IP, link domain, image host, or branded sending domain has a poor signal, some gateways will drop or hold a preview. Suped's blocklist monitoring checks domain and IP listings on blocklists (blacklists). Compare a listing with the receiving system's rejection or quarantine reason; a blacklist listing does not establish why this preview was blocked, and a clear result does not guarantee delivery.
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Ask IT to review the full message path, including the Klaviyo sending domain, return-path domain, tracking domain, source IP, URLs in the message, and the quarantine or rejection reason. Use that evidence to fix the specific rule affecting a legitimate preview, rather than assuming that allowing the visible From address resolves the problem.
Klaviyo preview email troubleshooting flowchart covering mailbox checks, authentication, and quarantine.
Check content and recipient data
Missing profile or event data usually causes blank or incorrect personalized content, an empty dynamic block, or an error in the in-app preview. It does not by itself prove that a message disappeared in transit. For an event-triggered flow email, choose an event instance that contains the properties used by the template.
- Profile data: Select a profile with the required profile fields. For event-based personalization, choose the matching trigger event and an instance with the required properties.
- Dynamic blocks: Temporarily remove product feeds, conditional logic, and custom code blocks.
- Subject line: Use a unique subject so mailbox search can find the exact preview.
- Link domains: Check whether branded links and image URLs match your expected sending setup.
If imported HTML is missing in the campaign editor, compare it with the saved template and restore missing code in a duplicate before retesting. The missing-code community report describes this editor symptom; it is a different check from tracing an email that was sent but never arrived.
Blank is different from missing
If the email arrives blank, debug template rendering first. If it does not arrive anywhere, debug preview allowance, sending evidence, mailbox filtering, authentication, and reputation first.
Preview sends are insufficient for validating live unsubscribe or preference links and dynamic coupon generation. Use a live campaign to a small internal list for campaign behavior. To test event details in a metric-triggered flow, perform the matching trigger action with a test profile; a campaign send does not reproduce that flow's event context. The Klaviyo preview guide explains the live-test distinction.
What to send support or IT
A useful support request gives Klaviyo or IT enough detail to search logs. Include the Klaviyo account ID, timestamps with timezone, the exact recipient, sender, template name, subject, preview allowance status, and whether other destinations received the preview.
Support packettext
Platform: Klaviyo Klaviyo account ID: [ID] Template, campaign, or flow: [name and ID] Test type: [Send test preview, live campaign, or triggered flow] Editor action and status: [button used and exact confirmation or error] Preview sent at: [date, time, timezone] Preview recipient: [address] From address: [address] Subject: [exact subject] Preview allowance: [available, reached, or not confirmed] Other test recipients: [received or missing, with attempt times] Tester result: [received or missing] Authentication result: [SPF, DKIM, DMARC from a received copy] Message ID: [if available] Question: Was this recipient's message generated, queued, rejected, or accepted? Question: What was the receiving server's SMTP response and the sending route?
Best escalation path
If Klaviyo confirms that the receiving server accepted the message for the missing recipient, give the mailbox admin its message ID and timestamp for a trace. Server acceptance does not prove inbox placement. If it remains queued or was rejected, ask Klaviyo for the delivery status, exact SMTP response, and sending route before treating it as a mailbox rule problem.
Use Suped to collect authentication evidence
Suped's DMARC reporting and email authentication platform collects authentication evidence and blocklist (blacklist) status for your domains and sending IPs. For a missing Klaviyo preview, use it alongside Klaviyo's recipient-specific send logs and the receiving system's message trace.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
- Review the received test copy in Suped's email tester for SPF, DKIM, and DMARC results, then compare them with the account's sending-domain setup.
- Use Suped's DMARC reports to check whether Klaviyo traffic has a wider authentication problem. Report-based alerts depend on reports arriving from receivers.
- Check the sending IP and relevant domains in Suped's blocklist monitoring, then compare any blacklist listing with the gateway's stated reason.
- Use Suped's issue diagnostics to document a specific authentication fix and attach the evidence to the Klaviyo or IT support request.
DMARC aggregate reports normally cover a daily reporting period. They summarize authentication rather than track a preview by recipient or message ID, and they do not establish inbox placement. The aggregate reporting standard describes those reports. Use received headers and delivery logs when you need evidence for an individual preview immediately.
Views from the trenches
Best practices
Check the account's preview allowance before changing sender DNS or rebuilding template code.
Save timestamps, recipients, subjects, and sender details before asking support to trace.
Treat admin quarantine as separate from spam, because mailbox users cannot always see it.
Common pitfalls
Assuming no inbox copy means Klaviyo failed to send, without checking account limits.
Chasing minor header warnings before proving whether the message reached any mailbox.
Allowing only the visible From address while the gateway blocks links or return paths.
Expert tips
A neutral test mailbox gives stronger evidence than repeated sends to the same inbox.
DMARC pass rates help show whether missing previews are part of a wider sender issue.
Ask for SMTP evidence and message IDs so support teams can search exact log entries.
Marketer view
Marketer from Email Geeks says a missing preview should be tested at another destination before assuming Klaviyo failed to send it.
2024-04-05 - Email Geeks
Marketer view
Marketer from Email Geeks says minor report warnings such as list header findings rarely explain a complete absence from every folder.
2024-04-05 - Email Geeks
