Google has confirmed it is bringing Local Services Ads into Google Ads proper, restructuring them as Performance Max pay-per-lead campaigns. Bidding, reporting and management will change beginning August 2026. On the surface this looks like a tidying-up exercise. In practice, it changes the commercial logic of local lead generation campaigns in ways advertisers need to get ahead of now.
The Pay-Per-Lead Model Is Now Inside a Platform Built for CPA
Local Services Ads operated as a separate product with its own interface, its own verification requirements and a pay-per-lead billing model that sat outside the main Google Ads ecosystem. Advertisers who used them were often running them independently of their wider paid search activity, with minimal overlap in reporting or budget management.
Moving that pay-per-lead model into Google Ads means it now sits alongside campaigns running on cost-per-click with Smart Bidding strategies chasing target CPA or target ROAS. That is a meaningful change in how performance is compared and how budget decisions get made. A pay-per-lead campaign sharing an account with a tCPA search campaign will require clear thinking about how each is evaluated, what counts as a lead, and whether the two are pulling from similar audiences or query pools.
For lead gen advertisers who have historically kept their Local Services budget separate from their main Google Ads account, the integration creates both an opportunity and a risk. The opportunity is unified reporting. The risk is that costs and conversions from two very different billing mechanisms start getting conflated without proper segmentation.
Performance Max Is Doing More Jobs Than It Was Designed For
Google is using the Performance Max framework to absorb more and more campaign types. Shopping, local, search, display, video - and now local pay-per-lead. PMax started as a way to consolidate asset-based advertising across channels with AI-driven placement. Using it as the structural container for what was previously a verified, human-reviewed lead product is a significant stretch of the format.
That matters because Performance Max campaigns are already complex to manage, analyse and attribute properly. Adding a pay-per-lead variant increases the demand on advertisers to understand what signals the campaign is optimising against, how bidding is being set, and whether the leads being counted are being counted consistently with how they were defined under the old Local Services model.
Advertisers running existing PMax campaigns for lead gen will need to be particularly careful about how these new pay-per-lead campaigns are structured in relation to what they already have running. If campaigns are competing for the same geography and service category, the interaction effects on budget and bidding could be unpredictable without deliberate separation at the campaign or account level.
Bidding Changes Are Where the Detail Will Matter Most
The move to Google Ads means bidding on what were Local Services campaigns will now be managed through the same interface and presumably the same bidding frameworks as the rest of the account. That is a step up in complexity for advertisers who previously set a rough budget and let Google handle delivery within the Local Services platform.
Smart Bidding requires strong conversion signals to function well. For pay-per-lead campaigns, that means the lead data feeding back into the account needs to be clean, consistent and timely. If the definition of a billable lead under the new structure differs from what was previously counted - or if lead quality varies significantly by service type or location - the bidding algorithm will be working with noisy data from day one.
The practical implication is that advertisers should not simply migrate and assume the bidding will self-correct. Importing historical lead data, setting realistic target CPAs based on actual qualified lead costs (not just billable contacts), and building in a review period before increasing budgets would be a sensible approach. Treating August 2026 as a reset rather than a continuation is probably the safer framing.
Reporting Consolidation Is Genuinely Useful, But Requires Setup
One of the clearest practical benefits of this change is that local lead performance will now appear inside Google Ads reporting alongside everything else. Advertisers who have been exporting data from the Local Services dashboard and stitching it together with Google Ads data manually - or trying to represent it inside GA4 or Looker Studio dashboards - will have a more direct path to unified reporting.
But that benefit only materialises if the account is set up to segment properly. Lead sources, campaign types and billing models need to be clearly distinguished in reporting from the start. Mixing pay-per-lead conversions with cost-per-click conversions in a single blended view will make it harder, not easier, to understand what is actually driving acquisition costs.
For agencies and in-house teams building dashboards in Looker Studio or pulling data through the Google Ads API, now is the right time to plan how the new campaign type will be represented. Custom columns, campaign labels and separate views for pay-per-lead versus standard campaigns will keep reporting meaningful rather than muddy.
Lead Quality Accountability Needs to Come With the Migration
Local Services Ads had a lead dispute process built in. If a lead was irrelevant, a duplicate, or spam, advertisers could flag it and potentially receive a credit. How that accountability mechanism translates into the Google Ads environment is not yet fully clear, but it is one of the most commercially important questions for lead gen advertisers to get answered before August 2026.
Pay-per-lead only makes commercial sense if the leads being paid for are genuinely qualified. If the dispute and credit mechanism becomes harder to access, or if the definition of a billable lead drifts, the effective cost per acquisition could rise without the campaign reporting showing it. Advertisers should be building lead quality checks into their CRM or call tracking setup so they have independent data to assess what they are actually paying for.
Offline conversion imports, call tracking integration and CRM-based lead scoring are the tools that create that accountability. Advertisers who have not yet connected their Google Ads conversion tracking to downstream lead quality data are more exposed to this risk than those who already pass qualified lead signals back into the platform. If there is one preparation task worth prioritising before the migration, this is it.
What to Do Before August 2026
Audit your current Local Services Ads performance properly - not just lead volume, but cost per qualified lead, lead source by service category, and dispute rate. That baseline is what you will need to evaluate whether the migrated campaigns are performing equivalently or worse.
Review your existing Google Ads account structure. If you are running PMax campaigns for similar service categories or geographies, plan how the new pay-per-lead campaigns will sit alongside them. Unplanned overlap between campaign types chasing the same conversions is one of the more common ways PMax accounts accumulate waste.
Get your conversion tracking in order. Pay-per-lead campaigns optimised by Smart Bidding will only perform as well as the signal quality you feed them. If your lead-to-sale data is sitting in a CRM that has no connection to Google Ads, the next few months are the right window to build that connection - before the bidding algorithm starts making decisions based on whatever it can see.