How do I tell whether a call came from Local Services Ads or from my regular Google Ads?
LSA calls arrive on a Google forwarding number tied to your Local Services profile, not on the dynamic numbers your search ads swap onto the website. The reliable way to separate them is to point the LSA forwarding destination at a tracking number used for nothing else, then stamp that number's source onto the CRM record the moment the call is created. Caller memory and callbacks still blur the edges.
The two channels reach you by different plumbing
Search ads use dynamic number insertion. A visitor lands on your site, a script swaps in a pooled number, and the session that produced the call carries the campaign, keyword and click identifier. Nothing about that mechanism applies to Local Services Ads, because the LSA unit is not your website. Google publishes its own forwarding number inside the ad, the customer taps it, and the call is routed to whatever destination number your profile has on file.
That difference is an advantage if you use it. The LSA forwarding destination is a single configurable field. Whatever number you put there becomes a clean, unambiguous marker for the channel, which is the simplest form of LSA tracking that actually survives contact with a busy call center.
The configuration mistake that collapses both into one bucket
Most accounts point LSA at the main business line, the same line printed on trucks, yard signs and the Business Profile. From that moment on the two channels are indistinguishable at the phone system, and everyone falls back to asking callers how they found you, which is unreliable.
- Provision a dedicated destination number. Use it only as the LSA forwarding target. Never print it, never publish it, never put it in an email signature.
- Keep search ads on their own pool. Pool numbers should never be reused as LSA destinations, or your session-level Google Ads attribution will start claiming LSA calls.
- Ring the same desk. The routing behind the numbers should be identical so nobody in the office has to behave differently.
What to write onto the record at creation time
Source labeling after the fact never holds up. Stamp the lead source, the LSA lead identifier where you have it, the job type Google matched, and the exact timestamp at the moment the customer record or booking is created. Later reconciliation is a join on those fields, not a guess.
Once the stamp is consistent, the same call recording can be scored the same way as every other source, which is what makes cross-channel call analysis meaningful instead of anecdotal.
Where the separation legitimately breaks down
A customer who found you through LSA may save the forwarding number and call it back weeks later for unrelated work, which shows up as a new LSA-sourced call that Google never charged for. Another customer sees your LSA listing, does not tap, then searches your name and calls the main line. Both cases are real and neither is fixable by better tagging.
The honest posture is to report the match rate and treat the remainder as unknown. An attribution system that never admits ambiguity is hiding it somewhere.
Topics: LSA · call tracking · attribution · CRM
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.