RUNBOOK // sfmcPRODUCTION

Deliverability / Bounce Investigation

Start from recent evidence before changing sender or audience strategy.

Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources0Other sources0Last verifiedNot recorded

Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.

01

Scope the incident

Which send/job, domains, audience segment, time window and sender identity are affected?

02

Pull recent bounce diagnostics

Use _Bounce or Tracking Extract to capture category/type/SMTP reason/code.

03

Separate recipient vs ISP patterns

Group by domain and bounce category; look for concentration and temporary blocks.

04

Check subscriber state

Inspect held/bounced status and historical bounce count where relevant.

05

Review recent changes

Audience source, send volume, sender profile, authentication, creative/link changes and acquisition quality.

06

Choose remediation from evidence

Do not remove or suppress broadly before determining whether the issue is permanent, transient or configuration-driven.