The Lead File Says One Thing, the Campaign Says Another

When a spreadsheet says 2,149 leads and the campaign shows 1,945, the missing 204 rows are not automatically a mistake.

They may be duplicates already in the workspace. They may match a workspace blocklist. Some may have missing or malformed email addresses. A verification gate may have marked them invalid or risky. The sequencer may have skipped them because of company-level limits or bounce protection.

The mistake is delivering only the final number without the arithmetic.

A real 204-row mismatch

In one recent delivery audit, the Google Sheet title said 2,149 leads. The actual populated lead-ID rows totaled 1,945. That left a 204-row variance before any campaign-level review.

This is anonymized first-party operating evidence. It does not prove that every mismatch has the same cause. It proves that the count must be checked at the source before platform exclusions are blamed.

Uploaded does not mean accepted

Instantly documents two duplicate checks. File-level duplicate detection always removes repeated email addresses inside the upload. Workspace-level duplicate detection can also skip leads already present in other campaigns or lists when that option is enabled.

Instantly also checks its workspace blocklist during import. A blocked email or domain is not imported, and a lead added to the blocklist later is prevented from receiving more campaign messages.

That means one CSV can produce several valid counts:

1. Rows in file: every physical data row.
2. Unique emails in file: after file-level deduplication.
3. Eligible emails: after blocklist, format, verification, and policy exclusions.
4. Accepted campaign leads: rows the sequencer imported.
5. Contactable now: accepted leads that are not skipped, stopped, bounced, or waiting.

Use the label that matches the number. Calling all five of them "delivered leads" creates the dispute.

Why PlusVibe and Instantly counts move differently

Sequencers enforce their own safety controls. Instantly's BounceShield can skip known high-risk recipients, blocklisted leads, and leads affected by company send limits. PlusVibe supports a daily cap per recipient domain at both workspace and campaign level, with the workspace cap taking priority.

A first-party PlusVibe snapshot from August 12, 2026 showed 10,445 total leads across four campaigns, but only 2,077 contacted at that point. The difference was not presented as a loss. It reflected campaign progress, scheduling, and eligibility at a moment in time.

Build a row-level reconciliation ledger

Do not reconcile by eyeballing two totals. Give every source row a stable ID and record the outcome of each gate.

lead_id
source_file
source_row_number
normalized_email
file_duplicate_status
workspace_duplicate_status
blocklist_status
security_provider_action
mailbox_verification_status
import_status
campaign_lead_id
final_destination
exclusion_reason
checked_at

The final destination must be one of four values: accepted, excluded, review, or failed. A failed API call is not an exclusion. A temporary verifier response is not an invalid email. A duplicate is not a bad lead. The labels preserve the difference.

Use control totals at every transition

The reconciliation equation is simple:

source rows
= accepted
+ excluded
+ review
+ failed

If the right side does not equal the source rows, stop. Find the missing IDs before upload continues.

Then add a second equation for the platform:

eligible upload rows
= accepted by sequencer
+ platform duplicates
+ platform blocklist matches
+ malformed or missing email
+ platform errors

This is how you tell the difference between a source-file problem and a sequencer rule.

Download the evidence after import

Import notifications disappear. Your proof should not.

1. Save the source file without editing it.
2. Save the normalized upload file and its row count.
3. Capture or export the sequencer's accepted and skipped results.
4. Record the campaign or list ID.
5. Read back accepted leads from the destination.
6. Join source IDs to platform IDs and calculate every exclusion bucket.

For Instantly, note whether workspace duplicate checking was enabled. If it was disabled intentionally, state why. For PlusVibe, record any recipient-domain caps that can delay contact even after import.

What the client should receive

The client-facing delivery should be short enough to understand and detailed enough to audit:

This complements the broader lead-list source-of-truth workflow. The source-of-truth design protects the file. The reconciliation test proves what happened after it left the file.

Frequently asked questions

Why does my campaign show fewer leads than my CSV?

Common causes are duplicates inside the file, duplicates elsewhere in the workspace, blocklist matches, missing or invalid email addresses, verification exclusions, security-provider policy, and platform-specific skip rules.

Does Instantly remove duplicate leads?

Instantly says file-level duplicate detection always runs. Its optional workspace-level check can also skip leads already present in other campaigns or lists.

Should blocklisted leads count as delivered?

They can count as source rows, but not as accepted or contactable leads. Report them in a separate exclusion bucket with the blocklist rule that applied.

How do I prove the correct final count?

Use stable lead IDs, row-level outcomes, control totals, the platform import result, and a destination readback. The arithmetic must close exactly.

AnswerThePublic research note

The English, United States report for cold email lead list was generated on August 12, 2026. It returned one Google related term, no Google questions, and no usable search-volume or CPC figure. AI-query prompts focused on verifying list quality, targeted lead providers, and the features buyers should inspect. Those prompts shaped the reconciliation and QA sections; no unavailable demand data was invented.

Sources