Local Services Ads Are Moving to Google Ads: What PMax Pay-per-Lead Changes

Google is retiring the standalone Local Services Ads management experience and moving existing campaigns into Google Ads as a specialized Performance Max campaign type with pay-per-lead goals. This review explains the 2026–2027 migration timeline, the first affected US service categories, what remains unchanged for advertisers and consumers, and which bidding, budgeting, reporting, and Google Business Profile workflows require preparation.

Practical takeaway: this is primarily a migration of the campaign control layer, not a conversion of Local Services Ads into ordinary cross-channel Performance Max. Ads are expected to remain keywordless, limited to Google Search and Maps, and billed for valid leads. Advertisers should not rebuild a working acquisition strategy merely because the campaign label changes, but they should export historical reports, audit Google Business Profile data, record current settings, and prepare for automated bidding and a campaign-level cost target.

Executive summary

Google has announced that existing Local Services Ads, commonly shortened to LSA, will move into the Google Ads interface as Performance Max campaigns with pay-per-lead goals. The phased migration is scheduled to begin in August 2026 with selected US home-service advertisers. Broader US migration follows, while the remaining categories and advertisers outside the United States are scheduled to move during 2027.

The first named US verticals are:

• plumbing;
• heating, ventilation, and air conditioning, or HVAC;
• electrical services;
• appliance repair;
• house cleaning;
• lawn care;
• roofing;
• pest control;
• moving services.

The phrase “moving to Performance Max” can be misleading. Standard Performance Max is designed to distribute ads across Google inventory such as Search, YouTube, Display, Discover, Gmail, and Maps. The migrated Local Services format is a constrained pay-per-lead variant: Google says it will continue to serve only on Search and Maps, use service categories and local business information rather than advertiser-managed keyword lists, and charge for eligible leads rather than ordinary ad clicks.

For that reason, the claim that “LSA was already almost PMax” is directionally correct. Local Services Ads already relied heavily on automated matching, auction-time signals, service areas, job types, business profile information, and automated lead-focused bidding. The migration formalizes that architecture inside Google Ads rather than introducing a completely new acquisition model.

However, “nothing important changes” would be too broad. The auction and customer experience remain familiar, but the operating model changes in several material ways:

• the standalone Local Services Ads dashboard is being retired;
• manual maximum-cost-per-lead bidding is being removed;
• separate vertical-level cost targets are replaced by a campaign-level target;
• weekly budgets become average daily budgets;
• core business identity data is synchronized more tightly from Google Business Profile;
• Lead Manager in Google Ads replaces the old lead inbox;
• historical campaign performance reports do not transfer automatically.

The last point is the most urgent. Google says customer lead history will move, but previous campaign-performance reporting will not. Advertisers and agencies should export their historical reports before the assigned migration date.

What Google is actually changing

The change is best understood as the retirement of a separate product interface. Local Services Ads will continue to exist as a distinct local lead-generation format, but campaign management, budgeting, access, reporting, and lead handling will move into the broader Google Ads environment.

Google is expected to notify affected advertisers before conversion. Published rollout guidance describes an initial notice approximately 14 days before migration, a reminder approximately seven days before migration, and a completion message after the account has moved. The precise date is account-specific, so the notification email and in-product banner are more important than the general rollout calendar.

The conversion is automatic. Existing budgets, settings, business assets, and lead history are intended to transfer, but advertisers should not assume that every field will look or behave exactly as it did in the Local Services interface. A post-migration audit is still required.

Migration timeline

Period	Expected scope	What advertisers should do
August 2026	An initial group of US advertisers in plumbing, HVAC, electrical services, appliance repair, house cleaning, lawn care, roofing, pest control, and moving.	Watch for the account-specific notice, export historical reports, and audit current campaign and Google Business Profile settings.
Later in 2026	Broader groups of US Local Services advertisers, including more account and business configurations.	Standardize agency and multi-location workflows before each account receives its migration date.
2027	Remaining categories and advertisers, including Local Services Ads accounts outside the United States.	Non-US advertisers should not treat the later date as a reason to postpone reporting exports or profile cleanup.

