Attribution is the quiet reason so many Local Services Ads accounts fly blind. You can see spend in the LSA interface and revenue in your accounting, but the wire connecting the two — LSA lead attribution — is missing by default. Leads arrive as calls and messages that never touch your website, so the analytics tools you use for everything else simply cannot see them. This article explains why LSA is hard to attribute and how to build the link anyway.
Why the usual analytics can't see LSA leads
Most digital marketing attribution assumes a click: someone visits your site, a tracking cookie or tag follows them, and a conversion gets recorded. LSA breaks that model. The lead is a phone call or an in-platform message that resolves inside Google's system. There is no site visit, no landing page, no UTM parameter. As a result, LSA leads are effectively invisible to Google Analytics and to most website-based tracking. Google reports the lead in the LSA dashboard, but it does not push that lead into your CRM or tie it to a job you booked.
The bridge you have to build
Attribution for LSA is a matching problem: connect a lead in Google's system to a customer in yours. The two reliable keys are:
- Phone number — the caller's or messenger's number appears on the lead and, once they become a customer, on their record.
- Timestamp — the lead's date and time lets you disambiguate when the same number appears more than once.
With those two, you can take each LSA lead, find the matching customer, and stamp that customer's source as LSA. That single tag is what unlocks every downstream metric.
What attribution makes possible
Once leads are attributed, the numbers you actually manage by become computable:
| Metric | Needs attribution? | Why |
|---|---|---|
| Cost per lead | No | Google reports it directly |
| Booking rate | Yes | Must link lead to a booked outcome |
| Cost per booked job | Yes | Needs booked jobs traced to LSA |
| ROAS | Yes | Needs revenue traced to LSA leads |
| Lifetime value by source | Yes | Needs customers tagged by origin |
Notice the pattern: the only metric that survives without attribution is the shallow one Google hands you. Everything that reflects profit requires the bridge.
Practical ways to attribute LSA leads
- Manual match. Export LSA leads periodically and reconcile them against new customer records by phone and time. Tedious but workable at low volume, and it costs nothing.
- Ask at intake. Train whoever answers to note that a caller came through Google's verified listing. Imperfect — people forget, and callers don't always know — so use it as a supplement, not the system of record.
- Automated matching. A tool that ingests LSA lead data and matches it to your CRM by phone and timestamp removes the manual step and keeps attribution current, which is what makes weekly reporting sustainable.
Keep LSA as its own attributed source
Resist the temptation to fold LSA into a generic "Google" or "paid" bucket. LSA behaves differently from search ads and organic — different lead types, different cost model, different quality profile — and the whole point of attribution is to judge it on its own terms. Keep it a distinct source so that when you compare channels, you are comparing like measurements: cost per booked job and ROAS by source, not spend against a revenue figure you can't break apart.
The payoff
Attribution is unglamorous plumbing, but it is the difference between guessing and knowing. Without it, "LSA is working" is a hunch. With it, you can say exactly how many jobs and how much revenue the channel produced, what each customer cost, and whether the next budget dollar should go there or somewhere else. Build the bridge once, and every other metric in your reporting finally has something solid to stand on.
Frequently asked questions
Why are Local Services Ads leads hard to attribute?
LSA leads mostly arrive as phone calls and in-platform messages, not clicks to your website, so they never touch your site analytics. Google reports the lead in the LSA interface but does not pass it into your CRM or connect it to a booked job, so attribution requires you to bridge the gap manually or with a tool.
Can I track LSA leads in Google Analytics?
Not directly, because most LSA leads are calls or messages handled inside Google's platform rather than website visits. You can track them by exporting LSA lead data and matching leads to customer records by phone number and timestamp, keeping LSA as its own attributed source rather than folding it into web analytics.
How do I connect an LSA lead to a booked job?
Match the lead to a customer record using the phone number and the lead timestamp, tag that customer's source as LSA, and record the outcome when the job books. That link lets you compute booking rate, cost per booked job, and revenue per lead by source instead of guessing where jobs came from.