What automation triggers indicate a list-cleaning event?

Your latest campaign went out and something feels off. Bounce rate crept up. Opens dropped. A few spam complaints rolled in. These aren't just bad days. They're your list telling you it needs attention, and the best way to act on them is to build automation rules that catch the signals before they compound into a deliverability problem.

Here are the specific triggers worth watching, with the thresholds that actually matter.

Bounce rate spike (hard bounces)
A single hard bounce is normal. A batch is a warning. If your hard bounce rate crosses 2% in any single campaign, that's your trigger. Set an automation that flags any send with hard bounces above 2% and immediately suppresses those addresses from future sends. Soft bounces need a little more patience. Three consecutive soft bounces to the same address is a reasonable threshold before suppressing.

Spam complaint rate
Anything above 0.08% complaint rate per campaign should kick off a cleaning review. Gmail and Outlook both use this as a reputation signal. If you're connected to Google Postmaster Tools or the SNDS dashboard for Outlook, you can pull these numbers automatically. At 0.1% you're in dangerous territory. Your automation should pause new campaigns to the affected segment and queue those addresses for suppression.

Open rate drop (engagement decay)
A sudden 20%+ drop in open rates across a segment, not just one campaign, signals a problem. That problem might be deliverability (you're landing in spam and people aren't seeing emails at all) or it might be a list age issue. Either way, it's a trigger to run engagement-based hygiene on that segment.

Inactivity thresholds
This one varies by sender type, but here's a practical framework. No opens or clicks in 90 days for a weekly sender. No opens or clicks in 6 months for a monthly sender. When a subscriber crosses that threshold, they shouldn't get deleted outright. They should move into a re-engagement sequence. If they don't respond to two or three re-engagement emails, then suppress them. The automation logic here is date-of-last-engagement plus a workflow branch: re-engage or suppress.

Form spam attacks
A sudden spike in new signups, especially if they come in clusters, all from the same IP range, or all using similar email patterns, is a form attack trigger. Your automation should flag any signup batch where more than 5% of addresses fail syntax or domain validation at the point of entry. Catching this at the form level means you never add junk to your list in the first place.

Domain-level anomalies
If a high volume of addresses from one specific domain start bouncing together, that domain may have changed its MX records, shut down, or become a spam trap farm. An automation that monitors bounce clusters by domain and flags any sending domain generating more than 10 bounces in a campaign is worth building, especially for B2B senders with corporate email addresses.

Most major ESPs let you build at least some of these rules natively. Mailchimp and Klaviyo handle bounce suppression automatically and let you build engagement segments with custom inactivity windows. HubSpot and ActiveCampaign let you build more complex workflow branches that combine bounce status, engagement score, and signup date into suppression logic. Twilio SendGrid handles suppression lists at the API level, which is useful if you're managing multiple sending streams.

And if your list is older or hasn't been cleaned in a while, automation rules alone won't be enough for the first pass. You'll want a bulk validation run before you lean on ongoing trigger-based hygiene. (If you need that, we clean lists at RME. Here's how it works.)