The rollout is phased rather than a single global switch. Google can also adjust sequencing as it observes migration quality, so a category or market may move later than the broad calendar suggests.

How global are Local Services Ads?

Local Services Ads remain a geographically limited product. Google currently publishes country-specific Local Services Ads provider terms for 12 markets:

• United States;
• Canada;
• Austria;
• Belgium;
• France;
• Germany;
• Ireland;
• Italy;
• Netherlands;
• Spain;
• Switzerland;
• United Kingdom.

This list should be read carefully. A country-specific terms page indicates that the product operates in that market, but it does not mean that every service category is available in every city. Eligibility, screening, lead types, messaging features, and category coverage can vary by country and location. Google’s onboarding flow and country-specific eligibility page remain the final test for an individual business.

It is reasonable to describe LSA as a US-led format. The United States has a much broader catalogue of eligible service categories and a longer operating history, while international markets generally have narrower category coverage. That explains why Google is starting with selected US home-service verticals and scheduling the non-US migration for 2027.

What stays the same after migration

Advertisers still pay for valid leads

The core commercial model is not changing. Local Services Ads are not becoming conventional cost-per-click Search campaigns. Advertisers continue to pay for eligible lead interactions that Google classifies as valid, such as supported calls, messages, or bookings, depending on the market and category.

This distinction remains important: a Google-valid lead is not necessarily a qualified prospect, booked job, or profitable customer. The platform determines whether the interaction meets its billing rules; the advertiser still needs a CRM or operational system to measure whether the lead was accepted, qualified, booked, completed, and profitable.

Delivery remains limited to Search and Maps

The migrated campaigns are not expected to expand automatically into YouTube, Gmail, Discover, or the Google Display Network. They remain focused on high-intent local placements in Google Search and Google Maps.

This is the clearest difference from the standard Performance Max model, which is built to optimize across multiple Google channels. The new campaign type uses Performance Max infrastructure and automation, but it preserves the narrower Local Services inventory.

The format remains keywordless

Advertisers do not build traditional keyword lists. Matching continues to depend on the business category, selected job types, service areas, business profile, customer location and intent, and other contextual signals. Negative and positive keyword management therefore does not become the main optimization workflow after migration.

Verification and local trust signals remain central

Local Services advertisers still need to satisfy the applicable screening and verification requirements for their category and market. Reviews, responsiveness, services offered, service areas, business hours, and profile completeness continue to influence how competitive the business is. Eligible Google Verified status is intended to carry into the migrated campaign, although material business-identity changes can still trigger review or re-verification.

Customer lead history transfers

Google says existing lead history, message threads, and supported historical lead records will move into the new lead-management environment. This is different from campaign performance history, which advertisers must export separately.

What changes operationally

Area	Before migration	After migration	Practical consequence
Management interface	Standalone Local Services Ads dashboard and inbox.	Google Ads campaign management and Lead Manager.	Access roles, agency processes, notifications, and reporting workflows need to be checked.
Campaign type	Local Services Ads presented as a separate product.	Specialized Performance Max campaign with pay-per-lead goals.	The name changes more than the inventory or billing model.
Bidding	Automated Maximize leads, optional target CPL, and a manual Max per lead option in eligible configurations.	Automated bidding; manual maximum-cost-per-lead control is removed.	Advertisers lose a hard bid ceiling and must manage economics through budget, campaign structure, lead quality, and the available campaign target.
Cost targets	Some accounts can use different targets by service vertical.	A campaign-level target replaces separate vertical-level targets.	Services with very different job values or close rates may need separate campaigns rather than one blended target.
Budget	Average weekly budget in the Local Services interface.	Average daily budget in Google Ads.	Google converts the weekly amount using approximately weekly budget / 7. Advertisers should verify the new daily amount and monthly spending limit.
Business data	Some details can be managed separately between LSA and Google Business Profile.	Business name, physical address, and standard opening hours synchronize more directly from Google Business Profile.	Google Business Profile becomes a more important source of truth. Incorrect or outdated profile data can immediately affect the campaign.
Lead management	Local Services lead inbox.	Lead Manager in Google Ads.	Teams must verify call, message, booking, notification, and assignment workflows.
Historical performance	Reports available in the Local Services dashboard or through supported reporting tools.	New reporting begins in Google Ads; previous campaign-performance reports do not automatically transfer.	Exporting history before migration is essential for year-over-year analysis, agency reporting, and bid baselines.
Business callouts	Some legacy callouts, including BBB-related elements in applicable US accounts.	Certain legacy callouts are no longer supported.	Review the migrated profile and replace missing differentiators with supported business information and assets.

