Automated List Hygiene With the Sunset Engine

Sending to disengaged contacts is worse than not sending at all: it drags your open rate down and signals to mailbox providers that recipients didn't ask for your email, degrading deliverability for everyone on your list. The Automated Sunset Engine identifies genuinely inactive contacts on a nightly schedule. Give them a last chance through a re-engagement journey first, then switch on suppression for the rest, with no manual list export and no reminder to run a clean-up.

The Automated Sunset Engine scans your contact list nightly for subscribers who have gone completely quiet — no opens, clicks, form submits, or purchases beyond your configured threshold — and either routes them into a re-engagement journey or suppresses them automatically. No manual list export, no periodic reminder to run the clean-up.

Inactive contacts are a deliverability liability, not just a vanity metric problem. Sending to contacts who never engage drives up your bounce-to-open ratio and signals to mailbox providers that recipients didn't ask for your email — which harms your sender reputation for the entire list, not just the quiet slice. The Automated Sunset Engine removes that liability on a schedule, before it becomes a reputation problem.

What counts as inactive

A contact is inactive when their most recent engagement is older than your inactivity threshold (60–180 days, defaulting to 90). Engagement means opens, clicks, answers in an email (such as form submits, votes or RSVPs) and purchases, store orders included. The engine only judges contacts it has seen engage at least once: a contact who has never opened, clicked or answered anything has no engagement record and isn't sunset.

Two-phase approach: re-engage first, suppress after

The policy has two settings for this: a re-engagement journey and auto-suppression. They don't run one after the other. With both on, the same nightly sweep enrolls an inactive contact and suppresses them, so the journey's emails skip them. Phase it yourself:

  1. Re-engage first: set your win-back journey (a scratch-off offer, a special discount, a "we miss you" poll) as the policy's re-engagement journey, with auto-suppression off. Each night, contacts who have crossed the threshold are enrolled.
  2. Suppress after: once the journey has had its 30 days, turn auto-suppression on and clear the journey. From then on, contacts past the threshold are suppressed with the reason Inactive, while anyone the win-back brought back is no longer past it.

A contact who just hadn't opened in a while gets one more chance, and persistent non-responders are cleaned up without anyone reviewing a list by hand.

Configuring it

Go to Settings → Sunset policy:

SettingRecommended value
Enable Sunset EngineOn
Inactivity Threshold (Days)90 (60 for a tighter list, 180 for a very slow-cycle audience)
Re-Engagement Journey (Optional)Your win-back journey for the first 30 days, then none
Auto-Suppress Disengaged ContactsOff for the first 30 days, then on

What suppressed contacts see

Nothing: a sunset contact is simply skipped by every send. They stay in your contacts list and appear on the Contacts Suppressed tab with the reason Inactive, where you can resubscribe them if they get back in touch. While the policy is on, a resubscribed contact who is still past the threshold is suppressed again the next night.

Measuring the impact

Monitor your open rate trend in the first 60 days after enabling auto-suppress. A clean-up of genuinely inactive contacts should push your open rate up, since the denominator (recipients) is smaller while engaged recipients remain. If open rate drops, review whether the threshold is too aggressive for your send cadence.

Getting started

  1. Build a win-back journey or install the Re-engagement starter.
  2. Go to Settings → Sunset policy, turn on Enable Sunset Engine, pick your journey as the Re-Engagement Journey (Optional) and set your threshold.
  3. Leave Auto-Suppress Disengaged Contacts off for 30 days to see which contacts the engine catches, then turn it on and clear the journey.

See Automated Sunset Engine for the full settings reference.

A typical build-and-send sequence

  1. 1

    Build or pick a re-engagement journey

    Install the Re-engagement starter (a scratch-off win-back pre-wired to an inactivity segment) or point an existing win-back journey at the sunset policy.

  2. 2

    Configure the sunset policy

    In Settings → Sunset policy, turn on Enable Sunset Engine, set your inactivity threshold (90 days is the default) and select the re-engagement journey.

  3. 3

    Run with auto-suppress off first

    Leave Auto-Suppress Disengaged Contacts off for the first 30 days. The nightly sweep enrolls inactive contacts into the journey and suppresses no one, so they get the win-back before anything is removed.

  4. 4

    Enable suppression

    Once the journey has had its chance, turn auto-suppression on and clear the journey, since with both set the sweep enrolls and suppresses a contact at once. From then on, contacts past the threshold are suppressed with the reason Inactive and skipped by every future send.

Frequently asked questions

What counts as engagement for the sunset engine?

Opens, clicks, answers in an email (form submits, votes, ratings, RSVPs, quizzes, bookings) and purchases, store orders included. The most recent of them is what the engine compares against the inactivity threshold, so a contact who bought something 60 days ago but has never opened an email isn't inactive. A contact with no recorded engagement at all isn't evaluated.

Can I resubscribe a contact who was sunset-suppressed?

Yes. Sunset contacts stay in your contacts list and appear on the Contacts Suppressed tab with the reason Inactive and a Resubscribe action. Resubscribing doesn't reset their engagement, so while the policy is on, a contact who is still past the threshold is suppressed again the next night.

Does the sunset engine replace behavioral segments for win-back journeys?

They're complementary: a behavioral segment with a segment-entered trigger gives you a journey that catches contacts the moment they go quiet, while the sunset engine suppresses contacts once they're past your threshold. Run both together.

What happens if I don't configure a re-engagement journey?

You can skip the journey step entirely. With auto-suppress on and no journey configured, the engine goes straight to suppression for any contact past the threshold — fine for very aggressive list hygiene, but skips giving them a last chance.

When does the nightly sweep run?

Once a night, around 02:00 UTC. Saving the settings doesn't run it straight away.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.