Free tool · No signup · Your data stays in your browser

LSA Lead Tracker

Log your Google Local Services Ads leads, see your true cost per lead, find which bad leads Google will actually credit, and get specific recommendations to cut wasted ad spend. Free, no API key, no upload.

· Methodology v1.0 · Privacy policy
No signup 100% browser-side No API key

What changed about LSA lead credits (and why most contractors are losing money on it)

Until mid-2024, Google Local Services Ads contractors could manually dispute bad leads through a form in the LSA dashboard. Submit a reason ("job type not serviced," "geographic mismatch," "not a real customer"), wait for review, often get the credit. It was tedious, but the policy was at least predictable.

That ended in July 2024. Google replaced manual disputes with an automated lead credit system that uses machine learning to review every charged lead within 72 hours. Credits, when granted, appear on the contractor's account within roughly 30 days. The contractor's only remaining lever is the "Rate this lead" feedback survey attached to each lead in the dashboard.

The change was not just a workflow change. Two categories that were previously creditable under manual disputes are now no longer creditable at all:

If a contractor's categories or service area is set even slightly too wide, every resulting bad lead is now a charge with no recourse. That gap, between what Google bills and what is actually creditable, is what this tool measures.

What automated credits actually cover in 2026

Per Google's published policy, the automated system focuses on a narrower set of categories than the old manual process. Auto-credit eligibility roughly covers:

The "Rate this lead" feedback survey is the contractor-facing input to this system. Marking a lead "Very dissatisfied" with a specific reason is a signal Google's automated reviewer weighs when deciding whether to credit. Industry reporting on the feedback-to-credit conversion rate (from sources including Ylopo and contractor community discussions) suggests roughly 15-25% of flagged bad leads result in a credit. Worth flagging every one even at that rate.

The 15-day duplicate window, explained in plain English

A duplicate-lead credit applies when:

  1. The same customer calls your business twice through LSA.
  2. Both calls are about the same job.
  3. Both calls are charged by Google.
  4. Both charged calls happened within 15 days of each other.

If all four conditions are met, the second charge is creditable. If the second call happens on day 16 or later, it is not. This is the rule that catches most existing-client scenarios: a homeowner who used you six months ago and called the LSA ad number again because they did not have your direct number. There is no credit available there. The fix is operational: route known customers off your LSA tracking number by giving them a direct office line, a cell number, or putting an alternate number on invoices and email signatures.

Verticals where lead credits do not apply

Google's LSA credit policy applies primarily to home services. Per the Google Local Services help center, lead credits are not currently available for healthcare verticals, tax specialists, or EMEA (Europe / Middle East / Africa) advertisers. If you run LSA for an excluded vertical, the verdicts this tool surfaces will not map cleanly to your account, and the dashboard math should be read as an upper bound on recoverable money.

What this tool measures, and why "true cost per lead" is the number that matters

The LSA dashboard inside Google's product shows your nominal cost per lead: total spend divided by total leads, including the trash. That number is misleading because it averages your booked-and-quoted leads with your spam, your wrong-service, your out-of-area, and your existing-client charges.

The number that actually decides if LSA is profitable for you is the cost per valid lead, which is what this tool calls "True CPL." A valid lead is anything you would actually try to sell (booked, quoted, lost to a competitor). Spam, wrong service, out of area, and non-recent existing clients are excluded because they are not real opportunities. The gap between the nominal CPL Google shows you and the True CPL the tool calculates is the wasted-lead tax. For most contractors we have seen, that gap is meaningful and the fix is upstream (service area, categories, customer routing).

From there, the cost per booked job is the metric that decides whether to scale spend. If your booked-job cost is below a comfortable fraction of your average ticket, LSA is profitable and you should spend more. If it is too high, the budget is buying activity that does not close.

What to do when you see a recommendation fire

The tool surfaces five recommendation patterns based on logged leads. Each recommendation cites the policy or signal behind it, and is phrased conservatively ("consider this, here is the tradeoff") rather than as a hard directive.

Related reading on LSA leads

If you want to go deeper on any of the topics this tool surfaces:

Frequently asked questions

Are LSA lead credits automatic in 2026?

Yes. Google removed manual disputes in July 2024 and rolled out an automated credit system. Machine learning reviews every charged lead within 72 hours and applies credits automatically for invalid leads, with credits appearing within roughly 30 days. The contractor's only remaining lever is the "Rate this lead" feedback survey on each lead in the LSA dashboard.

What leads are no longer creditable?

Two categories were removed from creditable reasons in 2024: leads where the customer asks for a service the contractor does not offer ("job type not serviced") and leads where the customer is outside the contractor's stated service area ("geo not serviced"). Both were creditable under manual disputes. Neither is creditable now. The only fix is upstream in your LSA service category and service area settings.

What is the 15-day duplicate lead window?

Google credits a duplicate lead when the same customer calls about the same job twice and both calls are charged within 15 days of each other. The second charge is creditable. Calls outside that 15-day window, for example an existing client returning months later, are not creditable.

How does the "Rate this lead" feedback survey work?

Inside the LSA dashboard, each lead has a feedback survey where you rate the lead and pick a reason. Marking it "Very dissatisfied" with a specific reason sends a signal to Google's automated credit reviewer. Industry reporting suggests roughly 15 to 25 percent of flagged bad leads result in a credit, so it is worth submitting feedback on every legitimate bad lead. The tool generates a paste-ready note for the survey on every creditable case.

Does this tool send my lead data anywhere?

No. The entire tool runs in your browser. Lead data is stored in your browser's localStorage on your own device and never leaves it. No signup, no account, no email collected, no analytics on lead data. The one optional opt-in feature is anonymized aggregate sharing (counts by service type, valid-lead rate, average spend per lead, which recommendations triggered) which is currently a stub that does not transmit anything.

Does this work for verticals other than home services?

Per Google's published policy, lead credits are not currently available for healthcare verticals, tax specialists, or EMEA advertisers. If you run LSA for an excluded vertical, the credit verdicts in this tool will not map cleanly to your account in the same way.

How accurate is the credit verdict?

Each verdict cites the specific Google policy that applies. Spam and duplicate-within-15-days leads are likely auto-credited by Google's machine learning, and the tool flags them so you know to verify on the next billing cycle. Wrong-service and out-of-area leads are flagged as not creditable based on the 2024 policy change. The verdict is a probabilistic guide based on documented policy; final credit decisions are made by Google's automated system.

Can I import a CSV export from my LSA dashboard?

Yes. The Log a lead view has a CSV import section. The tool auto-maps common column names (date, service, amount, outcome). If a required column cannot be auto-detected, a manual mapping step appears. The file is parsed entirely in the browser and never uploaded.

Privacy policy · Credit rules last verified May 2026