Weekly budgets become daily budgets

This change is visible, but it is not entirely new at the technical level. Google already documents that Local Services budgets exposed through the Google Ads API are represented as daily amounts, calculated from the weekly budget. The interface migration therefore aligns the visible budget model with infrastructure that was already partly shared.

Even when the mathematical conversion is correct, daily pacing can feel different from a weekly target. Demand is uneven for emergency plumbing, HVAC, moving, pest control, and similar services. Advertisers should compare:

• the old average weekly budget;
• the migrated average daily budget;
• the Google Ads monthly spending limit;
• the business’s actual capacity to answer and fulfil leads by day of week.

Manual maximum-cost-per-lead bidding ends

Google has already been recommending automated Maximize leads bidding for Local Services Ads, and its current target-CPL documentation describes auction-time optimization based on historical and contextual signals. The migration removes the remaining manual maximum-per-lead option and makes automation the normal operating model.

This is not necessarily negative for every advertiser. A model can respond faster than a fixed bid to location, time, demand, competition, and expected lead probability. The risk is loss of a hard ceiling. Businesses with strict unit economics should therefore measure cost per accepted lead, booked job, and acquired customer, not only the platform’s billed CPL.

One campaign-level cost target can blend unlike services

A plumber may accept a higher acquisition cost for a sewer replacement than for a minor tap repair. An HVAC company may value an installation lead very differently from a maintenance enquiry. When multiple service categories share one campaign-level target, Google is optimizing toward a blended result.

Advertisers should consider separate campaigns where categories have materially different:

• revenue per completed job;
• gross margin;
• lead-to-booking rate;
• service area;
• operating schedule;
• staffing capacity;
• acceptable acquisition cost.

Campaign separation should follow business economics, not merely the desire for more control. Excessive fragmentation can reduce data and slow automated learning.

Google Business Profile becomes more operationally important

Business name, physical address, and standard hours are expected to synchronize from Google Business Profile. That reduces duplicate maintenance, but it also means that profile governance affects paid lead generation more directly.

Before migration, confirm that the profile contains the correct legal or customer-facing name, address or service-area configuration, ordinary opening hours, phone details, website, categories, photos, and verification status. Avoid unnecessary last-minute identity changes: significant name or address edits can require another verification review and may interrupt ad serving.

Historical performance reporting does not migrate

This is the only clearly irreversible migration issue. Lead records and conversations are operational data; campaign performance reports are analytical history. Google says the former transfers and the latter does not.

Export enough detail to preserve useful comparisons, including where available:

• spend;
• charged leads;
• credited or disputed leads;
• average cost per lead;
• lead type;
• service category;
• location or service area;
• date and time;
• booking or disposition information;
• campaign and account identifiers.

Agencies managing multiple businesses should export at account level and preserve a mapping between the old Local Services account, the client, the Google Ads customer ID, and the migrated campaign. Google’s Local Services API can help manager-account users retrieve lead, cost, and performance data at scale before the reporting break.

Was Local Services Ads already “almost PMax”?

Yes, in the sense that matters for campaign mechanics. Long before this migration, LSA already used many features associated with Google’s AI-led campaign architecture:

• no advertiser-managed keyword list;
• matching based on service categories, job types, service areas, and contextual intent;
• auction-time prediction of lead likelihood;
• automated Maximize leads and target-CPL bidding;
• heavy reliance on business information, reviews, verification, and responsiveness;
• optimization around a business outcome rather than website traffic.

