Google has published proper documentation for Performance Max campaigns running on pay-per-lead goals — campaign settings, targeting, best practices, the lot. Three help pages, unremarkable on their own. What they confirm is less unremarkable: Local Services Ads are being folded into Performance Max, and pay-per-lead is how that merger gets managed.
If you run — or used to run — Local Services Ads for a trades or home-services business, this is worth reading properly, not skimming.
What's actually moving
LSAs have always sat apart from the rest of Google Ads. Different interface, different verification process, pay-per-lead rather than pay-per-click, and — crucially — a level of local trust and vetting that made them genuinely good for tradespeople, solicitors, locksmiths, the businesses where a phone call is the whole point.
Folding that into Performance Max means the lead-generation logic that used to live in its own walled garden now runs on the same automated, cross-channel machinery as everything else — Search, Display, YouTube, Discover, Maps, all bid and served from one pool by one algorithm chasing one goal. The new documentation is Google explaining, ahead of the wider rollout, how you'll define service areas, pick categories, and set the campaign up to optimise toward a lead rather than a click or a purchase.
On paper, that's more reach and less admin. In practice, it's a much bigger black box deciding who gets your call.
Why this is a bigger deal than a normal PMax launch
Performance Max already asks for a lot of trust — you hand it a goal and a budget and it works across the whole of Google's inventory with limited visibility into what's driving what. That trade-off is manageable for ecommerce, where a sale is a sale and the data is clean.
Lead gen is messier. A "lead" can be a genuine job booked, a tyre-kicker, a wrong number, or someone three postcodes outside your service area who filled in a form by mistake. Performance Max can't tell those apart from the ad platform side — it only knows a form got submitted or a call got placed. Feed it "leads" as the optimisation goal without teaching it which leads were actually worth having, and it'll happily go and get you more of the cheap, junk kind, because as far as it's concerned that's a job well done.
That's exactly the trap the old LSA model protected against a little, with its more manual verification and narrower targeting. Merging it into Performance Max's automation removes some of that natural friction — friction that, annoyingly, was doing useful work.
What to check before you touch this
For anyone running trades, home services, or any pay-per-lead account once this rolls out fully to you:
- Feed it offline conversion data from day one. If Performance Max only ever sees "form submitted," teach it what happened after — job booked, quote given, no-show, wrong area. Without that, it's optimising blind toward volume, not value.
- Set service areas tightly and check them regularly. Automated systems given room to expand reach tend to use it. A locksmith three towns over is not a lead, whatever the platform counts it as.
- Watch call quality, not just call count. If you can, get call tracking or recording in place before this launches on your account, not after you've noticed the cost-per-lead creeping up with nothing to show for it.
The point
Every time Google folds a specialist product into its general-purpose automation, the same thing happens: it gets easier to run and easier to run badly. Performance Max isn't the problem — it's genuinely capable of good things here. The problem is what happens when nobody's told it what a good lead actually looks like, and it goes off maximising the wrong version of "success" with total confidence. That's a machine doing exactly what it was asked. The job, same as always, is making sure what you asked for is what you actually want.
Russell Anson runs Compulsion, an independent paid-search consultancy. Eighteen years in, pointed at the only metric that matters. compulsion.agency