Local services ads reporting for agencies
Picture the Tuesday phone call: a plumbing client wants to know why they paid Google a few thousand dollars last month. You have the answer somewhere: a lead list in the Local Services Ads interface, a spend figure in Google Ads, some call recordings, and a spreadsheet you last touched three weeks ago. Twenty minutes of digging later you have a number. That is the reporting problem with Local Services Ads in one sentence.
Local services ads reporting is its own discipline because LSA does not behave like the rest of the Google stack. There are no keywords, no impression share, no click-through rate. There are leads, charges, disputes and a badge. The metrics your client cares about live in a different interface from every other number in their report, and most of them never reach GA4 at all.
This guide covers the google local services ads metrics worth reporting, the four realistic ways to get LSA data out of Google, how to structure a local services ads leads report that answers the question before it gets asked, and where automation genuinely helps.
Last updated: August 2026
Key takeaways
- Local Services Ads is a pay-per-lead product, so the reporting spine is charged leads, cost per charged lead and booked jobs, not clicks or CTR.
- LSA leads usually do not appear in GA4, because the call or message happens inside Google's own interface and never touches the client's website.
- Disputed and credited leads change effective cost per lead, so a report that only shows gross spend overstates what the client actually paid.
- LSA campaigns can be viewed alongside Search and Performance Max inside a linked Google Ads account, but lead-level detail still lives in the Local Services Ads interface or the Google Ads API.
- Across the platform connections agencies have made in ReportsMate, the average client account has about two platforms connected, and GA4 is the most-connected of them at roughly seven in ten client accounts. LSA is almost always a separate login on top of that stack.
What's in this guide
- What is local services ads reporting?
- How do agencies get LSA data into client reports?
- Which local services ads metrics should you report?
- How do you build a local services ads leads report?
- Where LSA reporting quietly breaks
- How LSA fits the rest of the local reporting stack
- Reporting cadence and a monthly checklist
- FAQs
What is local services ads reporting?
Local services ads reporting is the practice of turning Google Local Services Ads lead and charge data into a client-facing summary of leads generated, leads paid for, cost per lead and jobs booked. It differs from standard Google Ads reporting because LSA charges per lead rather than per click, so the familiar impression and click metrics either do not exist or do not matter.
Local Services Ads is the pay-per-lead format that sits above the normal search results for service categories like plumbing, electrical, HVAC, locksmiths, law firms and real estate, carrying a Google Guaranteed or Google Screened badge. Google's own Local Services Ads Help documentation is the source of truth for eligibility, badge requirements and the dispute process, and it is worth re-reading each quarter because the product changes more often than Search does.
The practical consequence for reporting: your client is buying leads, so your report has to be a leads report. Impressions and position are largely invisible in LSA. Spend, lead count, lead quality and lead outcome are everything.
We built ReportsMate email-first because, after years around agency reporting, the dashboards clients were handed almost never got logged into. That is doubly true for LSA clients, who are usually tradespeople or practice owners running a business from a ute or between appointments. The report that lands in the inbox is the one that gets read.
How do agencies get LSA data into client reports?
There are four realistic routes, and most agencies end up using two of them at once. Here is an honest comparison, including where ReportsMate does and does not fit.
| Approach | What you get | Ongoing effort | Best for |
|---|---|---|---|
| Manual export from the Local Services Ads interface | Full lead list, lead type, charge status, dispute outcomes | High - someone exports and reformats every month | Single-location clients, low lead volume |
| Link LSA to a Google Ads account | Local Services campaign spend and lead counts sitting beside Search, Shopping and Performance Max | Low after setup | Agencies already reporting Google Ads for the same client |
| Google Ads API local services lead resources | Lead-level data pulled on a schedule, including conversations | Developer time to build and maintain | Multi-location and high-volume accounts |
| Dedicated LSA connector in a reporting platform | Prebuilt LSA metrics in a dashboard or report | Low, but check the vendor's connector list | Agencies whose whole client base runs on LSA |
| Automated email report for the connected stack, LSA summary layered on | Client reads the report without logging in anywhere | Low ongoing, LSA numbers added as commentary | Agencies reporting several platforms per client |
Being straight with you about our own vantage point: ReportsMate is an email-first white-label reporting platform, and the connectors that are live today are Google Analytics 4, Google Ads, Meta Ads, Google Search Console and Google Business Profile. LSA lead-level detail is not one of them. Some competitors do carry a dedicated Local Services Ads connector - AgencyAnalytics has one, and other vendors such as DashThis, Whatagraph, Swydo, Supermetrics and Looker Studio each maintain their own connector lists that change over time, so check the current list before you commit a client to a workflow.
What ReportsMate handles is the part around LSA: the branded, scheduled email that carries GBP visibility, Google Ads performance, GA4 behaviour and Search Console rankings into the client's inbox on a cadence, with the LSA lead summary added as the headline commentary. For a lot of home-services agencies that combination is the practical answer.
Which local services ads metrics should you report?
The core LSA metric set is charged leads, cost per charged lead, lead type mix, dispute credits, response rate, review signals and booked jobs. Report those seven and you have covered what a service business owner actually asks about.
| Metric | What it tells the client | Where it lives |
|---|---|---|
| Total leads | Raw volume of calls, messages and bookings the ad produced | Local Services Ads interface |
| Charged leads | The leads they actually paid for after credits | LSA interface, linked Google Ads account |
| Cost per charged lead | Spend divided by charged leads - the number owners quote to each other | Calculated |
| Lead type mix | Calls versus messages versus bookings, which predicts close rate | LSA interface |
| Disputed and credited leads | How much invalid volume you clawed back for them | LSA dispute history |
| Response and answer rate | Missed calls and slow replies, which affect both close rate and ranking | LSA interface, call tracking |
| Review count and average rating | A ranking input and the trust signal buyers see | LSA profile, Google Business Profile |
| Booked job rate | Leads marked booked or completed against total charged leads | LSA lead statuses plus the client's CRM |
| Budget pacing | Spend against the account budget, which throttles lead flow when hit | LSA interface |
Two of those deserve a note. Cost per charged lead is not the same as cost per acquisition - it is the cost of a conversation, not a customer. If you are setting client targets, work backwards from close rate using a cost per acquisition goal calculator so the CPL target you agree to is actually profitable at their job value.
Response rate is the one agencies under-report and clients under-appreciate. Google factors responsiveness into LSA ranking, and a client who misses half their calls is buying leads and then binning them. Putting missed-call volume in the report every month is uncomfortable and it is exactly why the report earns its keep. If the client runs call tracking as well, our guide to Google Ads call tracking reporting for clients covers how to reconcile the two call sources without double counting.
How do you build a local services ads leads report?
A local services ads leads report should open with charged leads and cost per charged lead, then break leads down by type and outcome, then show what you changed and what you will change next. Keep it to one screen of email before the detail starts.
A structure that works, in order:
- Headline block. Charged leads this period, cost per charged lead, spend, and each figure against last period. Three numbers, no preamble.
- Lead flow. Total leads, charged leads, disputed leads, credits received. This is where you show the client you are actively disputing rubbish leads rather than letting Google bill for them.
- Lead quality. Type mix, average call duration if you have it, and the proportion marked booked. Quality is the whole argument in a pay-per-lead channel.
- Client-side actions. Missed calls, average response time, and review volume added this period. Frame it as shared responsibility, not blame.
- What we did. Budget changes, service category adjustments, business hours edits, review requests sent, disputes lodged.
- What's next. Two or three specific actions with dates.
Insider terms worth defining once inside the report so the client stops guessing: reporting cadence (how often the report goes out, and the rhythm the relationship runs on), white-labelling (the report carries your agency's branding, sender name and domain rather than a tool's), and charged lead (a lead Google billed for, as distinct from every lead the ad produced).
For agencies who report on trades and home-services clients across several channels, we go deeper on the full monthly structure in client reporting for home services agencies.
Where LSA reporting quietly breaks
The most common LSA reporting failure is a mismatch between the lead count in your report and the lead count in the client's phone. Four causes, all fixable.
GA4 does not see most LSA leads. The call or message happens inside Google's interface, so no session, no event, no conversion in GA4. If your report leans on GA4 as the single source of truth, LSA looks like it produced nothing. Google's Analytics Help documentation is clear about what does and does not create a session, and an off-site call is not one. Report LSA leads from LSA data and say so in the report.
Disputes settle after the report goes out. Credits often land days or weeks after the lead was charged, so last month's cost per lead moves after you have already sent the number. Either report disputes on a one-period lag, or add a short line noting that figures include credits received to date.
Budget caps hide demand. When an account hits its budget the ads stop serving, so a flat month-over-month lead count can mean saturation rather than a plateau. Note budget-limited days in the report or the client reads a ceiling as a failure.
Multi-location gets messy fast. A client with six locations has six sets of LSA data, six review profiles and, usually, one impatient owner who wants a single number. Roll up at the top and break out by location underneath, the same way you would for multi-location Google Business Profile reporting.
How LSA fits the rest of the local reporting stack
LSA should be reported as one of four local channels, alongside Google Business Profile, Google Ads and organic search, because a service business buys leads from all four and does not care which interface they came from. A report that isolates LSA invites the client to judge it in isolation.
Here is the first-party picture from our own platform. Across the client accounts agencies have connected in ReportsMate, there are around 80 live platform connections spread across 43 client accounts, which works out to about two platforms per client. GA4 leads the mix at roughly seven in ten client accounts, followed by Meta Ads, Google Ads, Search Console and Google Business Profile. We have delivered more than 3,000 client report emails off the back of those connections.
The reason that matters for LSA: even before you add Local Services Ads, the average local client already spans two or more data sources. Adding LSA as a third or fourth login is how monthly reporting turns into a half-day job. The fix is not another dashboard, it is a single scheduled email that carries the connected platforms automatically, with the LSA numbers dropped into the same email as commentary.
Google Business Profile is the natural companion channel here, and it went fully live in ReportsMate in August 2026 with real data flowing: search and maps impressions, website clicks, phone calls and direction requests, connected through one Google OAuth click. When an LSA client asks whether the ads are worth it, GBP call volume is the free-versus-paid comparison that answers them. Google's Business Profile Help documentation defines each of those metrics if you want to quote definitions verbatim in a client-facing glossary.
Want to see the delivery model before committing to a workflow? See how it works - connect platforms, set a schedule, reports go out branded as yours.
Reporting cadence and a monthly checklist
Most LSA clients are best served by a monthly report with a lightweight weekly lead-count email, because lead volume is volatile enough that a month of silence feels like neglect. Pay-per-lead clients watch their spend daily; the reporting cadence should acknowledge that.
Run this list before every LSA report goes out:
- Pull the lead export for the full period, not the rolling 30 days the interface defaults to.
- Check the dispute queue and lodge anything invalid before you calculate cost per lead.
- Reconcile charged leads in the LSA interface against spend in the linked Google Ads account.
- Flag any budget-limited days.
- Pull GBP calls and website clicks for the same period so paid and organic local sit side by side.
- Check review count and average rating, both a ranking input and a talking point.
- Ask the client for booked-job counts if their CRM is not connected, and report the gap honestly if they do not supply them.
- Write two forward actions with dates. A report without a next step is an invoice with charts.
On tooling budget: reporting platforms in this category run from roughly the price of a couple of coffees a month for solo operators up to mid-double-digit monthly pricing for agencies managing dozens of clients. Our current tiers and client limits are on the pricing page, and every plan includes a 14-day free trial with no credit card.
FAQs
Q: What metrics do Local Services Ads report on?
A: Local Services Ads reports on leads rather than clicks. The metrics available are total leads, charged leads, lead type (phone call, message or booking), lead cost, dispute status and credits, response rate, review count and average rating, and budget against the account cap. There is no keyword-level data, no impression share and no click-through rate, because LSA does not sell clicks. For client reporting, charged leads and cost per charged lead do most of the work, with booked-job rate added from the client's CRM where it exists.
Q: Can you see Local Services Ads data inside Google Ads?
A: Yes, partly. Linking your Local Services Ads account to a Google Ads account surfaces Local Services campaigns alongside Search, Shopping and Performance Max, which means spend and lead counts appear in the same account view as the rest of the client's paid activity. Lead-level detail - who called, what they asked for, whether it was disputed - still lives in the Local Services Ads interface, or in the local services lead resources exposed by the Google Ads API. Check Google Ads Help for the current linking steps, as the setup has changed more than once.
Q: Do LSA leads show up in GA4?
A: Usually not. Local Services Ads leads happen inside Google's own interface: the customer taps to call or message straight from the ad unit and never lands on the client's website, so GA4 records no session and no conversion. That is the single biggest source of confusion in local reporting, because a client looking at GA4 concludes the ads produced nothing. Report LSA leads from LSA data, state the source in the report, and use GA4 for what it is good at, which is site behaviour and the traffic your other channels drive.
Q: How do you dispute a Local Services Ads lead?
A: Disputes are lodged from the lead detail in the Local Services Ads interface, and the usual valid grounds are that the lead was for a service you do not offer, outside your service area, spam, or a duplicate of a lead you were already charged for. Google reviews and issues credits where it agrees. For reporting, keep a running count of leads disputed and credits received, because the difference between gross spend and credited spend is real money and it is the clearest evidence a client has that you are managing the account rather than watching it.
Q: What is a good cost per lead for Local Services Ads?
A: It depends entirely on job value and close rate, so a benchmark from another vertical will mislead you. A locksmith closing 40% of leads on $180 jobs and a personal injury firm closing 5% on $12,000 matters have nothing useful to say to each other about cost per lead. Work backwards instead: take the client's average job value, multiply by their close rate on LSA leads specifically, and set a CPL ceiling that leaves the margin they need. Our free cost per acquisition goal calculator does the arithmetic in a few seconds.
Q: Can you white-label Local Services Ads reports for clients?
A: Yes. White-labelling means the report carries your agency's logo, sender name and domain instead of a tool's branding, so the client experiences it as your work. In ReportsMate that covers the sender identity and custom domain on the email itself, so the report arrives from your agency rather than from a platform the client has never heard of. Since LSA lead detail is not one of our live connectors, the practical pattern is a branded scheduled email carrying GBP, Google Ads, GA4 and Search Console data with the LSA lead summary written in as commentary.
Q: How often should LSA reports go to clients?
A: Monthly for the full report, with a short weekly lead-count note if the client is spending enough to watch it daily - which most pay-per-lead clients are. The point of a fixed reporting cadence is that the client stops wondering. Agencies lose accounts over communication gaps far more often than over performance, and a service business owner who has not heard from you in five weeks is not thinking about your last good month.
Q: Should LSA be reported separately from Google Ads?
A: Report them separately in the detail and together in the summary. Separately, because the metrics are not comparable: one is pay-per-lead and one is pay-per-click, and blending them produces a cost per lead that means nothing. Together at the top, because the client wants one total lead number and one total spend number for their paid search investment. A combined headline with two clean breakdowns underneath satisfies both readings without inventing a metric.
Final tips
Report the charge, not the click. LSA clients are buying leads and every metric in the report should ladder up to what a lead cost and what it turned into.
Put missed calls in front of them. It is the fastest performance gain available in most LSA accounts and it costs nothing to fix.
Do not let LSA live in its own document. The moment your local reporting spans an LSA export, a GBP screenshot and a Google Ads dashboard, the report stops going out on time - and reports that stop going out on time are how retainers quietly end.
Stop losing your Sundays to client reports. Start your free 14-day trial - no credit card, no setup, cancel anytime. Your clients get branded reports in their inbox automatically, on the schedule you set.