«We already report revenue by lead source in Zoho.»
You report revenue by what the field says. This checks the field against a join on the contact detail, which is the first time most teams see the difference.
Para 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.
Sin clave de API Nada que instalar en Zoho CRMNada que instalar Sin tarjeta de créditoSin tarjeta
Zoho CRM is one of the few systems in this catalogue 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 is also the first honest audit most teams get of whether the lead source field has been filled in accurately. Revenue with no traceable lead is reported as Direct / Unknown.
Comprobado por última vez con la documentación del propio Zoho CRM el 24 de septiembre de 2026.
La brecha
Every record has a lead source. Nobody can say when it was last set deliberately rather than left on the default.
Qué se vendió, a quién y por cuánto.
El clic, la palabra clave, la llamada y cuánto costó cada uno.
El archivo
Tres cosas sostienen la coincidencia: quién, cuánto y cuándo. Todo lo demás es opcional y solo cambia cómo se puede desglosar el informe.
On the contact or lead record. It is what joins the two exports and it is usually cleaner than either module's own linkage.
Closed-won deals with their value. Pipeline is a forecast, not revenue.
When the deal was marked won. Keep the lead created date too, so the cycle length is visible.
The field itself — exported as data to be checked rather than trusted, which is the point of this page.
Paso a paso
Escrito para quien tiene Zoho CRM abierto en la pestaña de al lado. Los nombres de los informes varían según la edición, así que cada paso indica qué buscar.
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, normalised, with unmatched deals and unmatched leads both kept visible.
Lo que recibe
Ingresos por canal, el número de ventas detrás de cada cifra y un grupo honesto para las que nadie pudo rastrear. Cifras de ejemplo, del caso práctico de la página SaaS B2B, no de una cuenta de Zoho CRM.
| Canal | Proporción | Ventas | Ingresos |
|---|---|---|---|
| Google Ads | 18 | $720,000 | |
| LinkedIn Ads | 21 | $930,000 | |
| Email marketing | 12 | $420,000 | |
| Directo / Desconocido | 24 | $930,000 |
Las ventas sin coincidencia quedan en Directo / Desconocido. Nunca se reparten entre los canales pagados para que el total se vea mejor.
El argumento
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.
Joining deals to leads on the contact detail rather than on the source field gives a second, independent view, 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 most source reports quietly exclude the failures.
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 produces plenty of deals and enormous handling cost, which is a real thing and 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, the report uses it and says so, 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.
Carrying the lead created date through lets the report group by when the lead arrived, which is the grouping a spending decision actually needs.
It also gives the cycle length per source, and sources differ on it far more than most teams expect.
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.
Preguntas justas
You report revenue by what the field says. This checks the field against a join on the contact detail, which is the first time most teams see the difference.
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 that produces a second, independent view, and 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 and the gap between the two becomes measurable.
A year, so the cycle completes and seasonal effects average out.
Yes, where the created date is exported, and that is the grouping a budget needs.
Yes, and sources differ on it much more than most teams expect.
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, beside what the source field claims, with the disagreement between them shown and everything unmatched kept visible.
Por sector
Cómo se ve el informe una vez cargada la exportación, escrito para cada uno.
Otros sistemas
¿Usa más de un sistema o está comparando? El método es el mismo; las columnas, no.
Zoho CRM y los demás nombres de productos y logotipos de esta página pertenecen a sus propietarios y se muestran para identificar el software del que procede un archivo. CloseRev no está afiliada a ellos ni cuenta con su respaldo, y no se conecta a ninguno: lee un archivo que usted exporta.
Empiece hoy
Nada que instalar en Zoho CRM, sin clave de API y sin necesidad de haber rastreado nada hasta ahora. El año pasado funciona igual de bien que este mes.