Instantly dashboard: the three metrics it hides

Instantly is one of the strongest cold-email platforms on the market. Its warm-up network, unibox and rotation logic are all well-built. But the dashboard you stare at every morning answers one question — "did my emails send?" — and leaves three bigger questions unanswered. Those three questions decide whether your campaign actually works.

What Instantly's dashboard shows

Before we talk about gaps, let us be fair to the product. Instantly surfaces several metrics very well:

• Warm-up score per mailbox — a 0–100 number from their internal network.
• Sends per inbox per day, with rotation controls.
• Open, reply and bounce rates per campaign and per step.
• Unibox with reply detection and sentiment tagging.
• Basic auth checks at mailbox setup (SPF/DKIM pass/fail).

That is enough to run a campaign, and in many cases enough to get decent results. It is not enough to know whether your mail is actually landing where people will see it.

Gap 1: per-provider placement

Instantly's warm-up score is a single number. It hides the most important fact about cold email in 2026: placement varies wildly per provider. A campaign can be 95% Inbox at Gmail and 5% Inbox at Outlook, or vice versa. The warm-up score cannot see that.

Why it matters: if 40% of your ICP is on Microsoft 365 and your mail only reaches the Gmail contacts, you are burning half your list every day without knowing. Reply rate goes down. You blame the copy. The copy was fine.

Fix: run a multi-provider placement test before every new campaign. Send the same message to seed mailboxes at Gmail, Outlook, Yahoo, Mail.ru, Yandex, GMX, ProtonMail and iCloud. Look at folder placement per provider. A free test covers all of these in one run.

Gap 2: tracking-domain DNSBL status

Instantly lets you set a custom tracking domain (you should — the default shared one is a deliverability risk). But once it is set, the dashboard never tells you its reputation again. If your tracking domain lands on Spamhaus DBL, URIBL or SURBL, every message you send goes to Spam regardless of how beautifully warmed your sending domain is.

Tracking domains hit blocklists for two reasons: they are newly registered (under 30 days old), or a previous tenant of the same domain used them for shady redirects. Instantly does not surface either signal.

Fix: before you add a tracking domain in Instantly, check it against the major URI blocklists. After setup, re-check monthly. The inbox-check tool runs this as part of the full audit.

Gap 3: DMARC alignment

Instantly verifies SPF and DKIM at mailbox connection. It does not verify that DMARC alignment will actually pass when the message is sent through its infrastructure. The mailbox can be perfectly set up in Google Workspace and still produce dmarc=fail once Instantly rewrites envelope senders for rotation.

This is the single most common authentication failure we see in cold email in 2026. SPF passes, DKIM passes, but DMARC alignment fails because the From domain and the authenticated domain do not match. Gmail and Yahoo's 2024 sender requirements made aligned DMARC a hard requirement for bulk senders — which cold outreach now qualifies as.

Fix: run a test send to a seed mailbox and inspect the Authentication-Results header. You are looking for dmarc=pass. If you see dmarc=fail or dmarc=none, fix alignment before the campaign runs.

The free 5-minute pre-launch check

Every time you add a new sending inbox to Instantly, or launch a new campaign, run this check first:

1. Authentication: send a test to a Gmail seed, open full headers, confirm SPF, DKIM and DMARC all show pass.
2. DNSBL sweep: check sending domain, tracking domain, and sending IP against Spamhaus, URIBL and SURBL.
3. Multi-provider placement: send one copy of your first email through Instantly to a seed list covering 20+ providers. Look at Inbox vs Spam vs Promotions/Categories per provider.
4. Content score: check the SpamAssassin and Rspamd scores on your template — under 3.0 is good, above 5.0 is risky.
5. Link check: every URL in the template through a link reputation scan.

The first four items run automatically in a single inbox placement test. The whole thing takes under 10 minutes and costs nothing.

Reading a multi-provider placement result

When you get the placement report, do not fixate on the headline number. Read it by provider:

• Gmail Inbox: target 85%+. Below 70% means domain or content issue.
• Gmail Promotions: neutral for cold outreach — not Spam, but not where replies come from. Reduce links and marketing language if you see this.
• Outlook / Microsoft 365: the strictest consumer-side filter. If this is below 50% Inbox, your Outlook contacts are functionally unreachable.
• Yahoo / AOL: list hygiene signal. Low Inbox here usually means bounce rate too high.
• Mail.ru / Yandex: CIS audience. If you sell there and these are Spam, your campaign is finished before it starts.

Rotating a burned inbox out of Instantly

When a placement test shows one mailbox in Spam at most providers while the others are fine, the mailbox is burned. Instantly's own dashboard will not flag this for weeks because the warm-up score updates slowly.

1. Pause the affected mailbox in Instantly (do not delete yet).
2. Move its share of volume to the remaining healthy mailboxes.
3. Leave the paused mailbox in warm-up-only for 30 days minimum.
4. Re-test placement at day 30. If Gmail and Outlook are both above 70% Inbox, it is safe to add back into rotation.
5. If still burned after 60 days, retire the mailbox and replace.

GlockApps vs Inbox Check for Instantly users

Instantly users often ask whether GlockApps is still worth the subscription. The honest answer depends on volume.

GlockApps strengths: mature integrations, scheduled automated tests, historical trend dashboards, Postmaster Tools integration. If you run 10+ sequences per week and need tracked trend data, it pays for itself.

Free inbox-check strengths: same per-provider placement data, no limits on tests, no account required, 20+ seed providers including CIS and European privacy inboxes. For the monthly pre-launch check most solo senders and small teams need, it is sufficient.

Frequently asked questions