The default candidate recipe
The default follows Klaviyo's active profile management guidance updated March 30, 2026. A profile is a candidate only when every group below is true.
The all-time windows make the recipe stricter than a typical 90-day or 180-day engagement segment. A person with any recorded open, click, site visit, product view, checkout, or order is excluded.
How metric sources are resolved
Klaviyo accounts can expose several metrics with the same display name. Commerce events may arrive from more than one storefront or integration. Deadweight keeps those sources separate.
For a zero-event condition, each matching source must be zero. For Received Email, any recognized Klaviyo email source can satisfy the minimum. The audit does not silently choose an arbitrary duplicate metric.
Fail closed. If a required metric cannot be found or interpreted safely, the recipe is not built. Missing data is not treated as zero activity.
What the free audit can do
The first OAuth connection requests account, metric, and segment read access plus segment write access. Segment write is used to create or update the named review segment. The token does not include subscription write access, so it cannot bulk suppress profiles.
The stored audit result uses aggregate counts and Klaviyo object identifiers. Deadweight does not need a raw subscriber email export to show the candidate count.
What changes before cleanup
Cleanup is a separate action. It requires an authenticated workspace owner, a paid cleanup entitlement, expanded OAuth scopes, and a typed approval for the displayed candidate count.
Before suppression starts, Deadweight records the current members in a temporary static list inside the connected Klaviyo account. That list is the rollback target. The profile snapshot stays in the merchant's Klaviyo account instead of becoming a second email database.
How suppression is executed
- Create and populate the rollback list from current segment members.
- Submit Klaviyo's bulk profile suppression job against the approved static snapshot list.
- Poll the job status and record total, completed, and skipped counts.
- Wait for Klaviyo's billable profile count to finish processing.
- Compare the final count with the baseline and report plan eligibility separately.
A completed job with skipped members is reported as partial, not silently labeled successful.
What rollback can and cannot do
Rollback submits Klaviyo's bulk unsuppression job against the saved list. It removes the manual suppression applied by the cleanup where Klaviyo allows it.
Rollback cannot restore consent withdrawn by an unsubscribe, reverse a bounce or suspicious-email suppression, or override another deliverability restriction. Those states remain protected by Klaviyo.
How savings are described
Before cleanup, any dollar figure is labeled an estimate or planning scenario. After cleanup, Deadweight can verify the processed billable count. The final invoice still depends on the plan tier selected, auto-downgrade eligibility, renewal timing, taxes, and contract terms.
That is why the product separates three numbers: candidate count, processed billable count change, and invoice result.
Primary references: Klaviyo active profile management, Klaviyo billing, and suppression and deletion.
See the output before connecting
The sample shows the count, rule, decisions, and billing checkpoint.