“We already push values back into CallTrackingMetrics.”
That works exactly as well as somebody remembers to do it, for the deals they remember. This reads the money from the system that already holds it.
For CallTrackingMetrics
CallTrackingMetrics attributes the contact. Match those contacts against your sales export and rank channels on the money rather than on the volume.
CloseRev reads a CallTrackingMetrics export of calls and form submissions — the caller's number or the submitted email, with the source, campaign and keyword attached — and matches those people against your closed-sales export. CallTrackingMetrics answers which campaign produced the contact; this answers which contacts produced revenue, which is the half no call platform can see. Contacts that never became revenue simply do not appear in the revenue column.
Page updated September 24, 2026.
The gap
The dashboard says a campaign produced ninety-one conversions last month. Nobody in the building can tell you how many of them bought, or what they were worth.
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 call record and the form record. Calls give you a number captured by the network rather than typed by anyone, which is the cleanest join key in this whole catalog.
The attribution fields on the contact. This is the half CallTrackingMetrics does well and the half your sales system has never heard of.
Used to order the match where somebody appears more than once: the earliest contact takes the credit, so a repeat caller does not move it to a later campaign.
The match does not read it. Use it to filter the export before upload — every qualified call, say — rather than expecting the report to rank on it.
Step by step
Written for somebody with CallTrackingMetrics open in the next tab. Report names vary by edition, so each step says what to look for.
Both are contacts and both belong in the lead file. Exporting only calls is the most common way to make paid search look better than paid social, because one of them converts by phone and the other by form.
Source, campaign and keyword are the point of the file. A lead export without them tells you a stranger called, which you knew.
From whatever holds the money — job management, practice management, a CRM, or the accounting system. Customer phone or email, amount, date.
The contact comes first and the money lands later, sometimes much later. A sales file starting where the call file starts will miss the revenue those calls produced.
The join runs on the phone and the email, normalized on both sides rather than compared as strings.
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 HVAC Companies page — not from a CallTrackingMetrics account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 38 | $241,400 | |
| Meta Ads | 24 | $61,600 | |
| Email marketing | 19 | $46,200 | |
| Direct / Unknown | 63 | $164,300 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
CallTrackingMetrics is unusual in tracking both halves properly. Most businesses take calls and forms, and most compare them by counting: ninety calls, forty forms, therefore the phone matters more.
Counting is the wrong comparison and everybody suspects it. A form fill from somebody researching at eleven at night and a call from somebody standing in their flooded basement are not the same event, and no volume metric will ever say so.
Ranking both on closed revenue puts them on one axis. The split that comes out need not be the one the team expected, and it is the number that should decide where the next thousand goes.
Scoring and tagging exist because somebody has to decide which leads were any good before the money arrives. It is a reasonable thing to do and it is systematically biased in a direction nobody notices: long, engaged, articulate conversations score well whether or not they buy.
When you rank channels by qualified leads in CallTrackingMetrics and by revenue here, the two lists can differ. That difference is the useful output. It separates the channel filling the phone with conversation from the channel filling it with customers, and those are frequently not the same channel.
A call log carries existing customers chasing a job, suppliers, recruiters, wrong numbers and outright spam, and every one of them is attributed to whichever number they dialed. A heavily advertised number collects more of this than a quiet one, so the noise is not evenly spread and it flatters exactly the campaigns you are spending most on.
Matching against a sales export filters it out by construction: a call that produced no revenue has nothing to match and never reaches the revenue column. No rule has to be written and no exclusion list has to be maintained.
The opposite case is more interesting. An existing customer who calls a tracked number and buys again is real revenue, but the purchase carries the same contact detail, so it credits the channel that first produced them — the earliest lead in the file. To see repeat purchases apart, map a first/repeat column as Product / service.
CallTrackingMetrics is often run across several offices, branches or franchise locations on one account, and the blended report is the one everybody looks at because it is the one that exists.
A blended cost per lead hides the thing worth knowing, which is that a channel works in one market and not in another. The same campaign in two cities can differ by more than two campaigns in one city.
Where the sales export carries a location or branch, map it as Location and the report cuts revenue by it, with the share traced to a channel in each. The matched-records export carries location and source on every sale for a per-branch ranking.
Fair questions
That works exactly as well as somebody remembers to do it, for the deals they remember. This reads the money from the system that already holds it.
Nothing changes. CallTrackingMetrics stays where it is and its export becomes the lead file.
That is the normal case and the reason this exists. Two exports, one join, on the phone and the email.
No. It supplies the lead file; this adds what those leads went on to pay. They answer different halves of one question.
Calls and form submissions with the contact detail and the source, campaign and keyword attached.
Closed sales from whatever holds your money — job management, practice management, a CRM or the ledger.
On the phone number and the email address, normalized on both sides with a proper phone library rather than string comparison.
Yes, and leaving them out is the most common way to make one channel look better than another for no real reason.
Yes — qualified-lead counts from CallTrackingMetrics beside revenue from here. Where the two rankings disagree is the useful part.
Then only the email can join them. If neither agrees, the sale stays in Direct / Unknown — it is not flagged or guessed. The one case set aside for a person is the same national number under a different country code.
No. A repeat purchase credits the channel that first produced the customer. Map a first/repeat column as Product / service to see repeat revenue apart.
Yes — map the sales export's location column as Location. A blended figure across branches is true of none of them.
Further than the call file, because the revenue lands after the contact — often months after.
Yes. Any provider exporting a contact detail with a source works identically.
The contact detail, the source fields and a date. No recordings, no transcripts, no voicemail — none of it is part of the match. Uploads are encrypted in transit and at rest, isolated to your workspace, and deleted with the import.
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.
CallTrackingMetrics 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
Call tracking answers one question well: which campaign produced the ring. It has no view of what happened after the call ended, which is where the money is decided. This is what the gap costs, and how to close it without replacing the call tracker you already have.
Read the articleBefore you blame the matching algorithm, look at how phone numbers are stored on each side. Extensions, country codes, leading zeros and a spreadsheet that decided a number was maths — this is where most attribution quietly fails.
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 CallTrackingMetrics, no API key, and no need to have been tracking anything until now. Last year works as well as this month.