«FieldPulse already reports revenue.»
It does. It cannot say which advert produced the customer, because that happened before the customer existed.
Para FieldPulse
Export invoices from FieldPulse, upload the leads behind them, and see which channels produce work that closes.
Sin clave de API Nada que instalar en FieldPulseNada que instalar Sin tarjeta de créditoSin tarjeta
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.
Comprobado por última vez con la documentación del propio FieldPulse el 24 de septiembre de 2026.
La brecha
Two channels deliver the same number of appointments and one of them produces half the revenue. Nothing you currently run would show that.
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 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.
Whether an estimate was won or lost, and what kind of work it was. Together they show where each channel leaks.
Paso a paso
Escrito para quien tiene FieldPulse 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 invoice with a customer contact detail, the total and a date.
Won and lost together. The close rate per channel is the most actionable number this report produces.
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. Contact detail plus the source.
The join runs on the phone and the email, normalised, and unmatched rows stay 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 Plomería y fontanería, no de una cuenta de FieldPulse.
| Canal | Proporción | Ventas | Ingresos |
|---|---|---|---|
| Google Ads | 96 | $163,200 | |
| Meta Ads | 21 | $25,600 | |
| Email marketing | 14 | $19,200 | |
| Directo / Desconocido | 88 | $112,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
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 estimates exported alongside invoices, the report gives close rate and average won value per channel, which is enough to change a budget with confidence.
It also separates 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 first is a buying decision and the second is a scheduling one, and they are routinely mistaken for each other.
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. Where both are present it shows the gap per channel, which occasionally reveals 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.
Summed by customer, the project is one decision with one value, which is the unit a marketing decision is made in.
The report sums by customer across the window and keeps the first job separate from later ones, so a repeat customer is not silently credited to the original advert.
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 enquiries 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 enquiries 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, and it usually pays for itself on the first budget decision it changes.
Until then, the size of the Direct / Unknown bucket is stated plainly rather than being distributed across whichever channels happen to have data.
Preguntas justas
It does. It cannot say which advert 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 one more file and it buys the close rate per channel, which is usually the number that changes 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 as a second file if you can.
Close rate and average won value per channel, which is where two similar-looking sources usually separate.
Six months at minimum, a year if you sell large installs.
Summed by customer, so a project is one decision rather than four wins.
They are reported separately, so the decision stays yours.
Yes, where the export carries one, and it removes most of the distortion from a lumpy file.
Summed across the window as recurring revenue rather than judged on the first visit.
The invoice is used. Where both exist the report shows the gap per channel, which is occasionally the finding.
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 per acquired customer by source, close rate where estimates are included, first and repeat work apart, 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.
FieldPulse 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 FieldPulse, sin clave de API y sin necesidad de haber rastreado nada hasta ahora. El año pasado funciona igual de bien que este mes.