Your Local Services Ads dashboard says 22 leads this month. Your calendar says something different. And your call tracking software, the tool you pay for precisely to settle this argument, has nothing to say about LSA at all.
That is not a broken setup. Google LSA call tracking breaks the standard playbook on purpose: Local Services Ads are the one channel where dynamic number insertion and number pools structurally cannot work. There is no page for the JavaScript to rewrite. Google shows its own forwarding number, on Google's surface, before you are anywhere near the transaction.
So here is what actually works. This guide covers how Google routes and reports LSA calls, why the usual tracking tech goes blind, what the common workaround costs you, and the dedicated number method that both attributes the call and answers it.
How Google Routes and Reports Your LSA Calls
Before you can track LSA calls, it helps to be exact about whose phone number is doing what.
The number your customer actually dials
When your ad appears in the Local Services pack, the phone number on it is not your business line. Google generates a forwarding number for your profile and routes calls from it to whatever you set as your lead phone number inside Local Services Ads. That hop is the whole mechanism: it is how Google counts the lead, records the call, and decides whether to charge you for it.
Every LSA lead you are billed for passed through that forwarding number. Nothing else about your marketing stack is involved.
What the lead dashboard gives you
Google's reporting is decent for what it is. You get:
- A list of leads with the caller's number and, usually, a name
- Google's own recording of the call
- Whether the lead was charged or credited back
- The lead type (phone call, message, or booking)
That is enough to reconcile a bill. It is nowhere near enough to run a business on.
What it cannot tell you
The dashboard has no opinion on whether anyone picked up. A call that rang out to voicemail at 4:40pm still appears as a lead, and you are still billed for it. It cannot tell you what was said in language your team would use, whether the caller was a real prospect or a solicitation, whether the job got booked, or how any of it connects to the customer record in your CRM.
So measurement on LSA has two separate holes. The first is attribution: LSA data lives in an LSA silo, disconnected from every other channel you run. The second is outcomes: nothing in Google's report tells you what the lead became.
If you are still getting your bearings on the channel itself, we covered how Local Services Ads work and what they cost separately. This post is about measuring them.
Why DNI and Number Pools Do Not Work on Local Services Ads
This is the part nobody explains clearly, and it is why the question "which call tracking tool should I use for LSA?" has an unsatisfying answer.
DNI needs a page to swap, and LSA does not have one
Dynamic number insertion works like this: a snippet of JavaScript sits on your website, reads how each visitor arrived, and swaps the phone number displayed on the page accordingly. Someone arriving from a Google Ad for "emergency water heater repair" sees a different number than someone arriving from organic search. When they call, the tool knows the source, the campaign, and often the keyword. CallRail built a very good business on exactly this, and it genuinely works.
None of it applies to Local Services Ads. The ad is rendered by Google, in Google's results, with Google's forwarding number on it. Your JavaScript never runs. There is no session to read and no number on the page to replace. A pool of twelve rotating numbers is useless when the only number the customer ever sees belongs to Google.
That is the structural piece: LSA is not a tracking problem you can solve with better tags. It is a channel where the entire display layer is out of your hands.
The double forwarding workaround
The industry workaround is to move the tracking number one hop back. CallRail documents the setup in its own help center: you assign a call tracking number as the lead phone number inside your LSA profile, so calls now travel from Google's forwarding number, to your tracking number, and then on to your actual line.
It works, in the narrow sense that calls get attributed. It also adds a second forwarding leg to every single lead. Your highest-intent caller, the one Google just charged you for, sits through that extra hop wondering whether the line is broken.
What the workaround actually buys you
You get channel attribution and a second recording of the call. Useful.
What you do not get is an answer. The call still lands on the same cell phone, in the same pocket, while you are on the same roof. CallRail's own small business benchmarking report found that up to 85% of callers whose calls go unanswered never call back. On a pay-per-lead channel that is a particularly expensive way to be well informed: you paid Google for the lead, you paid a tracking vendor to log it, and the lead went to whoever picked up instead. If you want the full breakdown of that second bill, see what CallRail actually costs, or our roundup of the best CallRail alternative options.
There is one more wrinkle worth knowing. Google re-grades LSA leads after the fact and can credit a lead back days after your tracking platform already logged it as a conversion. So the two systems drift, and the tracking dashboard slowly stops matching the invoice.
Now the honest part. On Local Services Ads, keyword-level attribution does not exist for anyone. Google does not report the search query behind an LSA lead, to CallRail or to us or to you. Channel-level is the ceiling for this channel, full stop. Which changes the question from "how fine-grained can my tracking get?" to "what else can my tracking number do for me?"
The Dedicated Number Method: LSA Call Tracking That Actually Works
If the display number is out of your control, control the destination instead.
One answered number per channel
Get a phone number whose only job in the world is Local Services Ads. Put it in your LSA profile as the lead phone number and put it nowhere else. Not on your website, not on your truck, not on your Yelp listing. From that moment, every call to that number came from LSA by definition. No JavaScript, no pools, no probabilistic matching, no debate at the end of the month.
Then repeat the pattern per channel: one number for LSA, one for Google Ads, one for Yelp, one for Avvo or whichever directory keeps sending you work. With NextPhone, all of those numbers ring the same AI receptionist with the same greeting, the same qualifying questions, and the same booking setup. One configuration, many doors, nothing to duplicate or retrain.
Setting it up
The whole job takes about ten minutes:
- Create a dedicated tracking number in NextPhone's call tracking and label it for the LSA channel.
- Open your Local Services Ads profile and set that number as your lead phone number.
- Place a test call through your own ad and confirm it rings the AI and lands in your inbox tagged as LSA.
- Leave it alone. Every LSA call from now on carries its channel automatically.
One small detail that pays off later: choose a local area code rather than a toll free number. Local numbers get answered noticeably more often, largely because toll free reads as telemarketing on a caller ID. Your LSA number is also the number that appears when you or your receptionist call that lead back, or text them a booking link, so its area code matters.
What gets tagged from then on
Every call to that number arrives with an LSA badge in your inbox, shows up in your per-channel insights breakdown, and writes its source into your CRM. You stop reconciling two dashboards and start reading one list.
The same method scales sideways. Here is the same approach applied to Google Ads campaigns, and here is how it looks for tracking Yelp calls from review-driven searches.
Want to see the channel tagging before you commit to anything? Book a NextPhone walkthrough and look at how a tagged call arrives.
Tracking That Answers: The LSA Ranking Dividend
Here is the argument that makes dedicated numbers more than a tidy filing system.
Responsiveness is part of how Google ranks LSA advertisers
Google is unusually direct about this. Its documentation on how Local Services ads are ranked lists your responsiveness to customer inquiries as a ranking input, alongside review score, proximity, and business hours. Answer your calls and you are shown more often. Miss them and you are shown less.
Sit with what that means for a tracking setup. If you route LSA calls to a number nobody reliably answers, your call tracking is not neutral. It is measuring a channel while actively degrading it. You will get a beautiful chart of a declining lead count.
Under five seconds, around the clock, in nine languages
The fix is not heroic discipline about picking up the phone. It is putting something on the other end of that dedicated number that always picks up.
Across 1,446,980+ real business calls answered, NextPhone resolves 90-95% of calls without human escalation, picks up in under 5 seconds, and maintains 99% positive caller sentiment. It handles calls in 9 languages, and when a call genuinely needs you, it routes to your phone with the context already collected.
Picture the roofer. It is 4pm, he is on a steep pitch with a nail gun, and an LSA lead calls about a leak ahead of Thursday's storm. Google bills him for that lead either way. In one version it rings out, the homeowner calls the next roofer in the pack, and Google notes a missed inquiry. In the other, the AI answers on the second ring, captures the address and the nature of the leak, books the inspection, and texts him the summary. Same ad spend, same lead, opposite outcomes.
Speed compounds on a pay-per-lead channel
Every LSA lead is already paid for at the moment it arrives, which makes response time the only variable left. The InsideSales lead response study, built on 5.7 million inbound leads, found conversion rates run 8x higher when the response comes inside the first five minutes rather than later. Wait a day and the lead has usually hired whoever answered first.
Google tracks your responsiveness on an ongoing basis, so the effect compounds in both directions. We broke down the mechanics of the LSA phone response score in a separate post, and we will not rehash them here.