Summary
After Klaviyo sending issues, the consensus is to proceed with caution. While some sources indicate the issue is resolved and resending is safe (particularly for important emails, according to some ESP support teams), others advise waiting 48-72 hours due to potential complexities. Monitoring the Klaviyo status page remains crucial. Segmentation, spacing out resends, testing email rendering, and DNS record verification (SPF, DKIM, DMARC) are heavily recommended. Additionally, monitor bounce rates and complaints and prepare for IP warmup if necessary to mitigate deliverability issues and maintain a healthy sending reputation.
Key findings
- Issue Status Discrepancy: Reports on the resolution of Klaviyo issues vary from resolved to intermittently fixed, requiring careful assessment.
- Segmentation Importance: Segmentation of resends is critical to avoid negatively impacting sender reputation.
- Comprehensive Monitoring: Monitoring Klaviyo status, bounce rates, complaints, and sending reputation is essential.
- DNS Verification: Correct DNS records (SPF, DKIM, DMARC) are vital for successful resending.
- Rendering and Testing: Checking the email rendering is crucial.
Key considerations
- Waiting Period: Consider waiting 48-72 hours before resending to ensure a stable fix.
- Potential Complexity: Acknowledge that the Klaviyo fix may have underlying complexities that can affect deliverability.
- IP Warmup: Prepare for IP warmup procedures if sending volume is high after a period of inactivity.
- Complaint Management: Avoid resending to users who previously complained.
- Bounce Assessment: The amount of bounced emails should be assessed and fixed.
What email marketers say
10 marketer opinions
After Klaviyo sending issues, various email marketers and experts suggest different approaches to resending emails. Some ESP support teams indicate it's safe to resend important emails, while others advise caution. Monitoring Klaviyo's status page for updates is a common recommendation. Segmentation of audiences, spacing out resends, monitoring bounce rates, and conducting test sends are highlighted as best practices. Additionally, checking for rendering issues and warming up IP addresses may be necessary depending on the situation.
Key opinions
- ESP Confirmation: Some ESPs indicate it's safe to resend emails.
- Klaviyo Status Page: The Klaviyo status page should be monitored for updates.
- Segmentation: Segmentation is crucial for resending emails to avoid reputation damage.
- Testing: Conduct test sends before large-scale resends.
- Bounce Rates: Monitor bounce rates after resending to adjust strategy.
Key considerations
- Rendering Issues: Check for and fix any rendering issues before resending.
- IP Warmup: Consider IP warmup procedures for high sending volumes.
- Reputation Damage: Resending to everyone without segmentation can harm sender reputation.
- Bounce Monitoring: You will need to monitor bounce rates of the campaigns.
- Official Communications: It's critical to monitor official communications of systems involved.
Marketer view
Email marketer from SendGrid blog recommends following IP warmup procedures if sending volume is high after a period of inactivity caused by Klaviyo issues.
1 Jun 2022 - SendGrid
Marketer view
Email marketer from Email Geeks reports that things went back to normal around 6pm CST.
29 Aug 2023 - Email Geeks
What the experts say
3 expert opinions
Experts advise caution when resending emails after Klaviyo sending issues. One expert suggests waiting 48-72 hours due to potential underlying complexities. Additionally, monitoring sending reputation is crucial, and handling complaints from the initial sending is essential to avoid further issues. Rushing to resend can negatively impact sender reputation, and sending to complainers will exacerbate problems.
Key opinions
- Intermittent Fix: Klaviyo issues may appear fixed but have underlying complexities.
- Reputation Monitoring: Actively monitor sending reputation after issues.
- Complaint Handling: Handling complaints is crucial when resending.
Key considerations
- Waiting Period: Consider a 48-72 hour waiting period before resending.
- Blacklists/Feedback Loops: Check blacklists and feedback loops to assess reputation.
- Complaint Management: Avoid resending to users who previously complained.
Expert view
Expert from Email Geeks shares that the Klaviyo issue appears intermittently fixed but advises waiting 48-72 hours before considering it resolved due to potential underlying complexities.
31 Aug 2024 - Email Geeks
Expert view
Expert from Word to the Wise details that handling complaints from the initial sending is important. Resending to those who complained previously will cause further issues.
6 Oct 2021 - Word to the Wise
What the documentation says
5 technical articles
Documentation sources suggest that while Klaviyo may report the incident as resolved, continuous monitoring is recommended. Ensuring correct DNS records (SPF, DKIM, DMARC) is crucial for deliverability during resends. Testing emails for rendering across different clients and adhering to RFC standards are vital for positive engagement.
Key findings
- Incident Resolution: Klaviyo reports the incident as resolved and systems operational.
- Continued Monitoring: Ongoing monitoring of systems is advised for stability.
- DNS Records: Correct DNS records (SPF, DKIM, DMARC) are essential.
Key considerations
- Email Testing: Thoroughly test emails for rendering across various email clients.
- RFC Standards: Adhere to RFC standards for email protocols.
- System Stability: Only resend once the system is completely fixed.
Technical article
Documentation from StatusGator indicates that users can monitor the systems in question to see any updates regarding resolution of the issues. Once the service posts that it is completely fixed then resending should be ok.
14 May 2024 - StatusGator
Technical article
Documentation from RFC standards dictates the protocols which are used for email. Any resending needs to adhere to these standards to help with the proper sending of the emails.
2 Mar 2024 - RFC Editor
How can I diagnose and fix deliverability issues in Salesforce Marketing Cloud?
How can I diagnose and fix HubSpot email deliverability issues for a large database with cold emails?
How can I diagnose and resolve email deliverability issues when emails aren't reaching intended recipients?
How can I diagnose email deliverability issues when using Constant Contact?
How do I setup a subdomain for email sending with Klaviyo?
How do I troubleshoot delivery errors and TempFail messages in Klaviyo when using Gmail?