The migration therefore looks less like Google replacing LSA and more like Google absorbing its management layer into the same campaign, permissions, reporting, API, and automation environment used by the rest of Google Ads.

There are still important reasons not to call the format “ordinary PMax”:

Dimension	Standard Performance Max	LSA after migration
Inventory	Can use Search, YouTube, Display, Discover, Gmail, Maps, and other eligible Google inventory.	Search and Maps only.
Billing focus	Campaigns optimize to conversions or conversion value within the normal Google Ads auction and charging model.	Advertiser pays for eligible Local Services leads.
Eligibility	Available to a broad range of advertisers and goals.	Restricted by country, service category, screening, and verification rules.
Primary inputs	Conversion goals, creative asset groups, feeds, audience signals, search themes, and other campaign inputs.	Business profile, services, job types, service areas, schedule, reviews, photos, lead settings, budget, and cost target.
Customer action	Often sends the user to a website, app, store, or Google-hosted destination.	Designed to generate direct local calls, messages, and supported bookings.

A useful shorthand is: PMax in infrastructure and automation; LSA in inventory, eligibility, customer experience, and billing.

Where performance can still change

The migration is not expected to create a new source of demand by itself. The same local searches and Maps interactions remain the core inventory. Performance can nevertheless change because the controls and data inputs around the auction are changing.

1. Loss of a manual bid ceiling

Accounts using manual maximum-per-lead bidding move into automated bidding. Cost may become more responsive to auction conditions, but advertisers lose a simple maximum bid control. A sensible target should be based on downstream economics:

maximum sustainable lead cost = expected revenue per lead × gross margin × acceptable marketing share

That calculation should use CRM outcomes, not Google’s valid-lead count alone.

2. A blended target can shift volume between services

When one campaign contains several services, the algorithm may favor the category that produces the easiest or cheapest valid lead, not necessarily the category with the highest profit after the job is completed. Monitor category mix, lead acceptance, booking rate, revenue, and margin after migration.

3. Daily budget pacing can expose capacity problems

A mathematically equivalent daily budget does not guarantee identical lead timing. If a business cannot answer calls during evenings, weekends, or peak demand, wasted opportunities can increase even when the platform CPL looks stable. Service schedule and staff availability should be reviewed together.

4. Google Business Profile errors become paid-media errors

Incorrect hours, address, name, category, or verification status can now affect both organic local presence and paid Local Services delivery more directly. Agencies should define who owns Google Business Profile changes and how those changes are approved.

5. Over-editing can prolong instability

Google’s current Local Services bidding guidance says automated models can need approximately two weeks to adjust and produce representative results. After migration, correct obvious configuration errors immediately, but avoid reacting to every daily fluctuation with repeated budget, target, category, or service-area changes.

6. A new interface does not solve lead-quality measurement

Local Services Ads can report billed leads, but the business must still determine whether those leads became qualified opportunities and revenue. The minimum useful measurement chain is:

Optimizing only to platform CPL can hide low answer rates, duplicate enquiries, jobs outside the profitable service mix, weak sales follow-up, and high cancellation rates.

Migration checklist for advertisers and agencies

Before the assigned migration date

• [ ] Export historical performance reports. Preserve raw files as well as dashboard summaries.
• [ ] Record the current setup. Save the weekly budget, bid mode, cost targets, service categories, job types, service areas, ad schedule, phone and message settings, photos, callouts, and lead-notification rules.
• [ ] Audit Google Business Profile. Verify the business name, address or service-area setup, standard and special hours, primary phone, website, categories, photos, and verification status.
• [ ] Review access. Confirm that the advertiser and agency have the required Google Ads and Google Business Profile permissions and that the migration notification email is monitored.
• [ ] Map old and new identifiers. Document the Local Services account, Google Ads customer ID, business location, and expected migrated campaign name.
• [ ] Review campaign structure. Identify service categories whose job values, margins, close rates, locations, or schedules are too different for one blended cost target.
• [ ] Define the lead workflow. Assign ownership for calls, messages, bookings, lead status, response-time monitoring, and CRM entry.
• [ ] Build a pre-migration benchmark. Record cost per valid lead, accepted lead, qualified lead, booking, completed job, revenue, and margin for at least the most recent representative period.

