Who this is for: Recruiters and managers who want to understand exactly how Recruiterflow counts opens, responses, meetings, and deliveries — so they can trust the numbers and not misread them.

Sequence analytics use a unique recipient model — each person counts once per metric per channel, regardless of how many steps or interactions they've had. If you're used to tools that count every event (every open, every click, every send as a separate number), the figures here will look smaller. They're not wrong — they're more meaningful. A 12% reply rate means 12% of people you reached actually wrote back, not that 12% of your total sends received a reply.

This article explains exactly how each metric is computed, where edge cases come up, and how attribution windows work.

Definition: The number of unique recipients for whom at least one outbound step was successfully completed.

What counts as "successfully completed":

What does NOT count:

This is your denominator. All percentage metrics (Open Rate, Reply Rate, Bounce Rate) are calculated as a share of Recipients Contacted — not total recipients added to the sequence.

Definition: A recipient is counted as "opened" once they open at least one tracked message — across any channel, across any step.

Counting rule: Each recipient contributes at most once to the Opened count for a sequence, regardless of how many emails or steps they opened. If a recipient opens Step 1 and Step 3 emails, they count as one opened recipient.

Tracking dependency: Open tracking must be enabled at the account level in Settings → Automation Settings → Email Tracking. If tracking is disabled, all open-related metrics and columns are hidden across the entire Sequences module — including the Overview tab, Channel Performance Report, Step-wise Report, and the Sequences Performance Report.

Definition: A recipient is counted as "responded" once they reply via any channel within 90 days of a step executing.

Counting rule: Each recipient contributes at most once to the Responded count, per channel, per sequence. The channel column that gets marked is determined by which channel the reply arrived through — not which steps exist in the sequence.

Attribution window: 90 days from the date any step in the sequence executed for that recipient. Replies received after 90 days are not counted.

The sequence stops the moment a reply arrives. The channel that delivered the first reply gets a tick mark in the corresponding Responded column. No further tick marks are added — because the sequence has stopped and no more steps execute.

A recipient can only have one Responded column marked when Stop on Response is ON.

The sequence continues running after a reply. Additional tick marks accumulate across columns as new responses arrive through different channels — but with a specific rule to prevent double-counting noise:

A new tick mark only appears if at least one further sequence step executed after the previous response was received.

In practice:

But if the recipient replies twice via email before Step 4 executes, only the first email reply generates the tick mark. The second email reply does not create an additional mark — there was no intervening step.

Responses are attributed to the channel through which they arrived, not the steps in the sequence. If a sequence has only email steps but a recipient replies via LinkedIn (because they found the sender's profile independently), the LinkedIn Responded column is marked ✓.

Definition: A meeting is attributed to a sequence if it was created in Recruiterflow for a recipient during the sequence period, plus a 90-day window after the last step executes.

Attribution window: Sequence start → last step execution date + 90 days.

Counting rule: Each recipient contributes at most once to the Meetings Booked count per sequence, regardless of how many meetings were created for them.

What qualifies: Any meeting created via Recruiterflow for the recipient during the attribution window. The meeting does not need to be explicitly linked to the sequence — it's inferred by timing.

Definition: Recipients for whom all email attempts bounced ÷ Recipients Contacted.

Note the distinction: a recipient who had one email bounce and one email deliver is not counted in the bounce rate — they were successfully contacted. Only recipients where every email attempt failed are included.

In the Sequences Performance Report (the workspace-wide view), metrics are aggregated at the unique recipient level across all sequences. A recipient in three active sequences who responds to all three counts as one responded recipient — not three.

In the per-sequence Overview tab, metrics are scoped to that sequence only. The same recipient in two different sequences appears once in each sequence's count — that is expected and correct.