How does attribution work for Google Local Services Ads?
Local Services Ads charge per lead and deliver that lead as a call or message inside Google's own system, so the source label is reliable while the detail is thin. You get lead type and job category, not keywords. Connecting an LSA lead to revenue means matching the caller's phone number to the job record in your field service system. Disputed leads should be checked against booking data rather than memory.
A different data shape from search ads
Search ads give you a click identifier that can travel into your CRM. Local Services Ads give you a lead object that lives in Google's console: a phone call or message with a category, a timestamp and a charge. There is no click identifier to stamp on a web form, because there was usually no web session at all.
That changes the matching strategy. For LSA the join key is the phone number and the timestamp, matched against the customer and job records created around the same time. Getting that match automated is the main technical task in LSA integration work.
What you can and cannot learn
- You can learn which job categories produce leads, what each lead cost, how many leads booked, and revenue per LSA lead once the phone match is in place.
- You cannot learn which query produced the lead, because that detail is not exposed the way search terms are.
- You can influence lead mix through job type selection, service area and review volume, which behave more like local ranking factors than bidding levers.
- You should watch response time and answer rate, since those affect how often you are shown at all.
Handle disputes with data, not recollection
Some charged leads are genuinely out of area, out of category, spam or duplicates. Platforms provide a dispute process with a time limit, and most contractors under-use it because reviewing leads is nobody's job.
The durable fix is a weekly reconciliation: list charged leads, join them to your booking records, and flag the ones with no matching contact, an address outside your service area, or a job type you do not perform. Reviewing a short exception list takes minutes. Reviewing every lead from memory takes hours and gets skipped. Where call recordings exist, call analysis can classify the conversation so obvious mismatches surface without anyone listening to audio.
Comparing LSA against search ads fairly
The two are not directly comparable on cost per lead, because an LSA lead is a contacted lead while a search ad conversion may be a form fill of unknown quality. Compare them on the same downstream measure instead: cost per booked job and cost per dollar of completed revenue.
That comparison usually reorders the two channels relative to what the platform dashboards suggest, and it is only possible once both are joined to the operational record. It is the same reconciliation problem as everywhere else in marketing reporting: one definition of a lead, one system of record for revenue.
Topics: Local Services Ads · LSA · lead disputes · phone matching
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.