Google LSAs Expose GBP Phone Dependency
Google Local Service Ads reportedly used Business Profile phone numbers instead of Google Ads call assets, threatening paid local attribution and call tracking integrity.
The News
Search Engine Roundtable reported on September 25, 2026 that Google Local Service Ads were showing the phone number tied to a Google Business Profile rather than the Google Ads call asset number. The reported mechanism affects local ad formats using both location and call assets. Google’s response said ads featuring specific business locations may route calls to numbers associated with those locations.
The OPTYX Analysis
This is a local discovery signal because the business listing is overriding, or at least competing with, the paid call-tracking configuration. The systemic mechanism is location-asset precedence, where Maps and Business Profile identity data becomes the operational source for a commercial action. Strategically, Google is tightening the connection between local identity, ads, and user contact paths. The change matters because the phone number is not just profile data; it is the attribution bridge between local intent, paid spend, lead routing, and offline conversion measurement.
Enterprise Impact
The exposed operator is the multi-location marketer, agency PPC lead, franchise growth team, or call analytics owner relying on call asset tracking for local-service campaigns. The vulnerability is silent attribution breakage: calls may still arrive, but campaign source, routing logic, and lead quality reporting can degrade. The required move is a phone-path audit across GBP, location assets, call assets, forwarding numbers, CRM ingestion, and store-level routing. Enterprises should test live ad surfaces by market before interpreting LSA performance swings as demand changes.
Locked Recommendations
This signal has triggered a material consequence alert. Strategic recommendations are locked pending analyst clearance.