“AutoLeap already reports on our marketing.”
On what it sends and what it can see. The customers your reminders brought back are not evidence that the ads worked.
For AutoLeap
Export invoices from AutoLeap, upload the leads behind them, and separate the customers marketing won from the ones your reminders brought back.
CloseRev reads an AutoLeap export of invoices — the customer's phone or email, the amount and the date — and matches it against the calls, ads and listings that produced the first visit. A shop system that also sends reminders and follow-ups is constantly bringing back existing customers, and none of that is acquisition, so reminders stay out of the lead file and each customer's revenue credits only the lead that won them. Revenue with no traceable lead is reported as Direct / Unknown.
Page updated September 25, 2026.
The gap
The bays are full and the marketing report takes credit for all of it, including the customers who came back because of a text you sent.
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. Where invoices are sent and paid by text, the phone on file is unusually reliable.
Closed repair orders, parts and labor together.
When the order was closed. The customer created date is not read — which matters after a migration, when it is the date of the move.
First visit or return, mapped as Product / service and worked out from invoice history rather than from the created date.
Step by step
Written for somebody with AutoLeap 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 the date.
If the shop moved to AutoLeap from another system, every imported customer carries the migration date as their created date and looks new — so do not use it to mark first visits.
Tracked numbers, search ads, map listings, coupons and any fleet or warranty program.
Long enough to tell a first visit from a return, and for a new customer's second visit to happen.
The join runs on the phone and the email, normalized, with first visits and returns apart where you map a visit type.
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 Auto Repair Shops page — not from a AutoLeap account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 203 | $101,500 | |
| Local service ads | 142 | $77,000 | |
| Meta Ads | 61 | $24,500 | |
| Direct / Unknown | 289 | $147,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
A shop system that sends service reminders, follow-ups and declined-work nudges is doing valuable work. Almost all of it is aimed at customers the shop already has.
Counted in a marketing report, every car those messages bring back looks like marketing working, and the shop's acquisition spend gets credit for its retention.
The honest split is simple: a customer's first visit is acquisition; everything after it is retention, whatever message prompted it.
Mapped as Product / service, a visit-type column puts them apart, and both numbers become useful. The acquisition figure tells you what the advertising bought, and the retention figure tells you what the reminders are worth.
Neither is inflated by the other, which is what makes either of them worth reading.
A shop that moved to AutoLeap from another system usually imported its customer list, and every imported record carries the date of the move as its created date.
Read naively, the month of the migration shows hundreds of new customers and every marketing channel that was running looks extraordinary.
The fix is to find each customer's genuine first invoice from a year or more of invoice history, rather than trusting the created date, before marking anything as a first visit. CloseRev itself does not read the created date.
Where the history does not go back far enough, treat customers first seen in that period as of unknown origin rather than as new; without a lead in the file, their revenue stays in Direct / Unknown anyway.
This one correction can change a shop's report more than any other on this page.
A channel can bring more cars at a lower ticket, or fewer cars at a higher one, and both show up as the same monthly total.
Which matters depends on the shop: a shop with empty bays wants cars; a shop at capacity wants bigger tickets on the cars it can fit.
With first visits marked, the report gives each channel's revenue and average ticket, and the matched-records export pairs every first visit with its channel, so the shop can choose which channel suits where it is.
It also exposes the channel that fills the lot with inspections and oil changes the bays had no room for.
Where invoices are delivered and paid by text message, the phone number on the customer record has been used and confirmed at least once.
That makes the match against a lead file unusually reliable compared with systems where a number is typed in at the counter and never checked.
Normalization still runs on both sides, and anything that does not join stays visible in Direct / Unknown.
The practical effect is that less revenue ends up in Direct / Unknown for want of a usable key, which makes the channel ranking more complete.
Fair questions
On what it sends and what it can see. The customers your reminders brought back are not evidence that the ads worked.
Then the created dates are the migration date; find each customer's real first visit in the invoice history before marking anyone as new.
Then the acquisition figure will be small and honest, and the retention figure will show what that loyalty is worth.
No. It reads a file you exported, so your repair orders, inspections and messages stay where they are.
Closed repair orders with a customer contact detail, the total and the date.
Because reminders bring back customers you already had, and counting those as acquisition credits the ads with the retention work.
Imported customers carry the migration date. CloseRev does not read that date; mark first visits from invoice history instead of trusting it.
A year, so a first visit can be told from a return and a new customer's second visit has time to happen. There is no window to set.
Yes. With first visits mapped as Product / service, the report shows their revenue and average ticket, and the matched-records export pairs each with its channel.
Leave them out, or run them as their own import, so one account does not decide a channel's ranking.
Yes, where they carry a code or a distinct number, ranked on the same revenue as everything else.
Every order joins on the customer's phone or email, so all their vehicles credit the same channel.
Any revenue with no traceable lead, including untracked calls, passing trade and customers who predate the lead file.
A contact detail, an amount and a date, plus a visit type if you include one. No VINs required, no inspection photos, no payment details. Encrypted in transit and at rest and deleted with the import.
Revenue by source, first visits and returns apart where mapped, reminders kept out of the credit, 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.
AutoLeap 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 articleA channel judged on its first invoice is judged on the wrong customer. For a business that sees the same households again, the channel that sends loyal customers can look expensive and the one that sends deal hunters can look brilliant. Here is how to compute revenue per customer by acquisition channel at 12 and 24 months from a sales export, read cohorts honestly, switch to margin, and set what you can afford to pay for a customer.
Read the articleStart today
Nothing to install in AutoLeap, no API key, and no need to have been tracking anything until now. Last year works as well as this month.