LSA-to-PMax Migration Breaks Agency Reporting Systems

The recent migration of Local Services Ads (LSA) to Google Ads has significant implications for agencies that use the Google Ads API. While the change is being discussed as an advertiser-facing update, it also affects how campaigns are represented in the Google Ads API.

Agencies need to be aware that the way LSA campaigns are identified will change after migration. This is particularly important for those that rely on the Google Ads API for reporting, budget automation, CRM synchronization, or custom scripts.

The issue arises because the software connected to these accounts may identify campaigns differently after migration. If an agency uses the Google Ads API and relies on `advertising_channel_type = LOCAL_SERVICES` to find LSA campaigns, it will stop working if it doesn't also recognize the Local Services subset of PERFORMANCE_MAX.

This is not a theoretical concern; Google's current API documentation distinguishes traditional LSA campaigns from Local Services Performance Max campaigns. Traditional LSA campaigns use `advertising_channel_type = LOCAL_SERVICES`, while Local Services Performance Max campaigns use `advertising_channel_type = PERFORMANCE_MAX` and expose a separate `pmax_campaign_settings.local_services_enabled` field.