PUT /v1/ads/{adId} with targeting.customLocations returns 400:
▎ "Google does not support updating customLocations after creation; editable fields are devices, locations (or the equivalent top-level countries/regions/cities/zips/metros), languages, keywords, and negativeKeywords."
That matches your docs, so it is intended. The problem is the fit with the original request. Our customers are local service businesses — a plumber, a painter, a window fitter. Their service area is a town plus a radius, not a list of
cities, so they are created with customLocations. "Region is the single most common thing a local business wants to change" was the reason for the request, and for exactly those campaigns nothing changed: the only way to correct a service
area is still to delete the campaign and rebuild it, losing its history.
Ask: support replacing customLocations on an existing campaign, with the same full-replacement semantics as the other location kinds.Please authenticate to join the conversation.
In Review
Feature Request
About 2 hours ago

JW Stukart
Get notified by email when there are changes.
In Review
Feature Request
About 2 hours ago

JW Stukart
Get notified by email when there are changes.