Google ADS API location_view clarifications

[Oksana Sulyma]

Hi Google Ads API suport team.

I have a question to confirm with you. Working at migration from AdWords API to Ads API according to this guide . 

For AdWords API we used geo-performance-report with the next predicate:

 IsTargetingLocation IN [true, false] AND LocationType = LOCATION_OF_PRESENCE

to get User locations data.

Will it be correct to use location_view instead fro Google Ads API? Just with no filters? 

Thank you!

Oksana

[Oksana Sulyma]

Hi guys, 

I see a lot of other later topics being addressed, but not this one... 

I'll really appreciate any help on my. question. 

[Google Ads API Forum Advisor]

Hi Oksana,

Thank you for reaching out to the Google Ads API support team.

With regards to your concern, you can use geographic_view.location_type='LOCATION_OF_PRESENCE' field form geographic_view report. Let me know if you have any question.

Thanks,

Nirmita Google Ads API Team

ref:_00D1U1174p._5004Q2Yl2xI:ref

[Oksana Sulyma]

Hi Nirmita! I've just 'replied to author' with my questions. Thanks in advance! Oksana

[Oksana Sulyma]

Hello! 

I just wanted to share the response I got via private message in case it might be helpful for other people: 

Hi Oksana,

Thanks for getting back to us.

Kindly note that there isn't a complete 1:1 mapping of AdWords reports to Google Ads reports. Most of the data is still accessible but not always in the same resources, and for the most part those changes were made to fix limitations in some AdWords reports where, for example, metrics may have been confusing or misleading in the way they were presented.

For your specific question - it appears as though the only difference between the geographic_view and the user_location_view is that the former exposes location_type while the latter exposes targeting_location. This is why you received an error on the query migration tool. As per report mapping for  GEO_PERFORMANCE_REPORT, you can find it in the Google Ads API from the geographic_view and user_location_view reports. Both reports have the same segments and metrics fields. If you still observe any discrepancy in the Google Ads API , please provide the complete request and response logs so that I can impersonate it on my end.

Regards,

Yasar
Google Ads API Team

Thanks Yasar, this was helpful and I was able to get data match in  geographic_view + geographic_view.location_type='LOCATION_OF_PRESENCE' filter, while I had to give up targeting_location field.