The short answer
Link an LSA account to its website in DuckDive and three numbers get stored for it: leads, charged leads and spend. Your agent reads them with the get_lsa_summary tool, then does the division, ranks the accounts and points out where many leads went uncharged.
- Cost per charged lead is arithmetic your agent does from two stored inputs. Google's LSA report screen does not show it, while some dashboard tools do.
- A growing gap between leads and charged leads is often the first sign that something changed in an account.
- Google says LSA performance reports will not move into Google Ads, so keep your own copy before your account migrates.
Cost per charged lead: the maths and the traps
The formula fits on a sticky note: spend for a window, divided by charged leads for the same window. Google's View reports on Local Services Ads page lists charged leads and the total you were charged, but it does not list a cost per lead figure (checked November 2026). With DuckDive, your agent does the division.
get_lsa_summary returns three things for a website's LSA account: leads, charged leads and spend. Cost per charged lead is computed by the agent from spend and charged leads. It is not a stored metric, so ask the agent to show its working. The division is easy; a number you would defend to an owner is harder. Five traps catch most people.
Dividing by every lead instead of charged leads
Spend only comes from charged leads. Divide by all leads and the uncharged ones water the figure down, so an account full of junk calls looks cheaper than it is.
Credits that land after the window closes
Google may credit low-quality charged leads on its own. Its automated lead credits page says credits generally post to your balance within 30 days, and the original charge still shows on your invoice. A seven-day figure can include charges that will later be credited back.
Short windows on small accounts
An account with a handful of charged leads a week swings wildly on one extra call. Rank accounts on 30 or 90 days; keep 7 days for spotting that something just broke.
Lead mix moving under you
Google's How leads work page says message leads are typically priced lower than phone leads, though not always. More calls and fewer messages can raise cost per charged lead with nothing wrong. DuckDive does not split leads by type, so check the mix in the LSA inbox.
Windows that do not line up
Every DuckDive data tool works on preset windows, a week at the short end and a year at the long end. To compare this month with the two before it, have the agent subtract the 30-day totals from the 90-day totals, then halve the rest for a 30-day pace.
Do not average averages
For a group of accounts, divide total spend by total charged leads. The mean of each account's own figure gives a quiet account the same weight as your busiest one.
Ask your agentFor each LSA account, work out cost per charged lead for the last 30 days and over the last 6 months, show the working, and flag any account where the 30-day figure is more than a quarter higher.
Tools it calls list_websites get_lsa_summary
Leads, charged leads and spend, defined
Three numbers come from the account and three are derived by your agent. Keep the two groups apart in anything you send a client.
- Leads
- Every contact the account recorded in the window, as
get_lsa_summaryreports it. - Charged leads
- Leads Google billed you for. Its help pages treat answered calls, voicemails, messages and booking requests as valid, and bill a missed call in business hours only once the caller has held on for more than 20 seconds.
- Spend
- What the account was charged for its charged leads in the window. Google's reporting API describes its cost field as the sum of costs from charged leads in the date range.
- Uncharged leads
- Derived: leads minus charged leads. Contacts Google recorded but did not bill.
- Share charged
- Derived: charged leads divided by leads. A useful early warning on an LSA account.
- Cost per charged lead
- Derived: spend divided by charged leads, for the same window and the same account or group.
Lead credits and the call, message and booking split have no column here. Both sit in the LSA report screen; look there when a derived number moves.
Your account data versus scraped LSA listings
"LSA data" means two different things, and knowing which you need saves a wasted trial.
Account data is what Google records inside an LSA account: leads, charged leads, spend, credits. Only people with access can see it. Google's Local Services API reporting guide builds its account reports around a manager account and its linked LSA accounts, and marks its detailed lead reports as deprecated in favour of the Google Ads API.
Listing data is what anyone can see on the search results page, collected by tools that run searches and record the ads. A scraper such as the Google Local Services Ads Scraper on Apify returns ad position, advertiser name, rating, review count, phone, service area and response time. It returns no leads, charged leads or spend, because those never appear on the page.
The two connect. Google's About ad rankings page says position depends on your bid and your likelihood of getting a lead, which takes in responsiveness, relevance and profile quality such as rating and review count. A listing tracker shows where you appear; account data shows what appearing there cost.
| Question | Account data in DuckDive | Scraped listing data |
|---|---|---|
| What did each charged lead cost? | Yes, spend over charged leads | No, spend is never public |
| How many leads went uncharged? | Yes, leads minus charged leads | No |
| Where do I show for a search in one town? | No, no ranking position | Yes, the better tool for this |
| How do rivals' ratings and reviews compare? | No | Yes, as seen when scraped |
| Read from inside the account? | Yes, through your Google access | No, read off the results page |
Sources: Apify actor page and Google's ad ranking help, checked November 2026.
DuckDive covers the account side only, so keep your listing tracker if you report on placement.
Worked example: six LSA accounts ranked by charged-lead cost
The first job most multi-account marketers want is a ranking: which account costs the most per billed lead? By hand, that is six logins and a spreadsheet.
Ask your agentAcross all accounts, divide spend by charged leads for the last 30 days and rank accounts from most to least expensive.
Tools it calls list_websites get_lsa_summary
Rank my six Pinehollow accounts by spend per charged lead, last 30 days.
list_websitesfinds the six Pinehollow Plumbing service-area sites, each with an LSA account linkedget_lsa_summarycalled once per site to pull its 30-day totals
Tallowmere is the most expensive at $80.00 per charged lead, twice Larchmoor. Across all six, $13,775 bought 242 charged leads, or $56.92 each.
| Account | Charged | Per charged |
|---|---|---|
| Tallowmere | 41 | $80.00 |
| Brackenhurst | 43 | $65.00 |
| Gannet Hill | 34 | $60.00 |
| Sedgebrook | 49 | $50.00 |
| Ostler Park | 30 | $47.00 |
| Larchmoor | 45 | $40.00 |
One thing the ranking hides: Brackenhurst logged 61 leads, and only 43 of them were charged. Spread its $2,795 over all 61 and it shows $45.82, which sits fifth against the other five's charged-lead figures. Even if every account were divided by all of its leads, Brackenhurst would still slide to fourth, because the other five had just two to four uncharged leads apiece.
So before trimming Tallowmere's budget, find out where Brackenhurst's 18 uncharged leads came from.
Rank your own LSA accounts by what a billed lead costs
Link each account to its website and your agent can do the division across all of them whenever you ask.
Free for 2 sites · No credit card
When leads rise and charged leads do not
An account that reports more leads every week can still be getting worse. If the extra contacts are ones Google does not bill, the phone rings more and the crew books the same jobs. The gap between the two counts shows it before the job board does.
Google's How leads work page names the contacts it filters out or bills only under conditions. Each one maps to something that changes inside a business:
- Invalid contacts such as spam or duplicates. Google filters these out, and more of them often follow a new category or a wider service area.
- Missed calls where the caller hangs up within 20 seconds. Only longer missed calls in business hours are charged, so a rise in short ones usually means the phone is not being picked up fast enough.
- Callers who hang up in an automated menu before pressing a key. Watch for this right after someone adds a phone tree.
- Repeat contacts within 15 days from the same number or email on a lead already charged. A recall campaign pushes these up.
- Unanswered calls outside business hours or the ad schedule. Changed hours in the profile show up here.
None of these is bad on its own; a repeat caller is often about to book. The problem is a share charged that drifts down for weeks while the lead count keeps climbing.
Ask your agentFor Pinehollow Plumbing, compare the share of leads that were charged in the last 30 days with its share over the last 90.
Tools it calls list_websites get_lsa_summary
| Window | Leads | Charged | Share charged |
|---|---|---|---|
| Last 90 days | 761 | 712 | 93.6% |
| Last 30 days | 275 | 242 | 88.0% |
The 90-day row already contains the last 30. Take those out and the earlier 60 days ran at 96.7% (470 charged of 486), so the slide is steeper than the two rows suggest.
One brand is easy to eyeball. For a whole book of accounts, turn the same check into a screen:
Ask your agentWhich accounts had more than 20% of their leads not charged over the last 90 days?
Tools it calls list_websites get_lsa_summary
Twenty percent is a starting line, not a Google rule. Move it until the screen flags the accounts you would actually go and check.
Worked example: flat spend, halving charged leads
This pattern costs real money because nothing on the budget line looks wrong. The invoice matches last month and the leads count is steady. Only the billed leads have dropped, so each one costs far more.
Ask your agentEmber Valley Heating's LSA bill looks normal but the owner says the phone is quiet. Pull 7, 30 and 90 days, back out the 60 days before this month, and tell me when it changed.
Tools it calls search get_lsa_summary
Ember Valley's invoice looks normal but the phone is quiet. When did it change?
searchfinds the Ember Valley Heating website and its idget_lsa_summarythe quarter, so the earlier 60 days can be backed outget_lsa_summarythe month that looks wrongget_lsa_summarythe latest week, to see if it is still happening
Spend held while charged leads almost halved. I subtracted the last 30 days from the 90-day totals ($10,950 spend, 214 leads, 166 charged) and halved the rest for a prior 30-day pace.
| Per 30 days | Earlier pace | Last 30 days | Shift |
|---|---|---|---|
| Spend | $3,625 | $3,700 | +2% |
| Leads | 70 | 74 | +6% |
| Charged leads | 66 | 34 | -48% |
| Share charged | 94% | 46% | -48 pt |
| Per charged lead | $55 | $109 | +98% |
The last 7 days ($860 spend, 17 leads, 7 charged) follow the same pattern, so the change is recent and still running.
The data cannot say why, only where to look: about half the contacts are now unbillable, and each billed one costs roughly twice as much.
From here the work moves into the LSA account, where lead types, credits and settings live:
What to check inside the LSA account
- Phone menu. Did anyone add an automated menu or change the call routing in the last month? Hang-ups in a menu are not charged.
- Answer speed. Review recent missed calls in the inbox. Short ones rise when a dispatcher leaves or a line is forwarded.
- Hours and ad schedule. Compare the profile's business hours with when the office really answers.
- Bid mode and maximum per lead. A higher maximum, or a switch of bid mode, can raise what each billed lead costs.
- Job types and service area. New categories or a wider area bring contacts Google may judge invalid.
- Credits posted. Look at the credits line in the report for the same window before you call the cost final.
If the phone is the trouble, the guide to finding which locations lost calls checks LSA leads against other signals to show whether demand fell or the answering did.
Connecting each LSA account
In DuckDive the unit is the website, and a website holds a single LSA account, so six accounts need six websites. Users of other reporting tools run into the same shape: a commenter on a public AgencyAnalytics feature request notes that Google treats each location as a separate LSA account. That request was opened in March 2022 and marked launched in April 2024, allowing up to five LSA accounts per campaign in that product.
-
Use a Google login that can already open those LSA accounts
Select Continue with Google. Every LSA account that login can open shows up as a choice. When a location you manage is missing from the list, the business that owns its account has to grant that login access on Google's side first.
-
Add a website for each account
One website per location or service area. On an agency account, file each under its client.
-
Attach each LSA account to its location's website
Choose the account that belongs to this location. If the same site also has analytics, Search Console or a Google Ads account, attach those to it as well, so later questions can put LSA beside them. Attaching an account kicks off its history import, which tends to take a few minutes.
-
Or hand the setup to your agent, then name LSA
With an admin account, and "Also allow actions" ticked when you connect, your agent can add the websites and attach sources itself. Its setup guide treats Local Services Ads as optional and leaves it out unless you ask, so paste the setup line from the top of this page and, once it finishes, ask for LSA by name:
Follow-up for your agentNow link each of these websites to its Local Services Ads account, and list any location you could not match to an account.
-
Point your AI app at DuckDive
Open your agent's connector settings and add the DuckDive MCP address,
https://api.duckdive.ai/mcp. Sign-in runs through Google, so that address is the only thing you paste. The Claude and ChatGPT pages walk through each app's screens and plan limits. -
Wait for the LSA line to read ready
Ask the agent to run
get_sync_statuson one of the location websites. It labels every attached source as ready, importing or failing, with the date of its newest data. When Local Services Ads reads ready, try the ranking prompt above.
The move into Google Ads, briefly
Local Services Ads are being folded into Google Ads, where each account becomes a Performance Max campaign with a pay-per-lead goal. Google's transition help page says the first wave started in August 2026 for select US home and storefront service advertisers, broader groups follow in late 2026, and non-US accounts and remaining categories in 2027 (as of November 2026). Account admins get an email 14 days before their date.
The part that matters for reporting: "Your Local Services Ads performance reports won't transition to Google Ads." Lead history, such as contact details and messages, does transfer. The same page says manual lead disputes are no longer supported. After the move, Google Ads shows charged leads under its "Conversions" metric.
Plan the save before your notice arrives. The LSA history checklist sets out the wave dates and export options. To set LSA spend against Google Ads spend for each site without counting a lead twice, the spend and leads ledger guide walks through it.
What this data does not include
get_lsa_summary is small on purpose: three numbers per account per window. Enough to rank, screen and spot a break; not enough to run the account. Here is what it leaves out.
- Lead details. No calls, messages, recordings or lead types. Use the LSA inbox, or Google Ads' Leads page after migrating.
- Disputes and credits. No dispute status and no credits figure. Check the report screen in the account.
- Budget. No weekly budget or monthly maximum, so the agent cannot tell you an account is capped.
- Ranking position. No placement or competitor data. A listing tracker covers that.
- Custom dates. Fixed windows only, up to the last 12 months.
So when is DuckDive the wrong pick? If you run one account and open it every morning, Google's screen is enough. If your job is fighting bad leads one by one, you need the inbox. If the client wants a branded monthly PDF, a reporting tool built for that fits better. The same goes for a cost-per-lead figure that is already calculated in a client dashboard: AgencyAnalytics' LSA integration lists Cost and Cost Per Lead as ready-made report fields, with each widget pointed at the account you choose (as of November 2026). For that job it is the better fit. DuckDive earns its place once you have several accounts and want questions answered across them, or want LSA beside the same site's Google Ads results, GA4 and Search Console in one conversation.
Plumbing, HVAC and other home services businesses can end up with an account per service area. Multi-office law firms may hold one per office. And real estate brokerages whose agents run their own accounts face the same pile of logins.
Credits, disputes and history
Old numbers can move. Google's credits page says some poor-quality leads are charged and credited within the first 24 hours, and others later, with credits generally posting within 30 days. So pull a month again near its end before you lock a client report.
Credits are not available everywhere. The same page says lead credits are not offered for health care categories, tax specialists or advertisers in EMEA, and that Google no longer credits "job type not serviced" or "geo not serviced" leads. There, a bad lead stays a charged lead.
Google's own report history is about to split off. The LSA report page says its data starts on October 1, 2017, and that reporting is what Google says will not follow your account into Google Ads. DuckDive keeps what it imports when you link an account, and your agent can ask about up to the last 12 months of it. That import does not replace exporting Google's own reports for older periods. The guide to saving LSA history covers what to export, and when.
Refresh a month before you rank it. Once a month's credits have posted, ask your agent to refresh the lsa source for the last 30 days, then rerun the ranking. refresh_website_data needs an admin account and can run for a given website once every 15 minutes.
Before you link your LSA accounts
Does cost per lead come pre-calculated?
No. DuckDive stores the two inputs, spend and charged leads, for each account and window, and your agent divides one by the other when you ask. Have it show the working so you can see which window and which accounts went into the figure.
Whose Google login should connect the LSA accounts?
Any login that can already open them. After sign-in, DuckDive offers every LSA account that login reaches. A missing account means the business that owns it has not yet granted that login access. DuckDive never asks for your Google password.
Why might an account's figures differ from the LSA screen?
Usually the date range does not line up, or credits posted after DuckDive imported that month. Compare one account over an identical range first. If credits have landed since, an admin's agent can refresh the last 30 days.
Can my agent dispute a lead or see call recordings?
No. DuckDive does not read lead details, recordings, lead types or dispute status, and it has no tool that changes anything in your LSA account. Disputes and recordings stay in the LSA inbox, or on the Leads page in Google Ads after your account moves.
Will Google carry my LSA reports across when the account migrates?
Google says no: performance reports stay behind, while lead history moves. Export Google's reports before your migration date, as Google advises. DuckDive keeps what it has already imported, but that is not a full substitute for those exports.
How many LSA accounts does the free plan cover?
One. The free plan covers a single website with no card required, and a website holds one LSA account, alongside whatever else that site links, such as GA4 and Search Console.
Sources
- Google's LSA report screen explained: which metrics it shows, the October 2017 start date and its pointer to the Local Services API. Opened November 16, 2026.
- Google's automated LSA lead credits page: credit timing, invoices and the categories and regions without credits. Opened November 16, 2026.
- Google's How leads work page: which contacts are billed, filtered out or billed once per 15 days. Opened November 16, 2026.
- Local Services API reporting guide: account reports built around a manager account. Opened November 16, 2026.
- An Apify LSA listings scraper: the fields scraped from the results page. Opened November 16, 2026.
- Google's LSA ad ranking help: bid and likelihood of getting a lead. Opened November 16, 2026.
- AgencyAnalytics request for several LSA accounts per campaign: opened March 2022, launched April 2024. Opened November 16, 2026.
- AgencyAnalytics LSA integration page: Cost and Cost Per Lead report fields. Opened November 16, 2026.
- Google Ads Help article 17213585 on the LSA migration: wave timing, reports left behind, lead history moved. Opened November 16, 2026.
Checked against its sources on . The plumbing and heating firms in EXAMPLE DATA blocks, and all their numbers, are made up.
