Skip to content
Analytics

Analytics & attribution

See which channel, mailbox, sequence, and step actually drives revenue.

Analytics reports the outbound funnel per channel, per mailbox, per sequence and per step, with spend attributed in INR. Every number is read at query time from the same channel_touches, sends and email_events tables the workers write to, so there is no nightly ETL job and no stale snapshot to reconcile.

What you get
  • ·Cohort-based reply rate over time
  • ·Per-mailbox health score history
  • ·Per-channel spend in INR
  • ·Step-level conversion funnel
  • ·Export to CSV / Sheets
Cross-channel attribution · 30 days
Touches sent
47,213
Replies
1,842
Reply rate
3.9%
Meetings
412
Cost / meeting
₹284
ROI vs spend
8.4×
Channel attribution · meetings sourced
Email
18445%
Call
10225%
LinkedIn
7819%
WhatsApp
328%
SMS
163%
How it works

The detail.

Reports tied to the same data the workers read

Every metric on the dashboard reads from the same channel_touches, sends, and email_events tables the workers write. No nightly ETL, no stale snapshot.

Per-mailbox health, not a campaign-level average

A campaign-level reply rate hides the one mailbox that is quietly burning. Autocloz keeps a health score per mailbox with its history, so a single sender drifting toward the spam folder shows up as its own line instead of disappearing into the campaign average — which is the difference between pausing one mailbox and rebuilding a domain.

Attribution that survives a multi-channel sequence

When a lead gets an email on day 0, a dial on day 2 and a LinkedIn invite on day 4, a single-tool report credits whichever tool the lead happened to answer in. Because every touch is written to one ledger, the step-level funnel shows the whole path — so you can see that the dial is what earned the reply the email got credit for.

The gotcha: cohorts, not calendar weeks

Reply rate by calendar week moves whenever send volume moves, which makes a ramp look like a decline. The reply-rate series here is cohort-based — leads are grouped by when they entered the sequence, so the curve tracks how a cohort responded rather than how much you sent that week.

FAQ

Specific to this feature.

Do I need a separate BI tool to report on outbound?

+

No. Per-channel, per-mailbox, per-sequence and per-step reporting is built in, and every table exports to CSV or Sheets if you want to take the numbers into a spreadsheet or a warehouse.

How fresh are the numbers on the dashboard?

+

They are read at query time from the live tables the workers write — channel_touches, sends and email_events. There is no nightly ETL step, so a send that happened a minute ago is already counted.

Is channel spend reported in INR?

+

Yes. Spend attribution is INR-aware, so provider cost sits next to reply and meeting counts in the same currency you are billed in, with no conversion step in between.

Can I see which step of a sequence loses people?

+

That is what the step-level conversion funnel is for: each step shows what entered it, what advanced, and what dropped, so a follow-up that kills the thread is visible as a step rather than inferred from a falling total.

In depth

The full story.

Most outbound teams end up reporting from three places at once: the sending tool's dashboard, the dialer's call log, and a spreadsheet somebody maintains by hand. The three disagree, because each one only sees its own touches and none of them can tell you what the sequence did as a whole. Autocloz avoids that split by writing every channel's activity to one set of tables and reporting off those tables directly.

The practical questions outbound analytics has to answer are narrower than "how are we doing": which mailbox to pause this week, which step to rewrite, and which channel deserves next month's budget. Per-mailbox health history answers the first, the step-level funnel answers the second, and per-channel spend against replies and meetings answers the third — each from the same underlying rows, so the three answers stay consistent with each other.

Pairs well with