Salesforce Marketing Cloud list hygiene: build a sunset policy in SFMC

Your Salesforce Marketing Cloud list keeps growing, yet open rates keep sliding. Bounces pile up, spam traps lurk in the shadows, and your sender reputation erodes without a sound. The culprit is rarely your content; it is list hygiene. In this guide we build a sunset policy in SFMC step by step: how to measure inactivity, isolate at-risk contacts, run a re-engagement campaign, and then cleanly suppress those who stay silent, with ready-to-use SQL and a scheduled automation to tie it all together.

Why list hygiene changes everything

Mailbox providers such as Gmail, Outlook and Yahoo judge your reputation on how recipients actually engage. Every send to a contact who has been dormant for eighteen months is a negative signal: low opens, hard bounces, complaints. A smaller but engaged list lands in the inbox more often and costs less to send to.

Three risks of a neglected list

Reputation damage comes first: IP and domain scores drop once bounce or complaint ratios cross ISP thresholds. Next come spam traps, recycled addresses that never opt in but happily receive your mail. Last is cost: you pay for billable contacts who no longer read anything.

Defining inactivity with Data Views

In SFMC, engagement lives in the system Data Views: _Sent, _Open, _Click and _Bounce. A common definition of inactive: no open and no click in the last 180 days, despite the contact receiving at least five emails in that window.

SQL for inactive contacts

SELECT s.SubscriberKey, s.EmailAddress, MAX(s.EventDate) AS LastSend
FROM _Sent s
LEFT JOIN _Open o ON o.SubscriberKey = s.SubscriberKey
    AND o.EventDate > DATEADD(day, -180, GETDATE())
LEFT JOIN _Click c ON c.SubscriberKey = s.SubscriberKey
    AND c.EventDate > DATEADD(day, -180, GETDATE())
WHERE s.EventDate > DATEADD(day, -180, GETDATE())
  AND o.SubscriberKey IS NULL
  AND c.SubscriberKey IS NULL
GROUP BY s.SubscriberKey, s.EmailAddress
HAVING COUNT(s.SubscriberKey) >= 5

Write the output to a data extension called Inactive_180d using the Overwrite action. Keep in mind that Data Views only retain about six months of history, which is why the window is 180 days. For a longer lookback, archive your tracking events into your own data extension.

The key insight: never define inactivity on opens alone. Since Apple's Mail Privacy Protection, opens are inflated by machine activity; a click, or an on-site conversion, is the only signal you can trust.

Segment before you act

Not every inactive contact is equal. A customer who bought three months ago deserves different treatment from a prospect who never converted. Join your inactive list with CRM data, through Marketing Cloud Connect or a synchronized data extension, before deciding what happens next.

Three treatment tiers

Recently inactive contacts (90 to 180 days) get more relevant content at a lower frequency. Established inactives (180 to 365 days) enter a re-engagement journey. Deeply inactive contacts (over 365 days, no purchase) are candidates for suppression.

Building the re-engagement journey

In Journey Builder, use the data extension as the entry source and plan three messages a week apart: a value reminder, a flagship offer or piece of content, and a final candid note along the lines of "Do you still want to hear from us?" A click on the confirmation link puts the contact back into your regular flow.

Recording the answer with AMPscript

On the confirmation CloudPage, store the contact's response:

%%[
VAR @key, @rows
SET @key = RequestParameter("sk")
SET @rows = UpsertData("Reengagement", 1, "SubscriberKey", @key,
    "Status", "Reconfirmed", "ReplyDate", NOW())
]%%
<p>Thanks, you're staying on our list.</p>

Validate the sk parameter server-side and never expose the email address in the URL.

Suppressing the silent ones cleanly

When the journey ends, a second SQL query finds contacts who neither clicked nor reconfirmed. Rather than deleting them, set them to Held or add them to a global suppression list applied to every send. You keep the history, and reactivation stays possible if they show up through another channel.

SELECT r.SubscriberKey
FROM Inactive_180d r
LEFT JOIN Reengagement e ON e.SubscriberKey = r.SubscriberKey
WHERE e.Status IS NULL OR e.Status <> 'Reconfirmed'

Automating the cycle in Automation Studio

Schedule a monthly automation: query the inactives, query the silent ones, refresh the suppression list, then send an internal report. Add a volume guardrail: if more than 15% of the list is targeted at once, the automation stops and alerts your team, since that usually points to a data problem rather than real inactivity.

Measuring the impact

Track three indicators before and after your first purge: bounce rate, complaint rate and click rate on active sends. Also compare inbox placement through your monitoring tools. In most cases the volume you send drops by 10 to 20%, while click rate and deliverability improve noticeably within the next two or three campaigns.

Key takeaways

Measure on clicks. Opens are too noisy to define inactivity on their own.

Segment before you suppress. Blend engagement with CRM data to protect dormant customers.

Re-engage before you hold. Three well-spaced messages win back a meaningful share of the list.

Hold, don't delete. A Held status or global suppression preserves history and compliance.

Automate with guardrails. A volume threshold prevents accidental purges.

Want an audit of your list or a tailored sunset policy? Get in touch with CGC-Agency.

A voir: