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 Arborgold

The estimate was in March. The crane job was in August.

Export invoices from Arborgold, upload the leads behind them, and rank marketing on completed work rather than on requests for a quote.

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

CloseRev reads an Arborgold 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 estimate. Tree care and landscaping quote far ahead of the work, so the gap between lead and revenue is months, and only a long window reads it correctly. Invoices with no traceable lead are reported as Direct / Unknown.

Page updated September 24, 2026.

The gap

Spring fills the book with estimates and autumn fills it with invoices, and no report connects the two back to a channel.

Arborgold 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. Phone is the working key in this trade; email coverage is patchier.

  2. Needed

    Invoice total

    What was billed for completed work. Proposals and accepted estimates are not revenue.

  3. Needed

    Invoice date

    When the work was billed, used consistently. The match does not need the estimate date: it credits the earliest lead however long before the invoice it arrived.

  4. Optional

    Service type

    Removal, pruning, plant health care, maintenance contract. Their values differ by an order of magnitude.

Step by step

Getting the file out of Arborgold.

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

  1. Export invoices for completed work

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

  2. Take a full year

    Seasonality is the defining feature here. Any window shorter than a year compares channels across different seasons and calls it a ranking.

  3. Export your lead sources

    Call tracking, the website form, search ads, map listings and any neighborhood or marketplace listing you pay for — combined into one lead file with the source on each row.

  4. Let the invoice file run past the leads

    A March lead becomes an August invoice. The match credits the earliest lead however far back it is, so the invoice file only needs to reach far enough forward to catch the work.

  5. Upload both

    The join runs on the phone and the email, normalized; repeat work carries the same contact and credits the channel behind the first job.

What comes back

The page Arborgold 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 Tree Service page — not from a Arborgold account.

Traced to a channel$152,50061% of $250,000
Sales matched131 of 215high confidence only
Average sale$1,170per paid sale
ChannelShareSalesRevenue
Google Ads71$82,500
Local service ads47$55,000
Meta Ads13$15,000
Direct / Unknown84$97,500

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 job and the ad share a row.

The lag between the lead and the money is the whole problem

A homeowner asks for a quote in early spring. The crew is booked out, the job is scheduled for July, and the invoice lands in August.

A ninety-day attribution window loses that entirely, and every report built on one credits the wrong quarter's marketing or nothing at all.

Reading a full year of invoices against a full year of leads removes the problem rather than tuning around it: the earliest lead is credited however long the gap. The lag itself is not a figure in the report, but the matched-records export carries the lead date and the invoice date on every job.

Channels differ on that lag: an emergency storm call converts in a day, a planned removal in months, and a channel judged on the wrong one looks either urgent or dead.

Removals, pruning and plant health care are three different businesses

A large removal can be four figures. A pruning visit is a few hundred. A plant health care program is a small recurring amount several times a year.

Blended, they produce an average that describes nothing, and a channel weighted towards one is ranked as though it produced the others.

Where the export carries a service type, mapped as Product / service, the report cuts revenue by it; the matched-records export pairs type and channel, which is where the channel that is expensive per lead can turn out to be the one producing removals.

Recurring programs deserve the same treatment as any other subscription: the value is the year, not the first visit, and every visit credits the channel that produced the customer, so a year of the program shows in that channel's revenue.

Storm work is real revenue and it is not evidence about your marketing

A wind event fills the phone for two weeks. Those calls arrive because a tree is on a roof, not because a campaign worked.

Left in the file undistinguished, a storm inflates whichever channel happened to be running and produces a conclusion that will not repeat.

The honest treatment is to read those weeks separately. Where the export carries a service type or a priority flag, that is straightforward; where it does not, the date range alone usually tells you.

The point is not to discard the revenue — it is to stop it being used as proof that something works when the weather was the cause.

Most of these leads are phone calls and most of them are untracked

Homeowners with a dangerous limb call. So do the ones who saw the truck, the yard sign or the map result, and none of those leave a form behind.

With no tracked numbers, the lead file covers the web forms only, and web forms are the minority of this trade's inquiries.

Distinct tracking numbers on the website, the vehicles and every paid listing turn a mostly-empty lead file into a complete one, and the cost is trivial next to the budget being judged.

Until that exists the report states the size of the untracked bucket rather than distributing it across the channels that happen to have data.

Fair questions

“Arborgold already does that.” Not quite.

They say

“Arborgold already reports revenue by customer.”

We say

It does, and it has no record of the ad that produced the customer, because that happened before the customer existed.

They say

“Our season is too short for a year of data.”

We say

The season is short; the year is what makes two seasons comparable. A single season ranks channels against weather.

They say

“Most calls come from the trucks.”

We say

Then a tracked number on the trucks will tell you how much, and that is worth knowing before you spend anywhere else.

Questions

Arborgold, specifically.

Something else? Ask us and a person answers.

No. It reads a file you exported, so your schedule, crews and customer records are not reachable from here.

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