Monitoring dashboard
Guardrails, lanes, and queue. Sending domains and warmup live under Settings. We pause sending when metrics go out of range.
Sending paused for review
Review metrics below. When ready, resume to allow sending again.
Operational guardrails (last 7 days)
We auto-pause when bounce ≥2% or complaints ≥0.1%. Deferrals are a throttle signal.
Targets: bounce <2%, complaints <0.1%. If out of range, fix list or copy then resume.
Deliverability trend
Run node scripts/monitor/aggregate-events.js (e.g. daily) to append to history. Last 30 points shown.
| Date | Sent | Bounces | Complaints | Bounce % | Complaint % |
|---|
No history yet. Run npm run monitor:report or node scripts/monitor/aggregate-events.js to build history.
Per-recipient-domain lanes (today)
Keep Gmail / Outlook / Yahoo under ~5–20/min each.
Queue
Recent events
| Type | Message ID | Time |
|---|
Testing: Simulate webhook event
Pretend a delivered, bounced, or complaint event happened for an outbox message. Useful to test guardrails and suppression without sending real mail.
Guide: limits, warmup, throttling
Inbox limits – Gmail, Outlook, Yahoo throttle by per-IP and per-domain reputation. Use shards (m1.x.com, m2.x.com) so no single domain looks bursty.
Safe rates: New 20–200/day → Warmed 500–2k/day → Strong 5k–20k/day. Per-recipient: Gmail 5–20/min, Outlook 5–15/min, Yahoo 5–10/min.
Warmup: Day 1: 20–50, Day 7: ~300, Day 30: 3k–5k. We ramp based on the schedule; keep bounce & complaints in range or we pause.
Want to send more? (Scale up)
Campaign sending is limited by each sending domain’s daily cap (and warmup when enabled). To send more:
- Add sending domains – Each domain (e.g. m1.yourbrand.com, m2.yourbrand.com) has its own cap. Add them in Settings; you’ll need a VPS or subdomain and correct DNS for your mail stack.
- Warm them up – Use “Start warmup” so we ramp the cap day by day. Then “Advance day” as you go, or run a daily job to advance.
- Arm sequences with a domain – In Sequences, when you add leads to a sequence, choose a sending domain so the queue stays within that domain's cap.
No code change needed: add the domain in Settings, finish DNS and mail setup for that domain, then use it when arming.