“FieldPulse already reports revenue.”
It does. It cannot say which ad produced the customer, because that happened before the customer existed.
For FieldPulse
Export invoices from FieldPulse, upload the leads behind them, and see which channels produce work that closes.
CloseRev reads a FieldPulse export of invoices — the customer's phone or email, the amount and the date — and matches it against the calls, forms and ads that produced the job. FieldPulse tracks the whole path from estimate to payment, which makes it unusually good at answering where each stage leaked once a lead source is joined to it. Invoices with no traceable lead are reported as Direct / Unknown.
Page updated September 24, 2026.
The gap
Two channels deliver the same number of appointments and one of them produces half the revenue. Nothing you currently run would show that.
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 customer record. The phone number is the reliable key in the trades.
Billed and collected, not the estimate total. Estimates measure quoting.
When the work was billed. Use it consistently for every row.
Repair, install, maintenance, mapped as Product / service. Estimates, won or lost, belong in the lead file rather than here.
Step by step
Written for somebody with FieldPulse open in the next tab. Report names vary by edition, so each step says what to look for.
One row per invoice with a customer contact detail, the total and a date.
Won and lost together, each with the source of the lead behind it. The report then shows each channel's estimates beside its invoices, which is its close rate.
Trade revenue is lumpy. One large install in a short file decides the ranking on its own.
Call tracking, web forms, search ads, map listings and marketplaces, combined into one lead file with a contact detail and the source on every row.
The join runs on the phone and the email, normalized, and unmatched rows stay 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 Plumbers page — not from a FieldPulse account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 96 | $163,200 | |
| Meta Ads | 21 | $25,600 | |
| Email marketing | 14 | $19,200 | |
| Direct / Unknown | 88 | $112,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
Two sources can deliver identical appointment counts and utterly different revenue, because the people they send are not equally ready to buy.
Marketplace leads shopping three contractors close at one rate. A caller from a map result with an emergency closes at another. Neither is visible in a cost-per-lead report.
With the estimates as the lead file, each tagged with the source of the lead behind it, the report shows each channel's estimates, its invoices and its average invoice — close rate and won value per channel — which is enough to change a budget with confidence.
It also frames two very different problems: a channel that sends poor leads and a channel that sends good leads your team is slow to call back. The report shows that a channel's estimates do not close; your own call records say which of the two it is.
Work changes on site. Some jobs grow, some shrink, and a few are abandoned after the estimate was written.
Ranking channels on estimate values rewards whichever one produced the most optimistic quotes, which is a measure of your salespeople rather than your marketing.
The report uses invoices as the revenue side throughout. Estimate values are not read, so the gap between quote and invoice per channel is one to work out from FieldPulse itself — and it can reveal that one source's jobs systematically shrink on contact with reality.
That is worth knowing before a channel is cut for producing small jobs it did not actually produce.
A single project can produce several invoices — a deposit, progress billing, a change order, a final. Counted individually, one customer looks like four wins.
Every one of those invoices carries the same customer and credits the same channel, so the project's value lands where it should; only the sales count reads four. Sum by project before uploading if you want the count to mean projects.
A repeat customer is credited to the channel that first produced them in the same way. To see first jobs apart from later ones, map a first/repeat column as Product / service.
For contractors with maintenance agreements, that separation is also how the recurring revenue becomes visible instead of being averaged away. An agreement signed on a first visit is worth several years of small invoices, and a channel that produces them is worth paying more for at the front end.
Trade inquiries arrive by phone from vehicle wraps, yard signs, map results and referrals, and none of those produce a row in any lead file by default.
A report built only on web forms describes the minority of your inquiries and will underrate every offline channel you have.
Tracked numbers on the website, the trucks and each paid listing fix this in a week, and every report afterwards is worth reading. It is the single cheapest improvement available to a contractor measuring marketing.
Until then, the size of the Direct / Unknown bucket is stated plainly rather than being distributed across whichever channels happen to have data.
Fair questions
It does. It cannot say which ad produced the customer, because that happened before the customer existed.
Then you are judging them on a stage where they look similar, and ignoring the stage where they do not.
It is the lead file, with a source on each estimate, and it buys the close rate per channel — the number that can change the budget.
No. It reads files you exported; your schedule, crews and customer records are not reachable from here.
Invoices with a customer contact detail, the total and a date. Estimates, with the lead source on each, can serve as the lead file.
Used as the lead file: each channel's estimates beside its invoices, which is its close rate, and where two similar-looking sources can separate.
Six months at minimum, a year if you sell large installs.
Every invoice credits the channel that produced the customer, so the project's value is right; the sales count reads each invoice, so sum by project first if you want it to count projects.
Yes. A repeat customer carries the same contact, so later work credits the channel that first produced them.
Yes, where the export carries one, and it removes most of the distortion from a lumpy file.
Every agreement invoice credits the channel that produced the customer, so a year of the agreement lands on that channel rather than being judged on the first visit.
The invoice is used; estimate values are not read.
Anything with no traceable lead, which in the trades is usually untracked phone calls.
A contact detail, an amount and a date, plus a job type if you include one. No addresses required, no notes, no card data. Encrypted in transit and at rest and deleted with the import.
Revenue by source, each channel's estimates beside its invoices where estimates are the lead file, repeat work credited to the channel that first produced the customer, 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.
FieldPulse 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
Multi-crew home and field services businesses run on phone calls and job management software, not on web forms. Which means the standard marketing dashboard is measuring the smallest part of the business and missing where the money actually is.
Read the articleCall 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 articleZillow Premier Agent sells connections by share of voice in a zip code, or through Zillow Preferred for a fee when a lead closes, generally within two years. A monthly bill set against this month's closings will mislead you either way. Here is how to measure Zillow ROI by connection cohort, where the break-even between the two pricing models sits, and what to do about leads who were already your clients.
Read the articleStart today
Nothing to install in FieldPulse, no API key, and no need to have been tracking anything until now. Last year works as well as this month.