Skip to content
2XD.co

Email Marketing / Deliverability & List Health

Find the cause before changing the entire sending program.

Review authentication, suppression handling, list sources, and delivery patterns. Narrow the issue to the controls you can actually inspect and improve.

Explore a workflow

Illustrative example

A sending domain has a known audience and a recent delivery report.

Sending review

Example record and reporting checks
CheckEvidence
AuthenticationReview domain configuration
AudienceGroup by source
FailuresInspect bounce reasons

Ready for the owner’s review

What happens

Review authentication, suppression rules, and changes by acquisition source.

The owner receives a prioritized list of concrete checks and fixes.

One decision that matters

One bad source can disappear inside the average.

A recent import may account for a disproportionate share of delivery failures. Segment the review by source and time period before deciding that every subscriber or sending domain needs the same treatment.

Technical reading

Google · Email sender guidelines ↗

Background for this design discussion. Implementation and outcomes depend on your systems.

Understand the moving parts

Three concepts behind this service.

What the term means and where your team will encounter it.

Authentication

Domain controls used to verify sending identity.

Review the relevant provider requirements and configuration.

Suppression

Records that must be excluded from a send.

Preserve exclusions when lists move between tools.

Source cohort

Recipients grouped by how and when they entered the program.

Compare bounce reasons for a recent import with other sources.

The build plan

What goes into
the working version.

We review your sending foundation and list quality. Then we clean up obvious risks, organize suppression and unsubscribe handling, and create basic practices for safer sending.

  1. 01

    Sending setup review

    We check the basics of domain authentication, sender identity, platform setup, and tracking.

  2. 02

    List hygiene

    We identify old, risky, duplicate, bounced, or unengaged contacts that can hurt performance.

  3. 03

    Suppression handling

    We help organize unsubscribes, exclusions, bounced contacts, and do-not-contact lists.

  4. 04

    Deliverability habits

    We provide simple sending rules for frequency, segmentation, content, and list maintenance.

A result you can check

Agree on the evidence
before the demo.

These are recommended checks for this service. We choose a baseline and acceptance criteria with the person responsible for the work.

CHECK 01

Failure patterns

Compare bounce reasons by source and period.

CHECK 02

Suppression fidelity

Verify excluded addresses remain excluded after imports.

CHECK 03

Configuration drift

Recheck sending-domain setup after changes.

Included at handoff

Built, explained, and ready for your team.

  • Sending setup review
  • List health cleanup plan
  • Suppression and unsubscribe process
  • Deliverability recommendations

In practice

Investigate a change in bounces

Compare bounce reasons by list source and sending domain before changing the whole program. Authentication checks and suppression history help narrow the cause.

Bring a recent delivery report and your sending domains.

Review list health →

Questions before you start

Can you guarantee inbox placement?

No. Recipient systems make placement decisions. The review identifies configuration, list quality, and sending practices you can improve.

What records help the review?

Bring recent bounce reports, sending-domain settings, list sources, and suppression rules.

Should we remove every inactive subscriber?

First define inactivity using meaningful signals and the audience’s normal buying cycle. Separate confirmed bad addresses from quiet but valid subscribers.

Can one source of signups damage list quality?

Yes. Review bounce and complaint patterns by acquisition source and date. That can reveal a problematic import that overall averages hide.

Do authentication checks explain every delivery problem?

No. Authentication is one input. Sending history, recipient engagement, complaints, and list practices also need review.

What should happen after a suppression-list migration?

Compare source and destination suppressions and test excluded addresses before the next campaign. Preserve the reason each record was suppressed.