
If you already have a spreadsheet of email addresses, bulk email verification helps you assess the quality of the list before sending to it.
This guide follows the file-based process: prepare an export, run email checks through Data Soap, review the results and return approved updates to your CRM. For the wider maintenance process, use our email list hygiene checklist.
Data Soap’s email verification service checks address formatting and technical email signals, with information about disposable addresses, role inboxes and catch-all domains. A result helps you judge whether an address is suitable for your next step. It does not prove the identity of its user, guarantee inbox placement or provide marketing permission.
You need to keep those three questions separate: does the address appear usable, does this contact belong in the audience, and are you permitted to send the planned message?
Export the relevant segment from your CRM or email platform. Include the email address and a record identifier if needed so the results can be matched back safely. Share only the additional fields needed for the job.
Do not merge different people merely because they share an inbox. A shared accounts address may belong on several customer records. You can validate the address once while keeping the relationships in your CRM.
Decide whether known unsubscribes, previous permanent bounces and records outside your retention rules need to be included at all. An address that has opted out does not need a new successful technical check to remain excluded from marketing.
Use a simple preparation log: original rows, duplicates removed, records excluded and addresses submitted. This makes the output easier to reconcile later.
Sign in to your DataSoap account and use the file upload workflow for your list. The portal supports bulk cleansing without writing an integration. Check that the correct column is being used for the email lookup and choose the email checks relevant to the job.
Review your available balance and the current email validation pricing before processing a large export. Start with a small, representative sample when you are introducing a new source file or unfamiliar layout.
A useful sample includes ordinary business addresses, shared inboxes and records from older parts of the database. It should help you test the matching and import process, rather than demonstrate an artificially perfect result.
Download the results when processing is complete. Keep the returned information alongside the original record identifier. Do not treat every result as a simple instruction to delete a contact.
| Result or signal | Practical next step |
|---|---|
| Address appears valid | Assess audience membership and permission before adding it to a send. |
| Invalid address or permanent failure | Exclude it from the campaign; correct it only using reliable updated information. |
| Disposable address | Apply the policy appropriate to your service and the reason it was collected. |
| Role-based inbox | Review its relevance; a shared inbox is not automatically unusable. |
| Catch-all domain | Keep it distinct from mailbox-confirmed results and assess the uncertainty. |
| Temporary or inconclusive check | Hold for review or a controlled retry rather than calling it permanently invalid. |
These are handling categories for your workflow, not a promise that every download uses these exact column labels. Read the returned reason alongside the other fields.
Imagine an illustrative file containing 5,000 rows. You remove 100 repeated addresses and exclude 200 known opt-outs before checking the remaining 4,700 addresses. Your final campaign count will still depend on the results and your audience rules. It is not automatically 4,700.
Some flags overlap: an address can be both role-based and catch-all. Do not subtract each flag total from the list as though they were separate people. Use a record-level decision and then count the final groups.
Import approved changes using the stable identifier. Avoid overwriting unrelated fields or replacing a newer customer update with an older export. Record the validation date and preserve the reason for excluding records.
Apply the latest suppression list to the final campaign audience. An opt-out received while the file was processing must still take effect before sending. Keep uncertain records in a review group instead of quietly mixing them into the approved audience.
A file upload suits an existing list, a migration or an occasional campaign. An API suits repeated checks inside a form, CRM or application. Explore the DataSoap APIs when manual exports are becoming a recurring task.
Yes. Email verification assesses technical signals without sending a marketing message to each address. The result still has limits, particularly where the receiving server does not provide a definite answer.
No. Separate permanent failures from temporary problems and consider why the underlying record is held. Excluding an address from a campaign is different from deleting a customer record.
No. Sender configuration, reputation, message content and receiving-server decisions also influence delivery. Validation improves the information used to prepare the send.
Prepare a small sample, run the email checks and review how the results map back to your CRM. Once the workflow is clear, repeat it for the full segment. Explore email verification or ask the DataSoap team about your file.
£100 of credits for £4.99. New customers, once.