What it is
A marketing database is not a stock that only grows; it is an asset that decays continuously and has to be maintained. People change addresses, lose interest, switch the channel they read and abandon accounts that later turn into spam traps. Database health is the ongoing practice of keeping the contactable list both deliverable and valuable: managing that decay deliberately rather than letting dormant contacts accumulate. It is the place several scattered ideas in the bundle, hygiene, re-engagement, suppression of the unresponsive and the sunset policy, come together as one lifecycle for the contact, not the campaign.
The never-engaging tail does not sit there harmlessly. Under sender-level reputation it actively drags inbox placement for the engaged contacts who actually convert. The reachable list is the engaged subset; sunsetting is a net gain in reachability, not a loss of reach. The lifecycle and running practice that follow are the operational consequence, not a reluctant trim of a healthy asset.
Why a database decays
Decay has several independent sources, all of which a healthy programme expects.
- Address and channel churn. Contacts abandon mailboxes and phone numbers, or simply stop reading the channel they signed up on. The grant is still on file; the human behind it is gone.
- Disengagement. A contact who was active goes quiet, then dormant. The address still accepts mail, but the person no longer opens it. This is the more dangerous case: it looks alive.
- Hard failures. Hard bounces and complaints remove contacts outright and must be suppressed immediately, per the hygiene SLA in segmentation and data.
- Spam-trap formation. A long-abandoned address can be recycled by a provider into a spam trap. Continuing to mail the never-engaging tail is how a sender hits one, which is why dormancy is a deliverability risk and not just a soft metric.
The contact lifecycle inside the database
Treat each contact as moving through states, defining the transition rules once so the whole programme agrees:
- Active. Engaged inside the recent window; mailed at the normal cadence.
- Declining. Engagement recency slipping; a candidate for reduced frequency and a re-engagement touch.
- Dormant. No engagement across the sunset window, an open or click in email, a tap or session from push and in-app, a reply to an SMS, a purchase in any (a common default is 90 days, set from your own engagement distribution, not a universal figure).
- Re-engagement. Run the win-back sequence in automation and sequences once, as a deliberate last attempt, not an indefinite drip.
- Sunset. A contact who does not respond is moved out of regular sending and suppressed from broadcast. Keep the sunset criteria identical across the flow and the segment so they never disagree, as noted in segmentation and data.
This is a lifecycle of the database itself, parallel to the customer lifecycle mapping but read from the angle of deliverability and list quality rather than the customer’s journey.
Why it pays to shrink the list on purpose
Sunsetting feels like destroying the asset you spent to build, which is why so many programmes refuse to do it. The logic runs the other way. Because sender-level engagement now governs placement for the whole list, the never-engaging tail does not sit there harmlessly: it drags inbox placement down for the engaged contacts who do convert. Removing the dormant tail raises the deliverability of everyone who remains. This is the operational expression of list quality over size and the mechanism in engagement is the new deliverability: the reachable list is the engaged subset, worth protecting more than the headline count.
Running it
- Track the engagement-recency distribution, not just the total. Watch how the list splits across active, declining and dormant over time. A list whose total is flat but whose active share is falling is decaying under a healthy-looking number.
- Run hygiene to an SLA. Suppress hard bounces and complaints immediately and permanently; the written thresholds live in segmentation and data.
- Re-engage once, then sunset. A single, well-timed win-back attempt, then move the unresponsive to the sunset segment. Endless re-engagement to the dormant is the failure mode it is meant to prevent.
- Suppress, do not delete, by default. Keep sunsetted contacts on a suppression record. Without one, they get re-imported and re-mailed, undoing the sunset.
- Measure net growth, not gross adds. Net list growth is acquisition minus decay. A programme reporting only new sign-ups while ignoring decay can be shrinking its engaged base while claiming growth. Read database health alongside list building, which feeds the top of the same pipe.