Cold email unsubscribe rate: distinguish people from request events

Define the decision

A recipient can click an unsubscribe link more than once or request removal in a reply. Current contact status can also reflect an earlier interaction outside the selected campaign. The definition must say whether the measure describes new events during a period or current excluded people in a cohort.

Work through the procedure

1. Define the cohort of contacted people and the observation cutoff.
2. Review qualifying opt-out evidence and deduplicate people across repeated requests.
3. Calculate the contact-level rate and keep the scope of attribution explicit.
4. Compare the manual definition with the application's metric before presenting them side by side.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

200 contacted people
4 people request no further outreach
One person repeats the request twice
Unique opting-out people: 4
Contact opt-out rate = 4/200 = 2%
Request-event count would answer a different question.

Read the result

The repeated request should matter operationally, especially if the first request was not handled, but it should not inflate the unique-person numerator. If a current status predates this campaign, do not automatically attribute that opt-out to the campaign's copy without event evidence.

Check before moving on

1. Verify the exclusion was actually applied, not merely counted.
2. Keep request time separate from report-generation time.
3. Review overlapping campaigns before assigning a single cause.

Limits and next action

Zintara's current overview unsubscribe total counts distinct leads currently unsubscribed within the send cohort; it is not a count of repeated link requests. This guide describes a separate manual contact-rate definition and is not jurisdiction-specific legal guidance.

Source: Zintara product context; calculations are defined in this guide