The Hidden API Problem in Google’s LSA-to-PMax Migration

https://hackernoon.imgix.net/images/UtmXuhaZqkOQfufBcaDWTOH6gd93-2a83b1g.png

Google's migration of Local Services Ads into Google Ads is being discussed mainly as an advertiser-facing change. The more consequential change for agencies may be happening underneath the interface: the way Local Services campaigns are represented in the Google Ads API. Budgets will move, reporting will change, bidding options will change, and agencies will manage campaigns from a different interface.

There is another problem that deserves attention: the software connected to those accounts may identify the campaigns differently after migration.

That matters if an agency uses the Google Ads API for reporting, budget automation, CRM synchronization, Looker Studio pipelines, data warehouses, or custom scripts. A workflow that currently finds LSA campaigns by advertising_channel_type = LOCAL_SERVICES can stop finding them after migration if it does not also recognize the Local Services subset of PERFORMANCE_MAX.

This is not a theoretical concern. Google's current API documentation now distinguishes traditional Local Services campaigns from...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE

Read more