The Deliverability Hub is a dedicated area in lemlist that brings your deliverability insights into one place, across lemwarm (Warm-up), lemlist (Outreach), and now Inbox placements. Instead of switching tools or guessing why performance drops, you can monitor key signals (delivered vs. bounced, bounce trends, inbox/spam signals, sending behavior, and inbox placement results) and set up alerts to catch problems early.
With Inbox placements, you can test and monitor where your emails land instead of guessing whether they reach the inbox. You can now see if messages land in the primary inbox, promotions tab, or spam folder—all centralized inside the Deliverability Hub.
Learning objective
By the end of this tutorial, you’ll know how to navigate the Deliverability Hub, analyze deliverability across Outreach and Warm-up, run inbox placement tests for a sender or campaign step, review placement results by provider, and configure alerts so your team can detect and fix deliverability issues before they impact pipeline.
Why this matters
Deliverability issues rarely happen all at once—they build up gradually. Without a single source of truth, teams often notice problems too late, after reply rates drop. Deliverability Hub helps you spot red flags earlier, understand what’s changing (bounces, spam signals, sending behavior, and inbox placement), and diagnose whether performance drops come from placement problems so you can scale outbound safely across multiple mailboxes and domains.
Prerequisites
You have at least one mailbox connected in lemlist (for Outreach metrics and inbox placement tests).
If you want to use the Warm-up tab, your mailboxes should be connected to lemwarm and actively warming up.
If you want to run an inbox placement test from a campaign step, you should already have a campaign and step available in lemlist.
Availability: Deliverability Hub is included in all plans and is available in the free trial.
What you can do in Inbox placements: View all inbox placement tests in one place, monitor placement trends, create manual inbox placement tests, and diagnose deliverability issues faster.
Core lesson — Step-by-step workflow
Phase 1: Open Deliverability Hub and choose what you want to monitor
Go to Deliverability Hub.
In the left navigation, click Deliverability hub. Then select the area you want to explore:lemlist | Outreach to review delivered vs. bounced performance for your campaigns
lemwarm | Warm-up to review warm-up reputation and inbox/spam signals
Inbox placements to run placement tests and review where emails land
Alerts to configure proactive monitoring
Phase 2: Filter your view to pinpoint the cause (time range, granularity, mailbox, provider, domain)
Set filters before you interpret any metrics.
Use the top filter bar to focus on the right slice of data:Date range (e.g., last 7/14/30 days)
Granularity (Daily/Weekly/Monthly/Yearly)
Mailboxes (single mailbox or multiple)
Providers and domains (to isolate provider-specific or domain-specific issues)
This is the fastest way to confirm whether a deliverability drop is localized (one sender/provider) or systemic (domain-wide). Remember that the sending ceiling is per provider, not per mailbox, so a provider-level view is often the one that explains a drop.
Phase 3: Analyze Outreach deliverability (Delivered vs. bounced, trends, and breakdowns)
Start with the headline Outreach KPIs.
In lemlist | Outreach, use the KPI cards to quickly assess performance in the selected time range:Total email sent
Delivered and delivery rate
Not delivered (Bounced) and bounce rate
Avg daily sent (useful for spotting sending spikes or slowdowns)
Check delivery vs. bounce trends over time.
Use the charts to see whether deliverability issues are getting worse, improving, or spiking on specific days (often a clue for list quality changes, provider throttling, or sending volume changes).Identify which providers are driving the problem.
The Performance by Email Provider table helps you compare performance by sender/recipient provider (e.g., Google → Google vs. Microsoft → Google). If one provider pair shows a much higher bounce rate, prioritize investigation there.Drill down by mailbox to find the sender at risk.
The Outreach Performance by Mailbox table makes it easy to see which mailbox has abnormal bounce rates or reduced delivery rate—ideal for Sales Ops and managers overseeing multiple senders.Review performance by recipient domain.
Use Outreach Performance by Recipient Domain to spot domains that systematically bounce. This can reveal segmentation issues (e.g., a specific target domain set), data quality problems, or domain-specific blocking.
Best practice: When bounce rate rises, first narrow down by mailbox and provider. Fixing one sender’s setup or behavior is often faster (and safer) than changing the entire campaign strategy.
Phase 4: Run inbox placement tests and review where emails land
How often to test: 1 to 2 times per month, no more. Placement varies day to day for reasons outside your control, so one or two reads a month give you a trend while four give you arguments. Testing weekly reports normal variation as a problem, and customers start reacting to noise.
Inbox placement is the recommended reputation signal once campaigns are live. If you will not or cannot run placement tests, keep lemwarm at 10/day as the fallback signal instead. One of the two must always be in place — never neither.
Open Inbox placements and start a new test.
Go to Inbox placements, then click Run inbox placement test. This is where you manually test whether your email lands in the inbox, promotions, or spam.Select the sender first.
In the Run inbox placement test modal, choose the mailbox you want to test in the Sender field. Use a real sender that is actually running campaigns — a clean test from a mailbox nobody sends with proves nothing.Optionally attribute the test to a campaign step.
If you want to test a live sequence or understand placement for a specific message, select a value in Campaign/step attribution. If not, you can leave it empty and run a manual test.Review or write the test content.
Add your Subject and Email content, or let lemlist auto-fill them from the selected campaign step. Test the content you actually send: placement depends heavily on the exact message, so a template nobody uses will not tell you anything useful.Check available credits, then launch the test.
Confirm you have a test credit available, then click Run test. lemlist will send the placement test and start processing results.Wait while the placement test runs.
Once submitted, you’ll see a progress state confirming that the test is in progress. Results are typically ready within a few minutes.Track all inbox placement tests in one table.
Back in Inbox placements, use the results table to monitor all tests in one place. You can review the date, campaign, step, user, mailbox, lead test data, score, and source.Open a test to review detailed placement results by provider.
Click any inbox placement test to open its details. You’ll see overall results plus a provider breakdown showing whether the email landed in the inbox, tabs, spam, or went missing across providers like Google, Microsoft, and SMTP/IMAP.
Why use Inbox placements: If reply rates suddenly drop while bounce rates stay stable, inbox placement testing helps confirm whether your emails are landing in spam or promotions instead of the primary inbox.
Reading the result: if Google and Microsoft look fine but SMTP lands in spam, that points to a content issue rather than infrastructure. Placement tests measure the real email; the warm-up score measures the mailbox. When you have both, placement is the one that decides.
Phase 5: Analyze Warm-up deliverability (lemwarm insights inside lemlist)
Switch to Warm-up to assess reputation signals.
Open lemwarm | Warm-up to monitor warm-up performance without leaving lemlist.Review real-time warm-up health signals.
The top KPI cards give you a quick snapshot of warm-up performance (based on selected filters), including:Deliverability Score
Inbox Rate
Inbox Count
Spam Count
The Deliverability Score is a weighted composite, not a placement percentage — a score of 80 is not an 80% inbox rate. Read the Inbox Rate card for placement, and the score for overall mailbox health. Once campaigns are live, a score below 80 is a reputation problem and below 65 means pause and investigate.
Compare deliverability score trends by mailbox and by domain.
Use these charts to spot whether a deliverability issue is isolated to a single mailbox (sender reputation) or affecting an entire domain (domain reputation/authentication/sending behavior). A score that falls week to week is almost always the spam-rate component — look at content, targeting and volume rather than DNS.Use the mailbox warm-up summary to manage at scale.
The Mailbox Warm-up Summary table provides an operational view per mailbox (average score, inbox/spam counts, daily limit, ramp-up). This is especially useful for Sales Ops teams managing multiple senders — it is where you check that each mailbox's daily limit and ramp-up match its phase: warming mailboxes at their target with a ramp-up of 1, and live mailboxes at a residual 10/day.
Phase 6: Set up Alerts to catch deliverability issues early
Open the Alerts tab and start creating an alert.
Go to Alerts, then click Create an alert in the section you want to monitor (Warm-up or Outreach).Configure the alert type, target, and severity.
In the Email deliverability alerts modal:Select an Alert type (the KPI you want to monitor).
Select the Monitoring target (global, or a specific mailbox/domain depending on the alert type).
Select a Severity level (e.g., Warning or Critical).
Define when the alert should trigger.
Set the threshold logic:Operator (above/below/equal)
Threshold (%)
Period (days) and whether it’s a rolling average or consecutive days
This prevents overreacting to one-day anomalies and helps you track real trends. Alerts are the right tool for continuous monitoring — they are what let you leave placement testing at 1–2 per month without flying blind in between.
Choose how you want to be notified (Email and/or in-app).
Enable Email notifications to alert additional stakeholders (e.g., Sales Ops, managers, agencies), and keep In-app enabled for quick visibility in lemlist.Verify your alerts are active.
Once saved, your alert appears in the corresponding list (Warm-up alerts or Outreach alerts), showing the metric, target, and threshold rules.
Phase 7: Monitor alert logs (what triggered, when, and where)
Review Alert logs to track incidents over time.
Use Alerts logs to see when alerts were triggered and whether they’re active or resolved. This is helpful for reporting, audits, and understanding whether your fixes worked.
Practical application: a deliverability routine (SDR/AE + Sales Ops)
Weekly — dashboard checks
Outreach: Filter to last 7 days → check Bounced KPI and the Delivery & Bounce Rate Over Time chart. If bounce rate spikes, drill down by provider and mailbox.
Warm-up: Check Inbox Rate and Spam Count → if spam increases, review score trends by mailbox vs. domain to decide whether you need a mailbox-level fix or domain-level investigation.
Once or twice a month — inbox placement
Run an inbox placement test for one important sender or one high-volume campaign step, using the content you actually send. If results show spam or promotions placement, review the provider breakdown to see where the problem is concentrated.
Do not put this on a weekly cadence. Placement moves day to day on its own, so a monthly or twice-monthly read gives you a trend you can act on, while weekly testing mostly generates false alarms.
Always-on
Keep alerts enabled for your key KPIs (e.g., spam rate in Warm-up, bounce rate in Outreach) so you don’t have to manually watch dashboards every day.
Keep one reputation signal running per live mailbox: inbox placement 1–2 per month, or lemwarm at 10/day as the fallback. Never neither.
Troubleshooting & common pitfalls
Issue: “I’m seeing a warning that no mailboxes are warming up.”
Root cause: No mailbox is connected to lemwarm, or warm-up isn’t started.
Fix: Connect mailboxes to lemwarm and ensure warm-up is running. Then return to lemwarm | Warm-up and refresh your filters.
Issue: “My inbox placement test shows spam or promotions placement.”
Root cause: The sender reputation, domain reputation, or email content is causing providers to classify the message outside the primary inbox.
Fix:
Open the test details and compare the provider breakdown to see where the issue is concentrated.
If only one provider is affected, investigate provider-specific setup or list quality. Google and Microsoft fine but SMTP in spam usually points to content, not infrastructure.
If multiple providers are affected, review sender reputation, domain health, and message content more broadly, and lower sending volume while you investigate.
Issue: “My placement results keep changing from test to test.”
Root cause: Placement genuinely varies day to day for reasons outside your control. Frequent testing surfaces that variation as if it were a problem.
Fix: Reduce to 1–2 tests per month and read the trend across tests rather than reacting to any single result. Use alerts for continuous monitoring in between.
Issue: “My charts/tables look empty or inconsistent.”
Root cause: Filters are too narrow (date range too short, wrong mailbox/provider selected) or there wasn’t sending activity in that period.
Fix: Expand the date range and select All mailboxes / All providers to validate whether it’s a data issue or a filter issue.
Issue: “I can’t see my inbox placement results yet.”
Root cause: The test is still processing.
Fix:
Wait a few minutes after launching the test.
Return to the Inbox Placement table and refresh the view if needed.
Open the row once the status changes from Pending to a score.
Issue: “Alerts aren’t triggering when I expect them to.”
Root cause: The alert is configured with a rolling window/consecutive-days rule that hasn’t been met yet, or the threshold is set too high/low.
Fix: Recheck Operator, Threshold (%), and Period (days). Consider starting with a Warning severity at a realistic threshold, then tighten it after you observe real traffic patterns.


























