Email deliverability glossary: 40 terms every sender should know
Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
A step-by-step guide to cleaning a HubSpot contact list: build the list, verify it through the integration, write the verdict to a custom property, then suppress and set undeliverable contacts to non-marketing.
To clean a HubSpot contact list, build an active list of the contacts you want to check, run it through an email verifier, write each verdict back to a custom contact property, and then use that property to suppress undeliverable contacts and set them to non-marketing. Done properly it takes under an hour for a list of 50,000, and it cuts both your bounce rate and your HubSpot bill, because marketing contact tiers are priced by the number of contacts you can email.
HubSpot already handles bounces: a contact whose address hard bounces is marked ineligible for marketing email and quietly dropped from future sends. That is reactive protection. By the time HubSpot marks the contact, the bounce has already counted against your sending reputation, and HubSpot's shared sending infrastructure is strict about accounts whose hard bounce rate climbs past the typical 2% warning line, because one bad sender affects everyone on the same pool.
The second reason is money. Marketing Hub pricing is tiered by marketing contacts, and lists typically decay at around 22% a year as people change jobs and abandon mailboxes. A database that grew to 60,000 marketing contacts over three years is likely carrying 10,000 to 15,000 addresses that will never receive another email, each of them occupying a paid seat. Setting those contacts to non-marketing is free and immediate, but you need to know which ones they are first.
The third reason is data quality. Lead scoring, workflows and sales sequences all assume the email on a record works. A sequence firing at a dead address wastes a rep's follow-up tasks and skews the reporting.
Do not verify the whole database on day one. Start with the contacts that will actually be emailed:
Contacts who opened something last week do not need a check; their engagement is proof enough.
verifyre_status, type Dropdown select with the options deliverable, undeliverable, risky and unknown. Optionally add a number property verifyre_score and a date property verifyre_checked_at.crm.objects.contacts.read and crm.objects.contacts.write, plus crm.lists.read so the integration can see your lists. Copy the token; HubSpot shows it only once.verifyre_status (and score and date to the optional properties). Verifyre pulls the contacts, verifies each address over SMTP without sending anything, and writes the results back. One credit is charged per unique address, and any address checked in the last 24 hours is free.verifyre_status is undeliverable, a list "Risky" for risky, and a list "Verified" for deliverable. Active lists update themselves as the property changes, so future verification runs flow straight into them.verifyre_status is undeliverable, unenroll from sequences.| Verdict | Score band | HubSpot action |
|---|---|---|
| Deliverable | 90 to 100 | Keep as marketing contact, include in all sends |
| Risky (catch-all, full mailbox, role account) | 30 to 89 | Keep, but send low-frequency or re-confirmation only, exclude from cold sequences |
| Unknown (server would not answer) | 30 to 89 | Re-verify after 48 hours; treat as risky if still unknown |
| Undeliverable | 0 to 29 | Set to non-marketing, add to suppression list, unenroll from sequences |
The difference between a permanent verdict and a temporary one matters here; hard bounce vs soft bounce explains why a full mailbox is risky rather than dead.
Yes, through CSV:
verifyre_status.The CSV route works fine for a quarterly clean. The integration is better when new contacts arrive daily, because it can be scheduled, and because it never needs an export that goes stale while you are working on it.
Quarterly for the whole marketing database, and before any large send to a segment that has not been emailed recently. New form submissions are better verified as they arrive, which is what real-time verification on the form does; the rest of the routine is in the email list hygiene checklist.
No. The integration only writes to the properties you map. Setting contacts to non-marketing, unenrolling them or suppressing them is done by you, through lists and workflows you control.
No. The record, its timeline, deals and attribution stay intact. The contact simply no longer counts towards your marketing contact tier and cannot receive marketing email until you set it back.
Usually because the domain is catch-all, so the server could not confirm the specific mailbox even though it exists. Recent engagement outweighs the verdict; keep those contacts on the verified list.
One per unique address. A 50,000 contact list with 2,000 duplicates uses 48,000 credits, and anything re-checked within 24 hours is free.
Related reading
@Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
@Real-time email validation checks an address as it is typed: syntax, typos, disposable domains, role accounts, MX and an optional mailbox check. Here is how it works.
@Gmail, Outlook and Yahoo addresses carry no company signal, so B2B teams segment them. When free addresses are legitimate, how the free and role flags route them, and bulk detection.
Photos: Freepik