Immediately after migration

• [ ] Confirm that the average daily budget matches the intended weekly and monthly spend.
• [ ] Verify the campaign-level target and automated bidding configuration.
• [ ] Check every service category, job type, service area, and schedule.
• [ ] Review synchronized business name, address, standard hours, phone details, photos, and supported callouts.
• [ ] Test Lead Manager, calls, messages, booking paths, email notifications, and user permissions.
• [ ] Confirm that eligible verification status and customer lead history are present.
• [ ] Annotate the migration date in agency reports, dashboards, CRM analysis, and business intelligence systems.
• [ ] Monitor lead mix and downstream quality for approximately two weeks before drawing conclusions from short-term volatility.
• [ ] Compare the new reporting data with the exported LSA baseline, allowing for the reporting-system break.

Additional agency actions

• [ ] Export every client account separately and retain unmodified source files.
• [ ] Update reporting connectors and campaign-type filters so the new pay-per-lead campaigns are not omitted or double-counted.
• [ ] Review manager-account and client-account access before the standalone dashboard is retired.
• [ ] Document whether the client, agency, or local branch owns Google Business Profile data.
• [ ] Explain the reporting discontinuity to clients before the first post-migration monthly report.
• [ ] Rebuild benchmarks around booked jobs and revenue rather than promising continuity based only on Google-reported CPL.

Bottom line

Google is not turning Local Services Ads into a full cross-channel Performance Max campaign. It is moving LSA into Google Ads and placing it on a Performance Max-style automation and management foundation while preserving the product’s defining characteristics: restricted eligibility, local Search and Maps inventory, keywordless matching, screening, and pay-per-valid-lead billing.

From the customer’s perspective, little should look radically different. From the advertiser’s perspective, the transition is meaningful but manageable. Automated bidding replaces the last manual bid option, weekly budgets become daily budgets, Google Business Profile becomes a stronger source of truth, lead handling moves to Google Ads, and historical performance reports must be saved manually.

The correct response is neither panic nor indifference. Treat this as an infrastructure migration with several operational consequences. Preserve the old data, validate the migrated configuration, measure lead quality beyond Google’s billing definition, and give the automated system enough stable data to learn.

Methodology and sources

This article is based primarily on Google’s official transition guidance and current Google Ads, Local Services Ads, and Google Business Profile help materials available on 28 July 2026. The review compares the announced migration with the existing LSA operating model: valid-lead billing, automated bidding, target CPL, weekly budgets, service areas, job types, screening, reporting, and Google Ads API representation. Rollout timing and transfer details were also cross-checked against contemporaneous industry coverage that reproduced Google’s announcement, because help-center pages can be updated during phased product launches.

• Google Ads Help: Local Services Ads transition to Performance Max campaigns with pay-per-lead goals
• Google Local Services Ads Additional Terms for Providers and country list
• Google Local Services Help: Getting started in the United States
• Google Local Services Help: How leads work
• Google Local Services Help: How bidding works
• Google Local Services Help: About Target CPL bidding
• Google Local Services Help: How to edit your budget
• Google Local Services Help: View reports and use the Local Services API
• Google Local Services Help: Service areas and job types
• Google Local Services Help: Screening and verification
• Google Ads Help: About standard Performance Max campaigns
• Google Ads Help: Average daily budgets and spending limits
• Search Engine Land: rollout summary based on Google’s announcement
• Search Engine Journal: migration workflow and advertiser changes
• PPC Land: detailed cross-check of Google’s transition guidance

This article is for advertising, analytics, and operational information only. It is based on Google documentation and rollout information available on 28 July 2026. Migration dates, eligible categories, supported countries, campaign controls, verification requirements, and reporting behavior may change by market, account, and rollout phase. metricfixer is not affiliated with Google, and no campaign outcome or lead quality is guaranteed.