Best Practices

Email verification is most useful as one step in a responsible sending process. It can remove obvious technical problems and highlight uncertainty. It cannot create consent, prove a person's identity or guarantee inbox placement.

Verify at useful moments

Run a check when it can change your next decision:

• before an important campaign;
• after a list has been unused for a meaningful period;
• after importing contacts from another system;
• when bounces or complaints increase;
• when a form or integration starts producing suspicious data.

For a new source, verify a small representative sample first. That reveals whether you selected the right column and whether the list needs a deeper review before you spend credits on all of it.

A repeatable review cycle

1. Save the source export and record how those contacts were collected.
2. Verify a sample if the source is new or unfamiliar.
3. Review the status mix and a sample of the reasons, not only the headline score.
4. Correct systematic data problems in the original form or import.
5. Run the full segment only when the review supports that decision.
6. Keep the resulting export with the campaign record and compare it with later bounce and opt-out data.

Keep list quality separate from permission

Only send to contacts you have a valid reason to contact. A Safe result does not make a purchased, scraped or old list permission-based. Keep a record of how contacts joined the list, honor unsubscribes and do not use verification to justify sending to people who did not expect it.

Segment the result instead of using one rule for everyone

Export groups separately. For example, a campaign may start with Safe + Valid while a team member reviews Risky addresses. Do not assume every role address or free-provider address is bad: some flags are context, not a rejection.

Avoid threshold-only automation

Do not build an integration that silently treats a numeric score as universal permission to send. A sensible automation can route Invalid records to a correction queue, flag Risky records for review and prepare Safe + Valid for a permitted campaign. It should not overwrite consent fields, resubscribe an opted-out contact or remove account-specific suppression information.

Use Quick and Deep deliberately

Choose Quick for regular list maintenance, opt-in lists and a first sample. Choose Deep when extra evidence could affect a high-value decision, such as a stale list or a less familiar source.

Deep may ask recipient systems for additional mailbox information, but they control the answer. A provider can hide mailbox state, accept every probe or offer no useful verdict. Treat that information as one signal, not a guarantee.

Make the mode decision visible

Record why a job used Quick or Deep in its name or campaign record. A simple note such as Quick: recent event registrations or Deep: old partner export gives the next reviewer context for the cost and the resulting risk tolerance. It also prevents an expensive Deep run from becoming a default that nobody reevaluates.

Check the job before starting

The Prepare stage shows the unique address count, duplicates removed, mode and actual credit charge. Review it before selecting Start Verification. This catches the common mistake of verifying a name or notes column instead of the email column.

The same normalized list in the same mode is recognized for 24 hours. TrekMail returns the existing job rather than charging it again.

Improve the source, not just the score

If a large share of a list is Risky or Invalid, investigate the collection path:

• require clear email input validation in your own forms;
• use a confirmation step when it fits the audience and workflow;
• fix recurring typo patterns at the source;
• remove contacts that bounce or opt out instead of repeatedly retrying them;
• recheck a list after a long gap instead of assuming an old score still applies.

Verification results are retained for 15 days. Save the export needed for your campaign record, then use real campaign feedback to improve the next import.

Watch the outcome after sending

Verification is not the last checkpoint. Compare later delivery events, bounces, complaints and unsubscribes with the segment you used. If a Safe + Valid group produces unexpected problems, pause the relevant source and investigate. If a Risky pattern keeps proving harmless for a clearly consented audience, document that context rather than weakening rules for every source.

Use the verifier to make a better decision before a send, then use real campaign feedback to improve the next decision.

For status meanings, see Reading Email Verification Results.