Connecting MillionVerifier to Smartlead: setup, sync, and gotchas in 2026

How MillionVerifier and Smartlead Work Together

MillionVerifier validates each address through SMTP-level checks and returns one of four statuses: good, bad, catch-all, or unknown. You export the good rows as a CSV and import them into a Smartlead campaign. The whole handoff takes under five minutes once you know which column filters to apply.

The SMTP check works by knocking on the recipient mail server's door and asking if the inbox exists, without actually sending an email. Most mail servers answer honestly. The ones that don't are catch-all domains: they say yes to every query regardless of whether the specific address is real. That's the part you'll need to handle separately.

Smartlead doesn't verify emails on import. It trusts your list. The quality of what goes into your campaign is entirely on you, which isn't a criticism of Smartlead. That's how most cold email platforms work. Verification belongs upstream.

Step-by-Step Setup

The setup requires no API keys and takes six steps. You need a MillionVerifier account, a CSV of raw leads with an email column, and a Smartlead campaign ready to receive contacts. The free tier handles up to 100 test verifications before you commit to a paid plan.

1. Export your lead list from your prospecting tool as a CSV. MillionVerifier's column-mapping interface is fussy about header names. Label your email column exactly "email" before uploading.
2. Upload to MillionVerifier. Log in and navigate to "Verify Emails," then upload your CSV file.
3. Wait for processing. MillionVerifier handles roughly 100,000 addresses per hour on paid plans. A list of 5,000 takes about three minutes.
4. Download the results CSV. Filter the "result" column to keep only rows labeled "good."
5. Remove extra columns. MillionVerifier adds "disposable," "free," and "role" columns. Delete them unless you plan to segment by those signals.
6. Import into Smartlead. Go to Leads > Add Leads > Import CSV. Map your columns when prompted.

Common failure: missing name fields. If Smartlead rejects your import with "missing required fields," check that your CSV includes "first_name" and "last_name" columns. MillionVerifier doesn't export those. Carry them through from your original lead list before you upload to MillionVerifier.

If you hit a "file too large" error in MillionVerifier, split your list into batches of 100,000 rows and upload each separately.

What the Status Labels Actually Mean

MillionVerifier's "good" status means the SMTP server confirmed the mailbox exists. "Bad" means it failed at the SMTP layer and will hard-bounce. The real decision is what to do with "catch-all" addresses, because that's where your bounce rate is won or lost.

Catch-all domains accept any email sent to them, so MillionVerifier can't confirm whether a specific inbox is real. A practical rule: include catch-alls from companies with 500 or more employees, where corporate IT teams typically manage real mailboxes. Skip catch-alls from companies under 50 employees, where sloppy DNS configs are far more common.

"Unknown" addresses timed out during verification. Don't import them into a new campaign. Run a second pass 24 hours later. If they come back unknown again, drop them. They're not worth the deliverability risk.

When This Workflow Has the Biggest Impact

Verification matters most when you're importing scraped data, free-tier prospecting exports, or lists that are more than 90 days old. Fresh data from paid tools with real-time enrichment needs it less, but still benefits from at least one verification pass before you load a new campaign.

Three scenarios where the ROI is clearest:

• Apollo exports. Apollo's database is large but ages quickly for SMB contacts. Running Apollo CSV exports through MillionVerifier before a Smartlead sequence typically removes 8 to 15 percent of addresses that are no longer valid.
• Re-engagement campaigns. Old leads who went cold often changed jobs or had their company shut down. MillionVerifier catches these before you spend send volume on dead inboxes.
• Event and conference lists. Email addresses collected in person frequently have typos and formatting errors. MillionVerifier catches those at the SMTP validation layer before they reach your campaign.

What MillionVerifier Costs vs. the Alternative

MillionVerifier's pay-as-you-go plan charges $7 per 10,000 verifications, with no monthly commitment. For a team sending 50,000 emails per month, that's $35 in verification costs to protect an entire campaign. That's less than the cost of replacing one inbox after a deliverability hit.

The math on skipping verification is bad. Rebuilding a burned Smartlead inbox, spinning up new domains, and rewarming takes 4 to 6 weeks. The $7 per 10,000 is not optional at any real sending volume.

Monthly subscription plans reduce the per-verification cost further. At 1 million verifications per month, the price drops to roughly $0.40 per 1,000. Most outbound teams hit that tier within a quarter of consistent prospecting. If you're evaluating your full cold email infrastructure, Modern Inbound's outbound services page covers how verification fits into the broader stack.

Scale Outreach Without Hiring SDRs

Most B2B teams underestimate the work before sending: buyer-language research, list logic, DNS, warm-up, deliverability, copy testing, and reply handling. Modern Inbound runs the operating layer so founders can stay focused on sales calls.

Frequently Asked Questions

The most common questions about this MillionVerifier and Smartlead integration involve the CSV handoff process, how to handle catch-all addresses, and what bounce rate thresholds to maintain. These answers reflect real usage patterns from outbound teams running active cold email sequences at scale.

Does MillionVerifier integrate directly with Smartlead via API?

No. The two tools don't have a native API connection. The workflow is CSV-based: verify in MillionVerifier, download the results, and import the good addresses into Smartlead manually. A Make or Zapier automation can handle the file transfer step, but it's not a live sync.

What bounce rate should I target before importing to Smartlead?

Keep your expected bounce rate under 2%. Smartlead's infrastructure flags campaigns that bounce frequently and can limit your sending. Running your list through MillionVerifier first typically puts your bounce rate in the 0.5 to 1% range on a clean list.

Should I include catch-all addresses in my Smartlead sequences?

For enterprise accounts with 1,000 or more employees, yes. Catch-alls at large companies are usually real inboxes managed by corporate IT. For companies under 50 employees, skip them. Including all catch-alls without filtering will push your bounce rate up and erode your sender reputation.

How often should I re-verify my lead list?

Verify any list that's more than 60 days old before importing it into a new Smartlead sequence. B2B email addresses change at roughly 2 to 3 percent per month. A list that was clean in April may have a 10 percent bad address rate by July.

Next Steps

Once your verified list is in Smartlead, the next decision is sequence structure. How many steps, what sending frequency, and which inboxes carry which campaigns all affect deliverability as much as list quality does. A clean list plus sloppy sending configuration is a common failure pattern that verification alone won't fix.

If you want help configuring the full cold email stack, including domain setup, inbox warmup, sequence writing, and reply handling, Modern Inbound manages the outbound infrastructure so your team doesn't have to.