Resource guide
How to clean a Klaviyo list without losing good subscribers
List cleaning is a reviewed audience decision, not a command to delete everyone who has not opened recently. Protect permission history and useful customer relationships while reducing sends to people who are not eligible or no longer interested.
Check consent and data history before engagement
Confirm how subscribers joined, whether they can currently receive email marketing, and which opt-outs, complaints and hard-bounce suppressions already apply. Do not restore suppressed profiles merely because they have purchased or appear in a customer export. Never buy a list or treat address validation as consent.
Check whether the account contains a complete engagement history. A recent platform migration, broken event sync or short observation period can make a good subscriber look inactive. Missing history means Unknown, not never engaged. Preserve consent and suppression provenance when reviewing or moving records.
Use reviewed engaged and unengaged segments
Build review segments using eligibility, time subscribed, messages actually received and several available behaviors. New subscribers who have not had a fair chance to engage should not be grouped with long-standing recipients who repeatedly ignored eligible sends.
Choose the observation window and minimum message count to match the store’s cadence and buying cycle, then inspect the rule and a small authorized sample. A 90-day window is not a universal deletion rule. A seasonal customer or infrequent purchaser may need a different interpretation.
Do not let privacy-inflated opens decide who stays
Apple Mail Privacy Protection and similar features can create opens without a person reading the message. Use non-privacy opens where the platform can distinguish them, but do not interpret their absence as proof that someone never read an email.
Verified clicks, relevant site activity and purchases can be stronger evidence of a relationship than opens alone. Clicks can still come from automated scanners, and purchases can occur without email influence. Use the combined history cautiously; neither a click nor a purchase overrides an unsubscribe.
Understand suppression versus deletion
Excluding a segment from a campaign limits that send. Email suppression prevents marketing sends to the suppressed profiles within the platform’s applicable rules while retaining the profile history. Check the channel scope: email suppression does not necessarily change SMS or other channel consent.
Deletion removes the profile and associated history according to the platform’s deletion behavior. It is not the routine first step for deliverability cleanup. Privacy-erasure requests have a different purpose and should follow the store’s appropriate privacy process; this guide is not legal advice.
Before any bulk action, review the exact segment, counts, reasons and intended effect with the authorized account owner. Do not export and reimport profiles to bypass suppression, or recklessly mass-delete records to improve a headline engagement percentage. Use secure access, not customer lists emailed to a service provider.
Re-engage cautiously, if it is appropriate at all
A re-engagement message is optional, not a right to contact everyone one more time. Consider only eligible, permission-based profiles with defensible history. Do not email unsubscribed, complained, hard-bounced or otherwise suppressed contacts to ask them to opt back in.
If sender reputation is already under repair, postpone risky old-list outreach and follow the platform’s repair guidance. Where re-engagement is justified, use a small reviewed group, a clear purpose and a stopping rule. Do not start a large old-list blast before a holiday promotion.
Review actual delivery, complaint and unsubscribe evidence before considering another group. Lack of reliable data is not a pass. Obtain written approval before changes or sends; a cleanup recommendation is not automatic authorization.
Keep a record and review again
Record the segment definition, observation period, available history, counts, approved action and date. Segments change as profiles enter and leave; a one-time action on current members does not prove future cleanup will happen automatically.
Keep suppression enforcement active across later campaigns and flows. Report missing metrics as Unavailable rather than zero, and investigate sudden bounce or complaint increases instead of assuming the cleanup solved every delivery issue. This educational guide does not promise inbox placement or add a major deliverability-repair project to the managed service.
Platform references
Editorially reviewed November 14, 2026. Platform settings can change; verify the current documentation and your own account before making changes.