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 Tekmetric

Two customers, same inspection, one approves the brakes and one does not.

Export repair orders from Tekmetric, upload the leads behind them, and rank channels on approved work rather than on cars through the door.

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

CloseRev reads a Tekmetric export of closed repair orders — the customer's phone or email, the total and the date — and matches it against the calls, ads and listings that produced the first visit. Tekmetric reports average repair order and approval rates unusually clearly; what it cannot say is which marketing produced the customers whose numbers are good. Orders with no traceable lead are reported as Direct / Unknown.

Page updated September 24, 2026.

The gap

Your average repair order is a shop-wide number. It is really several numbers, one per channel, and you cannot see them.

Tekmetric 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. The phone number is the reliable key in this trade.

  2. Needed

    Repair order total

    Parts and labor on closed orders, which is approved work rather than recommended work.

  3. Needed

    Order date

    When the order was closed. Applied consistently to every row.

  4. Optional

    Service type

    Mapped as Product / service — maintenance, major repair, tires. Declined work is not read; approval stays in Tekmetric's own reports.

Step by step

Getting the file out of Tekmetric.

Written for somebody with Tekmetric 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 order with a customer contact detail, the total and the date.

  2. Keep Tekmetric's approval report beside it

    Declined work is not read, but approval rate set beside each channel's revenue — the matched-records export names each customer's channel — is the most useful comparison here.

  3. Take a year

    A repair customer is worth several visits, and the first one is often the smallest.

  4. Export your lead sources

    Call tracking, map listings, search ads, coupon offers and any fleet or warranty program.

  5. Upload both

    The join runs on the phone and the email, normalized, with every return visit credited to the channel that produced the first.

What comes back

The page Tekmetric 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 Tekmetric 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.

Approval rate is where the channels actually differ

A digital inspection produces the same recommendations regardless of how the customer found the shop; what varies is whether they say yes.

That variation tracks with why the customer came: somebody drawn by a discounted oil change is making a price decision, and somebody whose car broke down is not.

Declined work is not read, but the report gives approved value per channel, and set beside Tekmetric's approval figures through the matched-records export, that explains a shop-wide average repair order that never made sense.

It is also the most actionable output here, because it points at the offer and the service advisor conversation rather than at the channel itself.

A channel with good traffic and poor approval can be fixable without changing the spend at all.

A discounted first visit measures the discount

Oil change and brake specials fill bays quickly and produce a first transaction that is nearly identical across every channel that runs one.

The information appears later, in whether the customer returned for work that was not discounted.

A year of repair orders, every visit credited to the channel that produced the customer, separates the channels that bought a transaction from the ones that produced a relationship.

Discount channels can lose that comparison by a wide margin, which is not an argument against offers but against judging them on the day they run.

Mapping a first/return column as Product / service keeps first visits and later ones apart, so the two effects are never averaged into one misleading figure.

Fleet accounts should not be averaged with retail customers

A small fleet is won once, serviced regularly and lost in a single bad experience, and its annual value dwarfs a retail customer's.

Averaged in, one fleet win makes whichever channel produced it look extraordinary on a result that will not repeat.

Mapped as Product / service, a customer-type column gives honest retail and commercial revenue lines, and the matched-records export shows whether the sources feeding each differ.

Where the export flags a customer type, map it; where it does not, mark fleet accounts before uploading, because the report will not infer them.

For a shop trying to build commercial work, that second ranking is the whole reason to run the report.

Many inquiries here are phone calls

Drivers with a warning light or a noise call, and so do the ones who saw the sign, the map listing or the coupon.

Without tracked numbers those all arrive identically, and the lead file covers only the customers who used a web form.

Distinct numbers on the website, the map listing, any print and the sign itself produce a lead file with a source on every row.

Until that exists the report states the size of the untracked bucket rather than distributing it across whatever else was running.

It is worth doing before anything else on this page. A shop that tracks its calls can rank every channel it buys; a shop that does not is reading a report about the fraction of customers who happened to use a form, and that fraction is not representative of anything.

Fair questions

“Tekmetric already does that.” Not quite.

They say

“Tekmetric already shows average repair order.”

We say

Shop-wide. It is several numbers, one per channel, and the differences are large.

They say

“Our coupons fill the bays.”

We say

They do. Whether they produce customers who approve real work is a different question the file answers.

They say

“We do not track calls.”

We say

Then most of this trade's inquiries have no source, and tracked numbers are the first fix rather than a different report.

Questions

Tekmetric, specifically.

Something else? Ask us and a person answers.

No. It reads an exported file, so your orders, inspections and customer records stay where they are.

Tekmetric 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 Tekmetric, no API key, and no need to have been tracking anything until now. Last year works as well as this month.