Dievio
Key points
- Distinguish available contact fields from validation evidence and inbox placement.
- Check applicable sender requirements independently of the list.
- Classify invalid recipients, policy failures and complaints before choosing an action.
Lead data quality affects which addresses you send to and whether the message fits the recipient. Deliverability also depends on authentication, sending behaviour, provider rules and recipient feedback. A clean list cannot guarantee an inbox placement.
Review the audience, contact data and sending setup as separate controls. When delivery weakens, identify the failing stage before replacing a list or increasing sending volume.
Separate contact quality from message delivery
| Control | Question it answers | Limit |
|---|---|---|
| Account and role fit | Is this person relevant to the intended business conversation? | A relevant title does not establish interest or permission |
| Field availability | Does the record contain an email or other contact value? | Presence does not prove the address is current |
| Email validation | What checks were performed, and what was their result? | A result has a method, time and limitations; it is not an inbox guarantee |
| Sender and message checks | Does the sending setup meet the recipient provider's requirements? | Passing authentication does not establish recipient interest or guaranteed placement |
Use the B2B data quality checklist to evaluate source and field evidence. Keep that review separate from the sending provider's acceptance rules.
Review the records before any campaign handoff
Confirm the person and the account
Check the current company, full role title and account criteria. A technically valid address can still belong to the wrong person for the campaign. Do not treat a seniority label as proof of budget ownership.
Keep uncertain addresses explicit
Remove malformed values and investigate obvious conflicts. Retain the validation status, method and observation time when those are available. Unknown or catch-all outcomes need a deliberate handling rule rather than being relabelled “verified”.
A personal-domain address or a shared role inbox is not automatically invalid. Decide whether it fits the campaign's audience and purpose. Do not infer a named individual's responsibility from a generic mailbox.
Apply preferences and exclusions
Check suppression and the applicable requirements for the intended channel before activation. Keep the records that explain why someone should not receive a message from re-entering through the next import. The B2B data compliance guide covers that separate review.
Check Gmail requirements independently of the list
Google's email sender guidelines require SPF or DKIM for all senders to personal Gmail accounts, alongside valid forward/reverse DNS, TLS and appropriate message formatting. Bulk senders have additional requirements, including SPF and DKIM, DMARC and alignment.
Review these with the person responsible for the sending service. Keep sender identity accurate and do not use misleading message headers. Google also recommends sending to people who want the messages; an address found in a database does not establish that expectation.
The Gmail sender FAQ explains bulk-sender classification and scope. Its requirements apply to messages sent to personal Gmail accounts; do not assume they describe every business mailbox provider.
- Confirm which domain and service actually send the messages.
- Verify the applicable authentication and alignment setup.
- For relevant bulk marketing traffic, implement the documented one-click unsubscribe mechanism and a visible body link.
- Test preference handling rather than assuming a footer link completes the process.
Google's FAQ says unsubscribe requests should be honoured within 48 hours. These controls are prerequisites, not a promise that a recipient will place the message in their inbox.
DievioYour next customer starts here.
Find decision-makers by role, company and location. Build your next prospect list in Dievio.
Find my leadsFree audience preview · No credit card
Read the signals without inventing a universal bounce benchmark
Keep rejection responses, reported complaints and business outcomes distinct. A bounce-rate increase can have several causes; a low bounce rate does not prove inbox placement or audience fit.
| Signal | Investigate | Next action |
|---|---|---|
| Invalid-recipient failures | Address quality, source, role changes and repeated use of old records | Suppress confirmed invalid addresses and review the affected cohort |
| Authentication or policy rejection | Actual provider response, sending configuration and message requirements | Correct the sender-side cause rather than marking every address invalid |
| Accepted messages but weak outcomes | Placement evidence, recipient expectations, targeting and message relevance | Investigate without treating an acceptance event as proof of inbox delivery |
| Complaints or opt-outs | Audience expectations, frequency and preference handling | Respect the request and review the campaign before continuing |
Google recommends keeping its user-reported spam rate below 0.1% and avoiding 0.3% or higher in the sender FAQ. Those are Gmail spam-report figures, not universal hard-bounce, reply-rate or list-accuracy thresholds.
The Postmaster Tools dashboard guide explains those limits. Use provider data with sending logs and a deliverability monitoring workflow; avoid relying on a single indicator.
Run a repeatable list and campaign review
- Define the cohort. Keep the source, account criteria, role group and review date together.
- Apply current suppression. Remove ineligible records before they reach the sending queue.
- Review the required fields. Check identity, email status and validation evidence; keep uncertain outcomes visible.
- Check the sending setup. Confirm applicable provider requirements and the unsubscribe process.
- Classify delivery failures. Separate invalid recipients, temporary problems and policy issues before choosing recovery.
- Feed findings back. Correct the source selection, mapping or review process that produced recurring problems.
Set review timing from the next campaign, material account changes and observed problems. A universal monthly or quarterly schedule does not fit every list. The lead list maintenance guide provides a cohort-based approach.
Use Dievio for audience and contact retrieval
Use account and role filters to define the relevant audience, then preview matching contact counts before retrieval. A count preview does not test the emails in the result.
Review returned fields against the campaign's requirements. If you already have LinkedIn profile URLs, LinkedIn lookup can match them to available contact records. It does not guarantee current employment, a fresh SMTP check or inbox placement.
Apply your validation, preference and sending checks before activation. Start with the pre-export hygiene checklist so the handoff contains reviewed records and clear unresolved cases.
