Hi,

I got a private reply, but it looks like Gmail may have gotten confused and 
split the email thread so let me reiterate the current details here.
I've tried using the place_id to retrieve data from the Places web service 
as suggested in the Google Ads API documentation: 
asset.location_asset.place_id 
<https://developers.google.com/google-ads/api/fields/v14/asset#asset.location_asset.place_id>

However, all of the requests I can make there to get location extension 
data (e.g. address, phone #) cost money to use 
<https://developers.google.com/maps/documentation/places/web-service/usage-and-billing#places-details>
.
Advertisers using the Google Ads API can handle a large volume of 
locations, so the single-place-id, rate-limited requests to the Places API 
look both inefficient and costly.

I think it's unlikely that Google would just remove the data from the Ads 
API and force their API users to buy the data back.
Instead, I think I haven't found the correct request in the Places API.

Could you help me understand what the new workflow to get Location data is?
Migration from Location Extensions to Location Assets is already underway.

Thanks,
Kevin

On Wednesday, August 30, 2023 at 6:58:41 PM UTC-7 Kevin wrote:

> Hi,
>
> I started using the Places API but found out recently that the Place 
> Details 
> <https://developers.google.com/maps/documentation/places/web-service/details> 
> request 
> that gives the address and phone # information is not free.
> Is there a different request I can use to get the address information for 
> Location extensions without paying money for each request?
>
> Thanks,
> Kevin
>
> On Tuesday, July 18, 2023 at 11:54:41 AM UTC-7 Google Ads API Forum 
> Advisor wrote:
>
>> I can't guarantee the future, but we don't have a policy of charging for 
>> APIs. Originally, you had to pay to use the Ads API but it was not a 
>> successful use case and it was abandoned years ago.
>>
>> Google has a number of APIs that can include location details. The 
>> thinking was to have it all in one place so that it is a consistent 
>> experience across multiple products.
>>
>>
>>   
>> This message is in relation to case "ref:_00D1U1174p._5004Q2j1cSB:ref"
>>
>> Thanks,
>>   
>> [image: Google Logo] 
>> Bob Hancock 
>> Google Ads API Team 
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0c6d8bbe-450d-4076-84d7-2edd9039e8f5n%40googlegroups.com.
  • Re... Kevin
  • Re... Kevin
  • Re... duca...@gmail.com
  • Re... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
  • Re... Kevin
  • Re... 'Google Ads API Forum Advisor' via Google Ads API and AdWords API Forum
  • Re... Kevin
  • Re... Kevin
  • Re... Kevin
  • Re... Kevin
  • Re... Kevin

Reply via email to