Campaign Monitor deliverability: the checks that catch problems early

Campaign Monitor deliverability problems are rarely visible in the metrics the dashboard surfaces first - open rate and click rate lag behind the actual cause by days or weeks. Catching problems early means checking authentication, reputation, and engagement directly rather than waiting for the campaign report to look bad.

Authentication: the first and most common gap

Campaign Monitor's domain authentication setup generates SPF and DKIM records specific to your account. Copy the exact values from your Campaign Monitor settings screen at setup time - the DKIM selector and any return-path hostname are account-specific and should not be assumed from documentation or a colleague's setup. Verify independently:

dig TXT yourdomain.com +short
dig TXT _dmarc.yourdomain.com +short

A domain with only SPF and no DKIM, or DKIM configured but not yet selected as active in Campaign Monitor's sending settings, will authenticate inconsistently - which some providers tolerate and others, particularly Gmail and Yahoo under their current bulk-sender requirements, do not.

IP reputation: shared vs. dedicated

Campaign Monitor's standard infrastructure uses shared sending IPs for most accounts. Shared IP reputation is a pooled resource - your placement can move because of another sender's behaviour, not just your own. If you are sending at high enough volume that a dedicated IP becomes available on your plan, know that a dedicated IP needs its own warm-up ramp; it does not inherit the shared pool's reputation, good or bad.

Engagement metrics that predict placement before it drops

Spam complaint rate deserves the closest watch of these. Google has published roughly 0.3% as the threshold above which bulk senders risk being treated as spam sources - that is a real, sourced number, unlike most "optimal" thresholds floated for the other metrics.

What Campaign Monitor's report cannot show you

Delivered, in Campaign Monitor's reporting, means the SMTP transaction succeeded - it does not mean the message reached the inbox. A message that lands in Gmail's Promotions tab or spam folder still counts as delivered. The only way to see actual placement is a seed-inbox test: send to real addresses across providers and check each folder directly, rather than inferring from the aggregate report.

Content and list hygiene, in that order

If authentication and reputation check out but placement is still inconsistent, look at content next - excessive links, spam-trigger phrases, or an HTML-to-text-ratio skewed heavily toward images. Then look at list hygiene: hard bounces not being removed, or a list that includes contacts who have never engaged since signup. Both degrade domain-level reputation over time even when each individual send looks fine in isolation.

Dedicated IP economics, if your volume qualifies

If Campaign Monitor offers a dedicated IP option on your plan and your volume is consistent enough to sustain the reputation it builds, moving off a shared pool removes one variable from future deliverability investigations - you no longer need to wonder whether another sender caused a placement drop. The trade-off is that a dedicated IP's reputation is entirely your own to build and maintain; a quiet period or a bad send has nowhere to hide behind a larger pool's aggregate reputation the way it would on shared infrastructure.

Building a routine around these checks

Rather than investigating deliverability only after a campaign underperforms, build authentication and reputation checks into your regular send cadence. Before any list segment you haven't mailed in 30 or more days, re-verify authentication is still passing and check recent reputation trend. Before any volume increase, run a seed-inbox test to confirm current placement rather than assuming it matches whatever it was the last time you checked. This turns deliverability from a reactive investigation into a routine pre-flight check, which catches problems before they show up as a disappointing campaign report.

What not to do

Do not treat a single campaign's bad metrics as proof of a systemic problem. One send with unusually low engagement can be a content or subject-line issue specific to that email; check whether the pattern repeats across the next two or three sends before concluding the domain itself has a reputation problem.

Do not increase send frequency to compensate for falling open rates. If the cause is a reputation or engagement problem, more volume accelerates the decline rather than recovering from it.

Where MailPilot fits

MailPilot does not integrate with Campaign Monitor. For the sending domain or a related mailbox reachable over OAuth (Gmail, Outlook) or SMTP/IMAP (SendGrid, Amazon SES, Mailgun, Postmark, custom SMTP), MailPilot verifies SPF/DKIM/DMARC against live DNS, runs seed-inbox placement tests across providers, and tracks daily reputation per mailbox - catching the decline before it shows up as a falling open rate in Campaign Monitor's own report.