Client reports: "I can't get email to send to subscriber X. Their record in the DE is there, Active status, email address correct. What's wrong?"
You check the DE - subscriber is there. You check the sendable setting - correct. You check the email address - valid. Nothing obviously wrong, yet email doesn't arrive.
The cause is almost always one of SFMC's three unsubscribe levels, and knowing which one saves you the hour we wasted the first time we hit this.
Level 1: Global Unsubscribe
The subscriber has opted out of every Marketing Cloud account that uses SFMC. Not just this brand - every brand.
Example: Subscriber A globally unsubscribed from Cloud Kicks's emails a year ago. Cloud Kicks uses SFMC. Later, Northern Trail Outfitters (different company, different SFMC account) imports Subscriber A and tries to send. SFMC blocks the send.
This is the most confusing case because the subscriber is "Active" in your account's records - but Global Unsubscribe is platform-level and overrides the account-level view.
How to check: there's no direct UI for "is this subscriber globally unsubscribed." You can verify via tracking records - if Sent count is 0 and the subscriber is Active, Global Unsubscribe is a strong candidate. Open a support case with Salesforce® to confirm.
Global Unsubscribe is rare. If it turns out to be the cause, there's no override - it's the subscriber's platform-level decision.
Level 2: Primary (Account-level) Unsubscribe
The subscriber has opted out of every email from this brand/account, but may still receive email from other brands using SFMC.
This is the most common unsubscribe, triggered when a subscriber clicks "Unsubscribe from all" in a Preference Center or the email footer.
Status in All Subscribers flips to Unsubscribed. Future marketing sends skip this subscriber entirely. Transactional sends can still reach them if they're in a Send Classification marked Transactional.
How to check: Email Studio > Subscribers > All Subscribers > search by Subscriber Key or email. If Status shows Unsubscribed, you found it.
Level 3: List Unsubscribe (Publication List)
The subscriber has opted out of one specific communication category but still receives others from the same brand.
Example: unsubscribed from "Weekly Promotions" Publication List, but still receives "Monthly Newsletter" and "Order Confirmations."
Set up via Publication Lists (Email Studio > Subscribers > Publication Lists). Each send is associated with a specific Publication List, and the subscriber's opt-out per-list is honored automatically.
How to check: look at the Publication List associated with the send, see if the subscriber is unsubscribed from it. Can also check tracking - _ListSubscribers or the Publication List detail UI.
Diagnosis flow
When a subscriber should be receiving email but isn't:
- Is the DE sendable? Check Is Sendable flag and Send Relationship.
- Is the subscriber status Active in All Subscribers? If not, Primary Unsubscribe - they unsubscribed from the account.
- Is the send's Publication List excluding them? Check Publication List memberships.
- Is it possibly a Global Unsubscribe? Rare, but check via Salesforce support if the first three check out.
90% of cases resolve at step 2 or 3.
Reference summary
| Level | Scope | Where it's tracked |
|---|---|---|
| Global | Every SFMC platform account | Global Unsubscribe list (platform-level) |
| Primary | This entire account / brand | All Subscribers - status: Unsubscribed |
| List | One Publication List | Publication List membership |
When to set up Publication Lists
If the client wants granular unsubscribe (subscribers opt out of weekly promos but keep monthly newsletter), Publication Lists are required. Without them, every unsubscribe is an all-or-nothing Primary Unsubscribe.
For B2C with multiple communication categories, set up Publication Lists early:
- Weekly Newsletter
- Promotional Offers
- Product Updates
- Birthday Campaigns
- Survey Invitations
Each send gets assigned to a Publication List at send time. Subscribers who opt out of one still receive the others.
The CAN-SPAM compliance note
All three unsubscribe levels must process requests within 10 business days per CAN-SPAM. SFMC processes near-instantly by default; custom Preference Centers that stage requests asynchronously need to respect this window.
Test before production: submit a test unsubscribe, verify the subscriber's status changes in All Subscribers within minutes, and confirm the next test send skips them.
Takeaway
When a subscriber isn't receiving email they should, SFMC is almost always respecting an unsubscribe somewhere - just not the level you looked at. Walk through Primary (All Subscribers status) first, then Publication List membership, then Global as a last resort. 5 minutes of checklist work versus an afternoon of random hypothesizing.
Debugging SFMC send failures on specific subscribers? Our Salesforce team runs audits, consent tracing, and Preference Center implementations on production engagements. Get in touch ->
See our full platform services for the stack we cover.
Need senior engineers for SFMC implementation, integration, or migration? See Sapota's Salesforce services — Marketing Cloud, Revenue Cloud, Sales Cloud, and Service Cloud delivery from $1,800/engineer/month.
