Hi, Thanks for the quick reply.
Setting and adjusting location bid adjustments based on users' physical location is the core of our bidding strategy. We currently use the Adwords API equivalent of the user_location_view report and the two metrics in question to do that. For a clean migration we would need to be able to query the user_location_view report for segments.geo_target_most_specific_location together with these two metrics. Given our campaigns' settings it looks like using the geographic_view also could work for us. We never target locations of interest so according to the docs we should get the users' physical location from the geographic_view report. I pulled data for one day from both reports and compared them and out of 250708 rows only 26 rows differed. The only difference was that for these 26 rows the geographic_view for some reason returned the area of interest instead of the physical location. Everything else and all other rows were identical. But this is a smaller issue and not relevant if we can query the user_location_view instead. Happy to provide additional details if you need it! Thanks /Sebastian On Thursday, March 17, 2022 at 10:07:43 AM UTC+1 adsapi wrote: > Hi, > > Thank you for reaching out to us. > > Based on the latest release of our documentation > <https://developers.google.com/google-ads/api/fields/v8/geographic_view?hl=en#fieldssegmentsmetrics> > > , *absolute_top_impression_percentage* is supported, but upon checking in > Google > Ads Query Builder > <https://developers.google.com/google-ads/api/fields/v10/overview_query_builder?hl=en> > > and Query Validator > <https://developers.google.com/google-ads/api/fields/v10/query_validator?hl=en> > > , it is still not compatible with > *segments.geo_target_most_specific_location*. > > For the user_location_view > <https://developers.google.com/google-ads/api/fields/v8/user_location_view?hl=en#fieldssegmentsmetrics> > > , *top_impression_percentage* is not supported yet. > > Could you provide your use case regarding why these certain fields are > indeed needed in your migration to the Google Ads API? For us to better > check it and file a feature request, subject for review. > > Best regards, > [image: Google Logo] > Heidi > Google Ads API Team > > > ref:_00D1U1174p._5004Q2Ylu7y:ref > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/b04e36d7-6dc8-47d2-b0cb-c991bbf8317cn%40googlegroups.com.
