Updated 16 Oct 2026: Google Ads API v26 now supports creating Local Services Performance Max pay-per-lead campaigns, with immutable local_services_enabled, required business-profile identifiers and lead-linking; existing migration guidance retained.

Key details

  1. Google began migrating selected U.S. Local Services Ads accounts in August 2026.
  2. The destination is a specialized Performance Max campaign with pay-per-lead goals inside Google Ads.
  3. Migrated campaigns remain keywordless, continue to serve on Search and Maps, and continue charging for valid leads.
  4. The standalone Local Services Ads dashboard is no longer accessible after an account migrates.
  5. Historical campaign performance reports do not transfer into Google Ads.
  6. Weekly budgets are converted into daily average budgets.
  7. Manual bidding and vertical-level Target CPA settings are not supported in the migrated campaign model.
  8. Google says broader U.S. migrations continue later in 2026 and remaining categories/non-U.S. accounts move during 2027.
  9. October 14 Google Ads API v26 supports creating Local Services Performance Max campaigns with local_services_enabled set at creation and required country_code/listing_id.

What builders should take away

  1. Export Local Services Ads historical reports before your migration date; Google says campaign-level history will not carry into the new Google Ads experience.
  2. Snapshot current weekly budget, lead volume, cost per lead, service mix and Target CPA settings so you have a clean pre-migration baseline.
  3. If different service categories need different economics, plan separate campaigns rather than relying on the old vertical-level Target CPA controls.
  4. Treat the first one to two weeks after migration as a transition period and compare backend booked jobs/revenue as well as Google-reported leads.
  5. Audit integrations, dashboards and agency automation that depend on the old LSA dashboard or report exports; management is moving into Google Ads.
  6. Confirm that the migrated campaign still reflects the correct services, locations, schedule, business photos, routing and verification state after cutover.
  7. For new automated campaigns, upgrade to Google Ads API v26 and set the immutable local_services_enabled flag and Google Business Profile listing ID correctly at creation.

What changed

Google began the first phase of migrating Local Services Ads into Google Ads in August 2026. Selected U.S. home and storefront service advertisers — including plumbing, HVAC, electrical, appliance repair, house cleaning, lawn care, roofing, pest control and moving — are being converted into a specialized Performance Max campaign type with pay-per-lead goals. Google says the core local model remains: these campaigns continue to charge for valid leads, remain keywordless and serve on Google Search and Maps. But campaign management moves out of the standalone Local Services Ads dashboard. Historical campaign performance reports do not migrate, weekly budgets are converted to daily averages, manual bidding is removed, and separate vertical-level Target CPA settings are collapsed unless advertisers split categories into separate campaigns. Google says the migration expands to broader U.S. groups later in 2026 and to remaining categories and non-U.S. accounts through 2027. On October 14, Google released Google Ads API v26, adding creation support for the specialized Local Services Performance Max campaigns: set PmaxCampaignSettings.local_services_enabled at campaign creation (immutable afterward) and provide country_code and Google Business Profile listing_id in LocalServicesPmaxCampaignSettings. The API also adds lead-to-campaign linking, coupon lead type and message-lead conversion category. Client libraries and code must be upgraded to v26 for these features.

Why it matters

For local-service businesses and the agencies or software builders managing their acquisition, this is a platform migration with real reporting and control consequences. Losing the old dashboard after migration means historical data needs to be exported before the account moves. The shift from weekly to daily budget framing and the removal of manual and vertical-specific bidding controls can also change how advertisers structure campaigns and compare lead economics across services. Google is preserving the pay-per-lead proposition, but operational ownership is moving into the broader Performance Max/Google Ads system, where automation and campaign structure matter more. The v26 API release resolves an important integration uncertainty: agencies and software vendors can now programmatically create this specialized campaign type and associate leads, though the local_services_enabled setting cannot be changed after creation. Integrations must explicitly support v26 and account eligibility.

The migration is already underway

Google says the first phase began in August 2026 for selected U.S. home and storefront service advertisers. Account administrators receive advance notices before their individual migration date. Broader service-area and custom-configuration groups are scheduled later in 2026, with remaining categories and non-U.S. accounts moving through 2027.

The pay-per-lead model survives the platform move

Google describes the destination as a specialized Performance Max campaign with pay-per-lead goals. Unlike ordinary Performance Max campaigns that are typically CPC-based and can serve across more Google inventory, these migrated local campaigns remain focused on Search and Maps and continue charging for valid leads rather than ordinary clicks.

Historical campaign reports do not follow the account

After migration, advertisers lose access to the old Local Services Ads dashboard and are redirected into Google Ads. Google explicitly says prior campaign-level performance metrics such as impressions, clicks, weekly spend and ad-level reports will not transfer. Advertisers who need comparison history should export or capture that data before migration.

Budget and bidding semantics change

Google converts the historical average weekly budget into a daily average by dividing it by seven. Manual bidding, including maximum cost-per-lead controls, is no longer supported after migration, and vertical-level Target CPA settings are replaced by a campaign-level target. Advertisers that need distinct bidding economics for different services may need separate campaigns.

Migration can temporarily disturb performance

Google says the transition is designed for minimal downtime but advises allowing up to two weeks for the migration to complete fully and for campaign performance to return to stable levels. That makes the cutover a measurement event: agencies should avoid interpreting short-term post-migration lead-cost changes as a durable trend without accounting for the transition period.

October 14: Google Ads API v26 adds campaign creation

Google's v26 announcement now documents a create path for Local Services Performance Max campaigns. Integrators must set PmaxCampaignSettings.local_services_enabled during creation; it cannot be toggled later. LocalServicesPmaxCampaignSettings requires country_code and Google Business Profile listing_id. The release adds lead-to-campaign linking, coupon lead type and message lead conversion category. This does not undo historical LSA report loss or bring back manual bidding. Upgrade client libraries and review v26 fields before automating new campaign creation.

What to watch next

  • Whether migrated advertisers see systematic changes in lead volume, lead quality or cost after the stabilization period.
  • The promised download path for historical Local Services Ads performance data.
  • Whether later migration phases change booking, bidding or lead-dispute behavior for advertisers with more complex setups.
  • Expansion beyond the first U.S. service categories and the exact timing for non-U.S. accounts.
  • Whether subsequent Ads API versions add broader reporting, lead dispute and lifecycle controls for the specialized campaign type.

Still unclear

  • Migration timing is account-specific within Google’s phased rollout, so not every eligible advertiser moves at the same time.
  • Google describes the destination as Performance Max with pay-per-lead goals, but some ordinary Performance Max documentation and controls do not apply to this specialized local campaign type.
  • Real-world post-migration changes in lead quality and cost are not yet established across a broad independent dataset.
  • API support is documented in v26, but account and campaign eligibility may vary across the phased migration.

Sources

Direct reading behind this dossier.

4 sources
Announcing v26 of the Google Ads API
Google Ads Developer Blog primary API release announcement

Local Services PMax campaign creation, immutable flag, required fields and lead linking.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment