Cookie preferences

Choose what we may use. Strictly necessary cookies keep you signed in and can't be turned off; everything else is your call and changes nothing about how the site works. You can change your mind any time from the footer.

For AutoLeap

Most of this month's cars were already yours.

Export invoices from AutoLeap, upload the leads behind them, and separate the customers marketing won from the ones your reminders brought back.

  • No API key
  • Nothing to install in AutoLeapNothing to install
  • No card requiredNo card

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.

AutoLeap sees

What was sold, to whom, and for how much.

no shared row
Your ad account sees

The click, the keyword, the call, and what each one cost.

The file

What the export needs in it.

Three things carry the match: who, how much, and when. Anything else is optional and only changes how the report can be sliced.

  1. Needed

    Customer phone or email

    On the customer record. Where invoices are sent and paid by text, the phone on file is unusually reliable.

  2. Needed

    Invoice total

    Closed repair orders, parts and labor together.

  3. Needed

    Invoice date

    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.

  4. Optional

    Visit type

    First visit or return, mapped as Product / service and worked out from invoice history rather than from the created date.

Step by step

Getting the file out of AutoLeap.

Written for somebody with AutoLeap open in the next tab. Report names vary by edition, so each step says what to look for.

  1. Export closed repair orders

    One row per invoice with a customer contact detail, the total and the date.

  2. Check when your customer records were created

    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.

  3. Export your lead sources

    Tracked numbers, search ads, map listings, coupons and any fleet or warranty program.

  4. Take a year

    Long enough to tell a first visit from a return, and for a new customer's second visit to happen.

  5. Upload both

    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

The page AutoLeap cannot show you.

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.

Traced to a channel$203,00058% of $350,000
Sales matched406 of 695high confidence only
Average sale$492per paid sale
ChannelShareSalesRevenue
Google Ads203$101,500
Local service ads142$77,000
Meta Ads61$24,500
Direct / Unknown289$147,000

Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.

The argument

What changes when the repair order and the ad share a row.

Reminders are retention, and they wear a marketing label

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 migration makes every customer look new

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.

Car count and revenue per car move separately

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.

Text-to-pay makes the phone number the strongest key

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

“AutoLeap already does that.” Not quite.

They say

“AutoLeap already reports on our marketing.”

We say

On what it sends and what it can see. The customers your reminders brought back are not evidence that the ads worked.

They say

“We just moved to AutoLeap.”

We say

Then the created dates are the migration date; find each customer's real first visit in the invoice history before marking anyone as new.

They say

“All our cars are return customers.”

We say

Then the acquisition figure will be small and honest, and the retention figure will show what that loyalty is worth.

Questions

AutoLeap, specifically.

Something else? Ask us and a person answers.

No. It reads a file you exported, so your repair orders, inspections and messages stay where they are.

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.

Start today

Two exports, and you will know.

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.