“We already report revenue by lead source in Zoho.”
You report revenue by what the field says. Leads taken from the systems that captured them, joined on the contact detail, give a second answer to set beside it — and the difference is the finding.
For Zoho CRM
Export won deals and leads from Zoho CRM, join them on the contact detail, and see what the source field has actually been recording.
Zoho CRM is one of the few systems in this catalog that holds both halves of the match: the lead with its source, and the deal that closed with its amount. CloseRev reads an export of won deals and an export of leads, joins them on the contact detail, and reports revenue by source — which, with the leads taken from the systems that captured them, is also an honest audit of whether the lead source field has been filled in accurately. Revenue with no traceable lead is reported as Direct / Unknown.
Page updated September 24, 2026.
The gap
Every record has a lead source. Nobody can say when it was last set deliberately rather than left on the default.
What was sold, to whom, and for how much.
The click, the keyword, the call, and what each one cost.
The file
Three things carry the match: who, how much, and when. Anything else is optional and only changes how the report can be sliced.
On the contact or lead record. It is what joins the two exports, and it can be cleaner than either module's own linkage.
Closed-won deals only, with their value; the stage is not read, so filter before exporting. Pipeline is a forecast, not revenue.
When the deal was marked won. The lead created date belongs in the lead file, where it decides which lead came first.
The field itself, uncleaned. The report groups by its values, so a default left on every record shows up as one large channel — which is the check this page is about.
Step by step
Written for somebody with Zoho CRM open in the next tab. Report names vary by edition, so each step says what to look for.
One row per deal with a contact detail, the amount and the close date.
Including leads that never converted. A source's cost is spread across everything it produced.
Its untidiness is a finding. Cleaning it before the report hides how much of the pipeline has no real source at all.
Long enough for the cycle to complete and for seasonal distortion to average out.
The join runs on the phone and the email, normalized, with unmatched deals and unmatched leads both kept visible.
What comes back
Revenue by channel, the count of sales behind each figure, and an honest bucket for the ones nobody could trace. Sample figures, from the worked example on the B2B SaaS page — not from a Zoho CRM account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 18 | $720,000 | |
| LinkedIn Ads | 21 | $930,000 | |
| Email marketing | 12 | $420,000 | |
| Direct / Unknown | 24 | $930,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
The lead source on a CRM record is usually set by whoever created it — a salesperson mid-call, an import, a form mapping written two years ago.
None of those are wrong on purpose, and collectively they produce a field that is roughly right and precisely unreliable, which is the worst combination for a budget decision.
Taking the leads from the systems that captured them — the call tracker, the form tool, the ad platform — and joining them to deals on the contact detail gives a second, independent view. Set it beside Zoho's own source report and the disagreement between the two is the useful output.
Where they agree, the field can be trusted for that channel. Where they do not, you have found a data problem that was quietly steering spend.
This is not a criticism of the team. It is what happens to every free-text or picklist field that nobody is measured on.
A CRM makes it very easy to report on won deals and slightly harder to report on everything that never became one, so source reports tend to exclude the failures quietly.
A channel producing two hundred leads and four deals then looks identical to one producing twelve leads and four deals.
Exporting leads regardless of outcome puts both numbers side by side — revenue and volume — which is the comparison that changes budgets.
It also surfaces the channel that needs a great many leads per deal — a handling cost that is invisible in a revenue-only view.
The report keeps unmatched leads visible for exactly this reason rather than discarding them as noise.
A deal marked closed-won carries the value the salesperson entered, which may be the contract, the first year, or an optimistic round number.
Where the business also has an invoicing system, exporting from that instead gives the collected figure, and the gap between the two is worth measuring once.
Channels do not distort that gap evenly: a source producing discount-led buyers will show a wider gap between won value and collected value.
Where only the CRM figure exists, use it and say so when the numbers are presented, rather than implying a precision the file does not have.
Being explicit about which number is being ranked is most of what makes a report defensible.
For anything with a considered purchase, deals closing now were created months ago, and grouping revenue by close date attributes it to whatever ran this quarter.
The report dates revenue by the close as well; the matched-records export carries the lead created date beside it, which allows grouping by when the lead arrived — the grouping a spending decision actually needs.
The same two dates give the cycle length per source, worked out from the export, and sources can differ on it a great deal.
That number has its own use: a channel with a six-month cycle cannot be switched on in response to a slow quarter, and knowing which ones can is a planning input.
Fair questions
You report revenue by what the field says. Leads taken from the systems that captured them, joined on the contact detail, give a second answer to set beside it — and the difference is the finding.
Then the two views will agree and you will have evidence for that, which is worth more than the assumption.
Because they are what the channel cost. A revenue-only view makes a wasteful source look efficient.
No. It reads exported files, so your records, notes and pipeline stay where they are.
Closed-won deals with a contact detail, an amount and a close date, plus leads with their source.
No. Its untidiness is part of the finding, and cleaning it beforehand hides how much pipeline has no real source.
Because a lead file from the systems that captured each lead, joined on the contact detail, gives a second, independent view to set beside the field. Where the two disagree you have found something.
Yes. They are the channel's cost, and excluding them flatters the highest-volume source.
Not always. Where you also have invoicing, export from that; running the import once each way makes the gap between the two measurable.
A year, so the cycle completes and seasonal effects average out. There is no window to set.
From the matched-records export, where the created date sits beside the close date; the report itself dates by the close. That grouping is the one a budget needs.
Not as a figure. The matched-records export carries the lead date and the close date on every match, so it can be worked out per source, and sources can differ on it a great deal.
Any revenue with no traceable lead. Its size is reported rather than distributed.
A contact detail, an amount and a date, plus a source label. No notes, no emails, no attachments, no pipeline detail. Encrypted in transit and at rest and deleted with the import.
Revenue per source from the join, to set beside what the source field claims, and everything unmatched kept visible.
By trade
What the report looks like once the export is in, written for each one.
Other systems
Running more than one system, or comparing? The method is the same and the columns are not.
Zoho CRM and the other product names and logos on this page belong to their owners and are shown to identify the software a file comes from. CloseRev is not affiliated with or endorsed by them, and connects to none of them: it reads a file you export.
From the blog
The export is the part of an attribution project that everyone treats as trivial and that determines whether the whole thing works. Here is the field list, the date-range trap, the deduplication rule, and the six columns to leave out on purpose.
Read the articleEvery attribution vendor quotes a match rate and none of them define it the same way. Here is what the number actually measures, what range is honest for a mid-market business, and the three ways the figure gets inflated before it reaches your slide.
Read the articleEvery revenue-by-channel report is a sum grouped by one field: the lead source. If that field is free text, half the revenue lands on lines like "Phone", "Website", "Other" and blank, and the channels that bring customers in by phone look like they lose money. Here is how to set the field up as a short fixed list, who fills it in and when, how tracking numbers, hidden form fields and booking links fill it automatically, how to settle conflicting sources, and how to audit it every month.
Read the articleStart today
Nothing to install in Zoho CRM, no API key, and no need to have been tracking anything until now. Last year works as well as this month.