Overview
Use this email deliverability report playbook when you need a week-on-week read on inbox risk before the next campaign goes out. Juno reviews connected email platform data, compares the latest completed week with the prior week, and turns the mess into a tracker and concise report.
It is built for marketers running campaigns, newsletters, lifecycle flows, automations, or transactional sends through platforms such as Klaviyo or HubSpot. The output helps you see which campaigns, segments, domains, or sending streams are healthy, which need watching, and which deserve action now.
The report focuses on the signals that usually matter most for sender reputation: bounces, hard bounces, soft bounces, spam complaints, unsubscribes, delivery evidence, and engagement movement where it explains the risk.
Why you should catch inbox risk before the next send
Deliverability problems rarely arrive with a polite calendar invite. A complaint spike, broad bounce-rate shift, or suspicious suppression gap can sit inside platform reporting until someone notices it after performance has already softened.
A weekly deliverability tracker gives the team a shared view before the next send adds more noise. It keeps date windows consistent, labels missing or low-volume data clearly, and ranks urgent risks ahead of general engagement commentary.
That discipline matters because mailbox providers keep raising the bar for commercial senders. Google's email sender guidelines emphasize authentication, low spam rates, and easy unsubscribes for senders reaching Gmail users, while also warning that bounces and deferrals should prompt reduced sending volume.
Juno helps by turning platform metrics into practical decisions. Instead of another dashboard scavenger hunt, you get the top risks, likely causes, confidence notes, and next actions your team can review before planning the next campaign.
Step-by-step
- 1Confirm the reporting scope, including the brand, email platform, account, market, reporting week, comparison week, streams to include, and any priority audiences, domains, campaigns, or segments.
- 2Reuse the right surface when a deliverability tracker or weekly email report already exists, then add the newest completed week so history stays comparable.
- 3Pull the highest-signal metrics for meaningful send volume, including sent volume, delivered volume when available, bounces, hard bounces, soft bounces, spam complaints, unsubscribes, opens, clicks, and relevant campaign or flow labels.
- 4Normalize the rates before comparing movement, calculating percentages from available counts when needed and marking unavailable metrics as missing instead of guessing.
- 5Rank the inbox risks by deliverability impact first, then use campaign context, list source, segment, send type, and engagement movement to explain likely causes without overcalling tiny samples.
- 6Produce a tracker and short weekly report with status labels, confidence notes, caveats, week-on-week movement, urgent issues, watch items, healthy high-volume sends, and recommended next actions.
Frequently asked questions
What inputs should I have ready?
Bring the email platform, account, reporting week, comparison week, sending streams, priority segments, and any context that could explain movement, such as list imports, suppression changes, domain updates, promotions, or platform issues.
Which metrics does the report prioritize?
It leads with bounce, hard bounce, soft bounce, spam complaint, unsubscribe, suppression, and delivery signals. Opens and clicks are included when they help explain risk, but open rates are treated as directional rather than perfect truth.
Can Juno run this if some data is missing?
Yes. Juno continues with the available evidence and labels missing, delayed, low-volume, or non-comparable data clearly. It should not estimate deliverability metrics that the platform did not provide.
How often should I run it?
Run it weekly after the prior full week has closed and the email platform has had time to settle. Monday or Tuesday morning is usually the cleanest default for a recurring deliverability review.
