“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.
For monday CRM
Export deals and leads from your boards, reconcile them once in the file, and get a single revenue-by-source answer.
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.
Page updated September 24, 2026.
The gap
Each team built the board it needed. None of them can be added together.
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.
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. The created date belongs in the lead file, where it decides which lead came first.
The board's own source or channel column, exported as data to be checked rather than assumed correct.
Step by step
Written for somebody with monday CRM open in the next tab. Report names vary by edition, so each step says what to look for.
Do not merge the boards inside monday. Combine the exports into one sales file and one lead file, which 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, normalized, so differing column names across boards stop mattering.
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 Marketing Agencies page — not from a monday CRM account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 61 | $186,400 | |
| Meta Ads | 48 | $93,200 | |
| Email marketing | 19 | $46,600 | |
| Direct / Unknown | 44 | $97,400 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
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 can be 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.
Normalization runs first — country codes, punctuation, casing — and the matched-records export 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, once they are combined into one lead file.
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 deals to leads on the contact detail — with the leads taken from the systems that captured them — 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, setting the report beside the board's own figures shows the gap rather than silently preferring one.
Where the disagreement clusters — one board, one team, one period — it 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, use it and say so when presenting the result, rather than implying a precision the data does not have.
Fair questions
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.
Not inside monday. Export each board, then combine the exports into one sales file and one lead file, where 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. There is no window to set.
That is the point. The join gives a second view; set it beside the board's own source figures and the disagreements show.
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, to set beside what the source columns claim, with 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.
monday 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 monday CRM, no API key, and no need to have been tracking anything until now. Last year works as well as this month.