Klaviyo BFCM Sunset Flow: Clean the List Before Volume Rises

A BFCM sunset flow is not a last-minute blast to everyone who stopped opening email.

It is a controlled exit path for profiles whose inactivity has been defined with enough evidence to defend. If the entry segment is loose, the flow can target recent customers, ignore engagement from a previous platform, or suppress email while a valid SMS relationship still exists. If it runs too close to Black Friday, the final re-engagement message competes with the campaign calendar it was meant to protect.

Treat the sunset flow as a deliverability release. Define the source data, eligibility window, engagement exits, channel boundaries, campaign exclusions, suppression review, monitoring, and rollback before any profile enters.

Define inactivity from your real sending history

There is no useful inactivity window without sending context. A daily sender, a weekly editorial program, and a seasonal brand create different evidence from the same number of quiet days. Start with message frequency, the number of emails received, the last meaningful click, recent site activity, order history, and the period covered by the data.

Klaviyo's list-cleaning guidance says engagement windows and message thresholds should match the sending cadence. It also notes that historical engagement from a previous email provider belongs in the segment when it overlaps the chosen period. A recent migration can make an active subscriber look silent if the old events never reached Klaviyo.

Write an eligibility contract before building the segment. Record the email events, ecommerce events, provider history, time windows, minimum message exposure, consent state, customer exclusions, market, and data owners. Save a count and sample profiles before activating the flow. A segment preview is evidence to inspect, not proof that the definition is safe.

Separate unengaged from never engaged

A customer who bought last month but stopped opening newsletters is not the same as a profile that received repeated messages and never opened, clicked, viewed a product, or ordered. Use separate segments for different evidence states instead of forcing one threshold across the database.

Klaviyo's current cleaning documentation describes a stricter never-engaged audience that combines marketing eligibility, message exposure, zero engagement, zero product views, and zero orders. The exact criteria still need to match the data available in the account. If a Shopify order event, historical ESP click, or site event is missing, fix the source or exclude the uncertain profile from suppression review.

The BFCM segmentation guide covers campaign audiences and exclusions. The sunset flow has a narrower job: give a defensible inactive cohort one final chance to engage, then mark the remaining profiles for operator review.

Make engagement remove the profile before the next action

Klaviyo's sunset-flow documentation uses a segment-triggered flow with filters that check whether a profile opened or clicked after entering. The purpose is simple: a person who re-engages should leave the sunset path before later messages or the final property update.

Do not rely on the trigger segment alone. Klaviyo checks profile filters at entry and again before flow actions, so use current eligibility checks throughout the journey. Include the engagement signals you trust, recent purchase and site behavior where available, consent, customer-service exclusions, and any active promotion state that should stop the flow.

Treat opens cautiously. Klaviyo notes that Apple Mail Privacy Protection can inflate open activity. A click, a product view, a checkout, or an order may be stronger evidence for a business decision when those events are captured reliably. Document the hierarchy instead of changing it during the launch.

Keep the final sequence short and honest

The message should make the choice clear: remain subscribed through a meaningful action, change preferences when that option exists, or unsubscribe. Avoid disguising a routine promotion as a deliverability check. A large discount may generate a click without restoring a durable relationship, and it can train the audience to wait for another rescue offer.

Klaviyo recommends a limited sunset sequence rather than repeated contact with inactive profiles. Set the number of messages, delay, qualifying action, destination, preference option, and final grace period before launch. The copy, links, and preference centre should work on mobile and should not promise a change that the data workflow cannot apply.

• A test profile qualifies from each approved inactivity path.
• An open or click after entry prevents later sunset actions when that signal is trusted.
• A recent order, site event, or protected customer state removes the profile when required.
• Unsubscribe and preference links write the expected consent state.
• The final property update occurs only after the full grace period and every filter check.

Protect the BFCM campaign calendar while the flow runs

A sunset flow cannot clean the audience if the same profiles keep receiving ordinary campaigns. Add the unengaged or sunset cohort to campaign exclusions while the flow is active, then test those exclusions against scheduled BFCM sends. Klaviyo's list-cleaning documentation explicitly supports excluding unengaged segments from campaign audiences.

Coordinate the flow with the BFCM sending strategy, winback, welcome, cart, browse, VIP, and post-purchase journeys. Name which messages are allowed to interrupt sunset eligibility and which should remain excluded. A service message or recent order can change the decision; another promotional email usually should not happen by accident.

Finish the decision window before peak campaign volume rises. Working backward from the final review date creates room for entry, messages, engagement, a grace period, cohort inspection, and any correction. Launching the sunset flow during BFCM turns audience hygiene into another live-event dependency.

Separate email suppression from other channels

Klaviyo states that email suppression stops email marketing, not SMS or push notifications. In a multichannel flow, apply email engagement rules at the email action when the customer can still be eligible for another channel. Do not let weak email engagement silently remove a valid SMS or push path.

Build a channel-state table with email consent, SMS consent, push eligibility, engagement source, quiet-hour or market constraints, unsubscribe behavior, and the owner of each rule. Test email-only, SMS-only, multichannel, and fully opted-out profiles separately. The outcome should reflect the permission actually granted, not the channel that was easiest to configure.

Review the cohort before suppression

A completed sunset flow should produce a reviewable cohort, not an unexplained deletion. Klaviyo's documented pattern adds a profile property after the final delay, then uses a segment of that property for suppression. Bulk suppression applies to current segment members; profiles who join later are not automatically included in that completed action.

Before applying suppression, save the cohort count, segment definition, observation time, sample profiles, protected exclusions, and reviewer. Compare it with the entry count and explain every exit: engaged, purchased, unsubscribed, failed a filter, still waiting, or marked for suppression. Unexpected movement is a reason to pause, not a reason to broaden the segment.

Keep recovery practical. Preserve the segment definition and evidence used for the decision. If a source event was missing or a filter was wrong, stop new entries, remove the affected cohort from review, repair the data or logic, and retest. Suppression is an account-wide email state, so the review deserves the same discipline as a production release.

Monitor the release and close it cleanly

Monitor segment growth, flow entries, waiting profiles, sends, clicks, trusted engagement events, unsubscribes, filter failures, property updates, campaign exclusions, and the final suppression cohort. Set stop conditions for sudden cohort growth, known customers entering, exclusions failing, engagement not removing profiles, or a property update occurring before the grace period ends.

After the review, verify that suppressed profiles no longer receive email marketing and that eligible SMS or push states remain intact. Keep campaign exclusions in place for any profiles still waiting or under investigation. Record what changed, who reviewed it, and when the next recurring list-cleaning review will occur.

How Lake House Group approaches BFCM sunset flows

Lake House Group treats list cleaning as a connected Klaviyo and Shopify operating decision. We align event history, segmentation, flow logic, campaign pressure, customer state, channel consent, suppression review, monitoring, and recovery before the BFCM calendar accelerates.

Related reading

• Klaviyo BFCM segmentation
• Klaviyo BFCM sending strategy
• Klaviyo data hygiene for Shopify
• Klaviyo winback flow for Shopify
• Klaviyo BFCM welcome flow