Verify the email addresses in your Salesforce contacts and leads

The workflow

1. Build a contacts (or leads) report from the Reports tab. Add the Contact ID (or Lead ID), Email and any status field you want. Click the arrow next to Edit > Export, choose Details Only and Comma Delimited .csv, then Export. Details Only is not capped at 100,000 rows the way a formatted export is.
2. Upload the CSV on the verify page, signed in; the first 100 checks are free. The email column is found by its header or contents and every other column is kept.
3. When the job finishes, download the valid, risky and invalid files. Each keeps all of your original columns.
4. Add a custom text field on the object, for example Email Status, if you do not have one. Without a field to write into there is nothing for the import to update.
5. In Setup, open the Data Import Wizard, choose Accounts and Contacts (or Leads), and select the option that updates existing records. Match by Salesforce ID, which the report export included.
6. Map ID and the result column to Email Status, run a 20-row test file first, and only then import the full valid, risky and invalid files. Salesforce tells you the wizard handles up to 50,000 records per import; split larger files.

Columns to map

• Contact ID or Lead ID, the only key that cannot collide; it is what makes the update safe.
• Email, kept in the file so the verified address is the one you checked.
• A new Email Status column mapped to your custom field, with the result from the SimpleVerifier file.

What to do with risky and catch-all results

Do not auto-delete or change the Email field on risky rows: a catch-all domain is often a real prospect's company. Set Email Status to risky and build a report or list view that excludes invalid for campaigns and Pardot or Marketing Cloud syncs, while sales reps can still call risky contacts. Updates made through the wizard cannot be undone by Salesforce, so keep the exported report as your backup.

What people use it for

• Flag dead contacts before a Campaign send or a Marketing Cloud sync.
• Check leads that came from web-to-lead forms, where fake and mistyped addresses accumulate.
• Give sales ops an Email Status filter so reps stop sequencing addresses that will bounce.

Using the result

Each address comes back valid (the mail server confirmed the mailbox), risky (delivery could not be confirmed: a catch-all domain, a role address such as info@, or a provider that hides mailbox status) or invalid (it will bounce, or it is a throwaway address).

Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.

Comparing tools? See email verifiers for Salesforce compared, with prices checked on each vendor’s site.

Common questions

Which plans include API access for Salesforce?

API access comes with Pro, Business and Agency, listed on the pricing page; Starter covers CSV verification only. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.

Is there a SimpleVerifier app on the Salesforce AppExchange?

No. Nothing in your org changes until you run a Data Import Wizard update yourself.

Why match by Salesforce ID instead of email?

Matching on email only works as well as the addresses do; two records with the same name but different emails stay separate, and bad addresses are the very thing you are checking. The ID from your own report is the reliable key.