How to track marketing ROI when you run Service Autopilot

Three disciplines, in order: make the lead source field in Service Autopilot required and keep the list short; put a dedicated call tracking number on every channel so phone leads stop being guesses; and close the loop by joining sources to actual transactions, so you're measuring cost per client, not cost per lead. SA's missing public API makes the fully automatic version harder, but the honest version is absolutely achievable, and most companies fail at step one, not at the technology. Here's the whole system.

Why is marketing ROI so muddy at most SA companies?

Not because the data doesn't exist: SA captures lead sources, estimates, and every dollar of revenue. It's muddy because the chain breaks at three predictable links. Sources get entered as "Google" for everything from LSA to organic maps. Phone leads (half or more of lead flow in most service companies) get logged as whatever the CSR guesses. And nobody joins the front of the funnel to the back, so decisions get made on cost per lead, which is the wrong number. Fix those three links and the fog lifts; no API required.

How should you set up lead sources in Service Autopilot?

Rules that survive contact with a busy office:

• Make the field required. If a lead can be saved without a source, sources will be blank by June.
• Keep the list short: 8 to 12 options. "Google Ads," "LSA," "Organic/Maps," "Website Quote," "Direct Mail," "Door Hanger," "Referral," "Repeat/Win-back." Fifty options produce garbage; ten produce data.
• Separate the Googles. Google Ads, Local Services Ads, and organic/Maps are three different investments with three different costs. One "Google" bucket hides your best and worst spend in the same average. (Why they differ so much: LSA vs. Google Ads.)
• Audit monthly. Ten minutes: pull new leads, count blanks and "Other," fix the intake habit, not the historical data.

How does call tracking fix the phone-lead problem?

A homeowner who found you on LSA and one who typed your URL from a postcard both just "called." Without tracking numbers, both become the CSR's best guess. With a dedicated number per channel (website, Google Ads, LSA, Google Business Profile, direct mail, even truck wraps), the source captures itself. Modern call tracking adds recordings, transcriptions, and AI summaries, which quietly doubles as sales coaching: you learn not just where leads came from but which ones your office actually booked. Missed-call data alone usually pays for the setup: we did that math in what missed calls cost.

How do you close the click-to-client loop without an API?

This is the step SA's closed perimeter complicates, and the workaround is the same export-replication pattern that powers everything else in this series (the API situation, the export mechanics). Export clients and transactions with their lead sources on a nightly or weekly cadence into a dataset your reporting reads. Then join three tables: what you spent per channel (from the ad platforms), what leads arrived per channel (from SA sources + call tracking), and what revenue those clients produced (from SA transactions). That's the whole trick. Our reporting dashboard does this join automatically for companies on our SA integration, but the logic works in a spreadsheet if you're disciplined.

Illustrative example of why it matters: Channel A delivers leads at $40; Channel B at $90. Judged on lead cost, A wins. But A closes 15% at $500 first-year value ($267 per client) while B closes 40% of higher-intent leads at $700, $225 per client, with better retention. B is your growth channel; lead cost said the opposite. Numbers illustrative; the rank-flip is something we see constantly.

What should you actually review each month?

One page, five numbers per channel: spend, leads, close rate, new clients, and first-year revenue booked. From those, cost per client and revenue per dollar. Trend them across three months before killing or scaling anything: service businesses are seasonal enough that one month lies. And one culture note: the report only stays honest if the office keeps tagging sources, so show the team the report. People maintain data they can see working.

Frequently asked questions

Can Service Autopilot report sales by lead source natively?

Yes: SA's reporting can slice revenue and clients by source, which covers the back half of the loop. What it can't see is your ad spend, which is why the join has to happen outside SA.

Do tracking numbers hurt local SEO?

Handled correctly, no: your primary number stays consistent on your Google Business Profile and citations, with tracking numbers used on ads, landing pages, and print. Any competent setup follows this rule.

What about leads that come from instant quotes?

Tag them at the source automatically: an accepted or abandoned instant quote should arrive in SA with its campaign attached. Automated intake is the one place sourcing should never depend on a human.

How much does attribution perfection matter?

Less than consistency. A slightly imperfect system used every month beats a theoretically perfect one nobody maintains. Get to "directionally right, consistently measured" and make decisions.

The takeaway: ROI tracking on Service Autopilot is a discipline problem wearing a technology costume. Required sources, tracking numbers on every channel, and a monthly join of spend to booked revenue: that's the entire system. The missing API changes how you build the join, not whether you can.

The 30-day setup checklist

1. Trim your SA lead source list to 8–12 and make the field required.
2. Split "Google" into Google Ads, LSA, and Organic/Maps.
3. Deploy tracking numbers on website, ads, LSA, GBP, and print.
4. Start the export: clients + transactions with sources, weekly minimum.
5. Build the one-page monthly report: spend → leads → clients → revenue per channel.