LSA vs Standard Performance Max After Migration

Migrated LSA is a specialized Performance Max campaign, not a standard cross-channel Performance Max campaign with a Local Services label. Google moved the account into Google Ads and placed it in the Performance Max campaign family while preserving the Local Services pay-per-lead model.

Google's LSA migration announcement defines the specialized campaign as pay per lead, keywordless, and eligible on Search and Maps. It also says advertisers continue to pay only for valid leads. Those rules form the practical boundary between migrated LSA and standard Performance Max.

Use the campaign contract, not the campaign-type label alone, to identify the account. Review billing, placements, service eligibility, assets, Business Profile information, lead destination, and bidding controls before copying a standard Performance Max playbook into an LSA review.

The table below uses Google's July 2026 migration documentation and current Performance Max documentation. A standard Performance Max campaign can vary by goal, feed, market, and account configuration. The LSA column describes Google's specialized migrated pay-per-lead campaign.

The largest practical differences are the commercial unit, eligible placements, service and screening context, creative requirements, and lead workspace. Those differences affect reporting, staffing, quality review, and campaign decisions.

Google's public announcement describes a unified Google Ads experience with a specialized Performance Max campaign type. The change gives Local Services advertisers a shared campaign table, familiar Google Ads access controls, Change history, reporting tools, and account-management structure.

The Why Google is moving LSA into Google Ads separates confirmed migration mechanics from PrimeLSA's analysis of Google's broader automation and campaign consolidation direction. The Performance Max label is evidence of shared infrastructure. It does not prove that every standard Performance Max feature or placement applies to LSA.

For operators, the safer naming convention is specialized LSA Performance Max when discussing the migrated campaign. That phrase keeps the Google Ads campaign family and the Local Services business model visible in reports, tickets, and client conversations.

Google says migrated Local Services campaigns serve on Search and Maps. The provider result can still present Local Services information such as business name, rating, service category, availability, contact actions, and eligible trust treatment. Placement depends on eligibility, demand, market, and Google's systems.

Google's Performance Max channel guide lists Search, Maps, YouTube, Discover, Gmail, and the Google Display Network for standard Performance Max. Do not use that broader list to tell an LSA owner that migration automatically adds video, Gmail, Discover, or Display inventory.

When channel reach is part of the media plan, report the two campaigns separately. A migrated LSA campaign covers the specialized Local Services opportunity. A standard Performance Max campaign may cover a broader set of Google inventory under its own goals, budget, assets, attribution, and quality controls.

Google says the migrated campaign remains pay per valid lead. In the Google Ads campaign table, Conversions means the leads for which Google charged the advertiser, Cost is campaign spend, and Cost / conv. is spend divided by those charged leads.

Lead quality still needs a separate business layer. Charged lead, qualified lead, booked job, completed job, and revenue are different measures. Lead Manager and campaign reporting show Google's records; intake, CRM, dispatch, and accounting systems supply downstream business outcomes.

A standard Performance Max campaign uses its selected conversion goals and bidding framework. Its conversions can represent purchases, forms, calls, store activity, imported outcomes, or other configured actions. Do not merge those conversions with charged LSA leads unless the reporting model preserves source, definition, and deduplication.

Migrated LSA remains keywordless. Service categories, eligible job types, service areas, business information, operating schedule, and Local Services context shape the campaign. The migration does not create a keyword tab that replaces those controls.

Google says photos and callouts move into the specialized campaign. Standard headlines, videos, and sitelinks do not apply. Review the Assets area to confirm transferred photos and callouts, but do not mark the migration incomplete because a standard Performance Max asset-strength prompt or creative checklist does not fit the LSA campaign.

Standard Performance Max commonly groups creative and destination inputs in asset groups. It can use audience signals, search themes, feeds, brand controls, and other supported settings depending on campaign configuration. Those controls belong to the standard campaign's plan, not the migrated LSA transfer inventory.

The Local Services product still depends on supported category and market eligibility. Business details, verification or screening requirements, provider information, and the connected Business Profile remain part of account review. A standard Performance Max campaign does not grant Local Services eligibility.

Past LSA lead history moves to Lead Manager, including the history Google lists in its announcement. New lead review also happens under Goals > Conversions > Leads. Campaign performance reports from the former LSA dashboard do not transfer into the new Google Ads reporting timeline.

Keep permissions narrow and test them by task. An account user who can view campaigns may still need the correct access to inspect lead detail, messages, or permitted recordings. Record who can see the campaign, Lead Manager, Business Profile connection, billing, and exports.

Use the migrated LSA campaign for eligible Local Services demand when the business can answer, qualify, book, and review pay-per-lead contacts. Use a standard Performance Max campaign only when its broader channel reach, conversion goals, creative plan, landing experience, and measurement design have a defined role.

Running both can be reasonable. Give each campaign a written job. Separate budgets and definitions, preserve source in the CRM, and review overlap before adding performance together. Avoid treating two platform conversion totals as unique customers without a deduplication method.

Do not rebuild a migrated LSA campaign as standard Performance Max merely to make the label feel familiar. First verify that the specialized campaign transferred. Google currently says advertisers cannot directly create new pay-per-lead campaigns in Google Ads, so an unnecessary replacement can create an access and recovery problem.

On Day 1, confirm the business, Customer ID, campaign name, status, and Local Services identity. Compare services, areas, schedule, budget, Target CPA, Business Profile, photos, and callouts with the saved pre-migration record.

Open Goals > Conversions > Leads and confirm transferred history, new lead rows, charged status, contact types, and user access. Add Conversions, Cost, and Cost / conv. to the campaign table. Preserve Change history beside any correction.

Use Google's up-to-two-week stabilization guidance as a review window. Correct transfer, access, routing, or verification defects promptly. Keep optional bidding and budget experiments out of the initial transfer check when the account can remain safely unchanged.

For approved technical workflows, Google Ads API documentation for Local Services campaigns documents a Local Services-enabled Performance Max indicator at campaign.pmax_campaign_settings.local_services_enabled. Google's documentation says this setting is available beginning with Google Ads API v24.2.

Google Ads API documentation for Performance Max asset groups documents a google_local_services_info asset-group field and an exemption from minimum asset requirements for Local Services-enabled Performance Max. It also says the category identifier is immutable after asset-group creation. Check the current API version and account permissions before building an integration.

Google currently documents update support for existing campaigns under its stated access conditions and says Local Services campaign creation through the API is not available. Keep API credentials and customer lead data out of public files. The UI remains the primary verification path for most owners.

Source review completed July 30, 2026. The specialized campaign's pay-per-lead model, Search and Maps placement, keywordless matching, transferred assets, reporting labels, Lead Manager destination, setup availability, and stabilization guidance come from Google's LSA migration announcement.

The standard Performance Max channel list comes from Google's Performance Max channel guide. Technical identifiers and asset-group exceptions come from Google Ads API documentation for Local Services campaigns and Google Ads API documentation for Performance Max asset groups. Campaign-role, reporting-separation, deduplication, and review recommendations are PrimeLSA operating guidance.