«We have dashboards on monday already.»
On the boards' own columns. This joins deals to leads on the contact detail, which is a different mechanism and therefore a check.
Para monday CRM
Export deals and leads from your boards, reconcile them once in the file, and get a single revenue-by-source answer.
Sin clave de API Nada que instalar en monday CRMNada que instalar Sin tarjeta de créditoSin tarjeta
CloseRev reads a monday CRM export of won deals — the contact's phone or email, the amount and the date — and matches it against the leads that produced them. Because monday boards are configured by the teams that use them, the same company often has several boards with different column names describing the same thing, and the export is where that finally has to be reconciled. Revenue with no traceable lead is reported as Direct / Unknown.
Comprobado por última vez con la documentación del propio monday CRM el 24 de septiembre de 2026.
La brecha
Each team built the board it needed. None of them can be added together.
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.
Whichever column holds it — the name varies by board, which is exactly why the join runs on the value rather than the column.
The won amount. Whatever the column is called, it needs to mean the same thing on every board you export.
When the item moved to won. Keep the created date too if the board records it.
The board's own source or channel column, exported as data to be checked rather than assumed correct.
Paso a paso
Escrito para quien tiene monday 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.
Do not merge them inside monday first. Reconciling in the export file is where the differences become visible rather than averaged away.
One board's number may be annual and another's the contract. Fix that once, in the file, and write down which you chose.
Including the ones that went nowhere, because they are what the channel cost.
Long enough for the cycle to complete and for board-level quirks to show up as patterns rather than noise.
The join runs on the phone and the email, normalised, so differing column names across boards stop mattering.
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 Agencias de marketing, no de una cuenta de monday CRM.
| Canal | Proporción | Ventas | Ingresos |
|---|---|---|---|
| Google Ads | 61 | $186,400 | |
| Meta Ads | 48 | $93,200 | |
| Email marketing | 19 | $46,600 | |
| Directo / Desconocido | 44 | $97,400 |
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 reason a team adopts monday is that anyone can build the board they need, and that is a genuine strength for running work.
It is a weakness the moment somebody asks a question that spans boards, because 'value', 'deal size' and 'contract' were defined independently by people solving different problems.
Reconciling them in an export is not a workaround; it is the only place the definitions can be compared side by side without rebuilding everybody's board.
The report ranks on one definition, stated once, which is what makes the answer defensible when a board owner disagrees with it.
It also makes the disagreements explicit, and those are usually worth fixing at the source afterwards.
Matching records across boards by an internal identifier breaks as soon as somebody duplicates an item or rebuilds a board.
A phone number and an email survive all of that, because they belong to the person rather than to the tool.
Normalisation runs first — country codes, punctuation, casing — and the report shows which key joined each row, so the match can be inspected rather than trusted.
That property is what lets this work across several boards, an old spreadsheet and a lead file from an advertising platform at the same time.
It is also why nothing here needs an integration, an API key or a developer.
Most boards have a source or channel column, filled in by whoever created the item, and it is exactly as reliable as that description suggests.
Joining leads to deals on the contact detail gives a second view of the same question, produced by a different mechanism.
Where the two agree, the column can be trusted. Where they disagree, the report shows the gap rather than silently preferring one.
In practice the disagreement clusters — one board, one team, one period — which usually points at a process change nobody documented.
Finding that is worth as much as the ranking itself.
An item moved to a won group carries whatever value somebody typed, at whatever moment they decided the deal was done.
Where the business invoices from another system, exporting revenue from there instead gives the collected figure and turns the deal value into a forecast again.
The gap between them is not distributed evenly across sources, and measuring it once tells you whether it is worth the second export permanently.
Where only the board figure exists, the report uses it and labels it as such rather than implying a precision the data does not have.
Preguntas justas
On the boards' own columns. This joins deals to leads on the contact detail, which is a different mechanism and therefore a check.
Then the reconciliation takes minutes and you have evidence rather than an assumption.
No, and deliberately: it reads files you exported, so nothing here has access to your workspace.
No. It reads exported files, so your boards, automations and workspace stay untouched.
Won deals with a contact detail, a value and a date, plus leads with their source.
That is fine — the join runs on the phone and email values, not on column names. The values still have to mean the same thing.
No. Export them separately so the differences are visible rather than averaged away.
Decide once, apply it to the file and record the choice. Comparing the two as though they matched is the failure to avoid.
Yes, they are what the channel cost. A revenue-only view flatters the highest-volume source.
A year, so the cycle completes and board quirks show as patterns rather than noise.
That is the point. The join gives a second view and the report shows where the two disagree.
Not necessarily. Where you invoice elsewhere, export from there and the difference becomes measurable.
Any revenue with no traceable lead. Its size is stated rather than distributed.
A contact detail, an amount and a date, plus a source label. No board content, no updates, no files. Encrypted in transit and at rest and deleted with the import.
Revenue per source across every board on one definition, beside what the source columns claim, with 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.
monday 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 monday 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.