Keep your Salesforce Pardot prospects mailable, deliverable, and off your bill
Salesforce Pardot — now Marketing Cloud Account Engagement — marks a prospect unmailable the moment it hard-bounces and holds it out of every future send, so it reacts fast to a bad address. But it can't judge a prospect it has never mailed, and on a platform that bills by the mailable prospect, every never-mailed invalid from an import, a form, or the Salesforce sync is both a deliverability risk and a line on your database count. Qualisend closes that gap: export your prospects, verify every address, and mark or delete the dead ones before your next send. Here's the workflow that works today, plus the API and no-code options.
One-click Salesforce Pardot sync is paused while we rebuild the platform
We've deliberately paused our one-click native connectors while we re-engineer the sync layer they run on — hardening how we authenticate, respect each platform's rate limits, and write results back — so that when the native Salesforce Pardot integration returns, it stays dependable at any list size rather than fragile at scale. None of this touches how Qualisend verifies an address.
Everything you need works today: the CSV export → verify → reimport loop below, and the API for verifying at signup, are both fully supported and running in production — that's how teams keep Salesforce Pardot clean right now.
What Salesforce Pardot cleans for you
Account Engagement's native hygiene runs on prospect mailability. A single hard bounce, or five soft bounces on the same address, flips a prospect to unmailable and holds it out of every future list email; an unsubscribe sets Opted Out; and a Do Not Email flag — set by hand or by import — does the same. Any of those makes the prospect unmailable, and unmailable prospects are excluded from marketing sends and drop off your mailable database count. For addresses Account Engagement has actually mailed, that's reliable automatic hygiene — and because retiring an address also takes it off your billable count, its own housekeeping never inflates your bill.
What it can't catch
The catch is that every one of those mechanisms is reactive — it needs a send and a bounce to fire. Never-mailed invalids from CSV imports, form and landing-page completions, and the Salesforce sync have never bounced because Account Engagement has never mailed them, so they sit in your database as fully mailable prospects until your first email proves otherwise — which is exactly when a mailbox provider forms its first impression of your domain. Disposable addresses, role addresses (info@, sales@), and decayed corporate mailboxes slip through the same blind spot, and B2B lists are unusually heavy with all three. An imported list is the sharpest case: it arrives with its bounce history stripped, so an address that was already failing on the old platform looks brand new — and counts as a mailable, billable prospect from the moment it lands.
Why a clean Salesforce Pardot list matters
On Account Engagement the billing model cuts the opposite way from most email tools, which sharpens the case for verifying early. Salesforce sells your prospect database in blocks of 10,000 mailable prospects, and only mailable prospects count — unmailable and recycled prospects don't — so a hard-bounced address actually drops off your bill once it fails. The leak is the never-mailed invalid: it stays a fully mailable, billable prospect until a send finally bounces it, so you can pay to store it for a whole billing cycle, or tip into an overage Salesforce invoices you for, while waiting for the bounce that would have retired it for free. Verifying a file before import keeps that junk off your mailable count from day one; verifying the database you already have lets you mark the dead addresses unmailable now — potentially back under a 10,000-block threshold — instead of a send from now. And the deliverability stakes are the same as everywhere: Account Engagement sends most accounts over shared IP infrastructure, so every hard bounce and spam complaint from an unverified list feeds the sender-reputation signal that Gmail and Yahoo's 2024 bulk-sender rules now police directly — and that decides whether the prospects you earned honestly reach the inbox at all.
The workflow that works today
Direct connectors are paused while we rebuild the platform, so the dependable path is the CSV loop: export from Salesforce Pardot, verify in Qualisend, reimport the clean file.
Export your prospects from Account Engagement
In Prospects, filter to the segment or list you want to clean (the Mailable filter is a sensible default), then use the prospect table action CSV Export — choose Express for the key fields or Full to include your custom fields. Account Engagement emails you when the file is ready and keeps it on the Exports page to download for 60 days. For scheduled backups, the Export API (v5) returns the same prospect data as CSV.
Verify the file in Qualisend
Upload the CSV to Qualisend bulk cleaning — up to 1,000,000 addresses per job, duplicates charged once — or paste addresses directly. The free plan's 100 one-time credits, which never expire, cover a first sample before you commit.
Read the results
Every address returns deliverable, risky, undeliverable, or unknown with a reason code, a 0–100 score, and sub-flags (catch-all, disposable, role, full mailbox), plus the MX provider and probe detail as evidence. Download the cleaned CSV.
Retire the undeliverables in Account Engagement
Filter your results to undeliverable. The cleanest way to act on them is to import a CSV that sets Do Not Email = true — a column of 1s mapped to the Do Not Email field: that marks them unmailable, drops them off your mailable database count, and keeps the record so a future import can't silently re-mail a known-bad address. Or use a prospect table action to mass-delete them to the Recycle Bin, which also removes them from your mailable count. Two cautions: a deleted prospect isn't gone for good — it undeletes with its full history if it later submits a form or re-syncs from Salesforce, and a permanent purge of the Recycle Bin typically needs a Salesforce support case, so Do Not Email is often the cleaner retire; and a Suppression List only omits an address from your sends without dropping it off your mailable count, so it's a targeting tool, not a billing lever. Verify before you suppress.
Or automate it at signup
Prefer to keep junk out from the start? Verify at the point of capture with the Qualisend REST API (scoped keys, rate limits, webhooks), or wire a no-code flow through Zapier, Make, or n8n so a prospect from a new form or landing-page completion — or a lead about to sync in from Salesforce — is checked before it ever becomes a mailable, billable prospect.
What Qualisend flags on every address
- Never-mailed invalid addresses that would hard-bounce and flip the prospect to unmailable on your next send
- Disposable / throwaway domains built to expire
- Role addresses (info@, sales@, support@) — common on B2B lists — that skew the scoring and grading your programs run on
- Catch-all corporate domains, flagged so you can move them to a dedicated list and throttle
- A 0–100 confidence score and machine-readable reason code for every address
A native, one-click Account Engagement (Pardot) connector is part of the platform we're rebuilding — it's returning, not deprecated. Until it ships, the CSV loop above and the API are the fully supported path, and they work with any Account Engagement edition.
What to do with each result
Every address comes back with a verdict and sub-flags. Here's the action that keeps your Salesforce Pardot list clean without throwing away contacts you can still reach.
deliverableKeep as a mailable prospect and send as normal.deliverable + role flagKeep for operational and account mail; exclude from scored and graded engagement programs.risky + catch-all flagMove to a dedicated list and throttle — the corporate domain accepts everything at the door, so the mailbox behind it can't be confirmed.risky + disposable flagMark Do Not Email or delete — the inbox was built to expire.unknownKeep mailable and re-verify next clean — usually greylisting or rate-limiting, not a verdict on the mailbox.undeliverableSet Do Not Email via a bulk import, or delete to the Recycle Bin; both take it off your mailable count. Don't wait for the send to bounce it.Related reading
Verify at capture so junk never becomes a mailable prospect.
Spot-check a sample of your Pardot list before committing to a full clean.
How fast a dirty list compounds into a deliverability problem.
Why a clean list protects inbox placement on shared sending infrastructure.
The platform-agnostic playbook behind the steps above.
The 2024 bounce and complaint thresholds your Account Engagement sends must clear.
Salesforce Pardot verification FAQ
Clean your Salesforce Pardot list in minutes
Start free with 100 credits that never expire — no card required. Export, verify, reimport, and protect your next campaign.