Database hygiene works best as a release process with visible decisions. Simply deleting duplicates or reporting an email validation percentage leaves important questions unanswered: which records were excluded, what changed and whether suppressed contacts stayed suppressed. At Latest Mailing Database, we recommend keeping those decisions attached to each campaign selection.
Preserve the original import
Store a restricted original copy before changing fields. Record the supplier, delivery date, file version, row count and intended selection. Work on a separate copy so the team can investigate a transformation without reconstructing the source. Do not circulate the raw file through personal messaging accounts.
Define the required columns before processing. A country field, source reference and permission evidence serve different purposes from a person’s name or email address. Reject a file that cannot be mapped reliably rather than guessing column meanings from position.
Normalize carefully
- Trim accidental leading and trailing whitespace and preserve the original value for review.
- Standardize country labels using an agreed mapping with an exception list.
- Keep telephone numbers as text so leading zeros and plus signs survive spreadsheet imports.
- Preserve accents and legitimate punctuation in names and addresses.
- Do not remove email plus tags or dots across all providers; address behavior depends on the service.
Document each rule and count the rows it changes. Review unexpected shifts, such as a country mapping that moves a large group into one destination. A transformation that looks tidy can still reduce accuracy.
Separate technical checks from permission
Syntax checks examine address structure. Domain and MX checks examine domain configuration. These checks alone do not establish that an individual mailbox exists, belongs to the intended person or may receive marketing. Store the result type and check date rather than presenting every test as the same verification.
The Gmail sender guidelines describe authentication and sending requirements for mail to personal Gmail accounts, with additional requirements for bulk senders. They concern sending practices as well as message handling. Passing a database check does not replace sender authentication or opt-out processing.
Review duplicates and exceptions
Use stable identifiers where available and define whether the campaign is person-based, mailbox-based or company-based. Two people can share a business mailbox; one person can have multiple legitimate addresses. Route uncertain matches to review instead of merging solely because names are similar.
| Bucket | Release action |
|---|---|
| Eligible selection | Keep only after the required evidence and suppression checks pass. |
| Technical exception | Hold malformed or unresolved contact values for correction. |
| Evidence exception | Hold records missing the required source or channel basis. |
| Suppressed | Exclude from the relevant campaign and preserve the exclusion as required. |
Apply suppression again immediately before release, after transformations and deduplication. Confirm that a replacement address or new import cannot bypass an existing withdrawal without review.
Release with a short manifest
Record input rows, duplicates handled, technical exceptions, evidence holds, suppressed rows and final output rows. State how overlapping exclusion reasons are counted so the totals reconcile. Include the campaign purpose, rule version, processing date and reviewer. Keep sensitive evidence in controlled storage rather than embedding it in the export.
After sending, feed hard failures, complaints and withdrawal requests back into the maintenance process. Set review intervals based on the data’s purpose and observed changes; repeatedly changing a displayed date is not a substitute for reviewing the records.
Use the permission records checklist before release, review SMS-specific checks when using mobile numbers, or request a sample format to discuss the fields needed for your workflow.