top_impression_percentage and absolute_top_impression_percentage together with geo_target_most_specific_location

[sebastia...@gmail.com]

Hi,

I'm trying to migrate to the Google Ads API but one thing is holding me back. I currently rely on the TopImpressionPercentage, AbsoluteTopImpressionPercentage fields of the GEO_PERFORMANCE_REPORT.

I saw that version 10 of the Google Ads API finally added metrics.top_impression_percentage and metrics.absolute_top_impression_percentage to the geographic_view. BUT when I tried to use them I realized those fields can't be queried together with segments.geo_target_most_specific_location which is what I need.

The below query gives to following error:

Cannot select the following segments because at least one unsupported metric is found in SELECT or WHERE clause: 'segments.geo_target_most_specific_location'(unsupported metrics: 'absolute_top_impression_percentage', 'top_impression_percentage').

1. Could we get this fixed?

2. Could we also get support for these two metrics in the user_location_view?

Without this I can't fully migrate my application.

Thanks!

SELECT
  segments.date,
  segments.geo_target_most_specific_location,
  metrics.impressions,
  metrics.top_impression_percentage,
  metrics.absolute_top_impression_percentage,
  metrics.clicks,
  metrics.cost_micros
FROM
  geographic_view

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to us.

Based on the latest release of our documentation , absolute_top_impression_percentage is supported, but upon checking in Google Ads Query Builder and Query Validator , it is still not compatible with segments.geo_target_most_specific_location.

For the user_location_view , 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,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2Ylu7y:ref

[sebastia...@gmail.com]

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

[sebastia...@gmail.com]

Update re my comment about the tiny difference between the geographic_view and user_location_view report.

I tried specifically querying the geographic_view for only physical location rows with the where clause geographic_view.location_type = LOCATION_OF_PRESENCE. This simply excluded the 26 rows.

It's not preferable to seemingly loose an arbitrary number of rows. BUT short-term I'm ok with using the geographic_view report if it's easier to simply only turn on so we can query it for geo_target_most_specific_location together with the metrics in question, than adding the metrics to the user_location_view report. According to my quick tests the number of rows we would loose seem to be negligible.

But ideally we would of course want to use the user_location_view and not have to worry about dropping any rows.

[Ngon Nguyen]

Chào mừng bạn đến với bảng nhớ tạm của Gboard, bất kỳ văn bản nào bạn sao chép sẽ được lưu tại đây.Sử dụng biểu tượng chỉnh sửa để ghim, thêm hoặc xóa đoạn.Nhấn vào một đoạn để dán vào hộp văn bản.Chạm và giữ một đoạn để ghim đoạn đó. Các đoạn đã bỏ ghim sẽ bị xóa sau 1 giờ.

Vào 21:48, Th 4, 16 thg 3, 2022 sebastia...@gmail.com <sebastia...@gmail.com> đã viết:

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/9714890f-a9fc-44cf-8af7-304757ac9452n%40googlegroups.com.

[Google Ads API Forum Advisor]

Hi Sebastian,

Thank you for these details and we're glad to hear about the temporary reporting setup you have implemented.

Moving forward, I have now created the feature request, subject for review, regarding the reports and fields we discussed. For now, you may keep an eye on our blog for updates or announcements.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2Ylu7y:ref

[sebastia...@gmail.com]

Hi Peter,

Thanks for filing the feature request!

Just to clarify, we have no temporary reporting setup. What we need to migrate to the Google Ads API is either:

A. For you to simply enable us to query the geographic_view report for the geo_target_most_specific_location together with top_impression_percentage and absolute_top_impression_percentage
B. OR ideally add support for the above to the user_location_view report.

/Sebastian

[Ngon Nguyen]

Vào 16:29, Th 6, 18 thg 3, 2022 sebastia...@gmail.com <sebastia...@gmail.com> đã viết:

--

--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api...@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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/0ae16525-271c-4078-bbef-5630e7e1acdfn%40googlegroups.com.

[Google Ads API Forum Advisor]

Hi Sebastian,

Peter has created an internal feature request for both of these scenarios. New features will be announced in the release notes for subsequent Ads API versions.

Regards,
Matt
Google Ads API Team

Matt Google Ads API Team

ref:_00D1U1174p._5004Q2Ylu7y:ref

[sebastia...@gmail.com]

Thank you Peter and Matt ٩( ᐛ )و

[Google Ads API Forum Advisor]

Hi Sebastian,

If you have additional questions regarding the topic being discussed in this thread, feel free to send those over to our team and we would be happy to assist you further.

Regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2Ylu7y:ref

[Aleksandr Krymskiy]

Hello,

 We have the same issue where we have an application that relies on the same combination of fields (top_impression_percentage and absolute_top_impression_percentage together with geo_target_most_specific_location) and the retrieved data is used in a ML algorithm whose output in turn drives automatic bid adjustments to our campaigns (also via API). With the AdWords API sunset - our application and business logic are essentially being disrupted with no solution.

There are multiple other threads on the forum referencing inability to use this combination of fields with no currently available solution from new Google Ads API. Since there is no solution with new API, can Google delay the sunset of the existing AdWords API? This is critical for us as it can essentially ruin our lead acquisition business.

Thank you,

Aleksandr Krymskiy

[Google Ads API Forum Advisor]

Hi Aleksandr,

Thanks for sharing this issue. Please allow me to raise it to our team and we will provide an update shortly.

Thanks,
Matt
Google Ads API Team

Matt Google Ads API Team

ref:_00D1U1174p._5004Q2Ylu7y:ref

[Google Ads API Forum Advisor]

Hi Aleksandr,

I appreciate your patience to this concern.

Allow me to raise a feature request to my team so that the top_impression_percentage and absolute_top_impression_percentage together will be compatible with the geo_target_most_specific_location. For now, please follow our blog as we will post relevant updates there when become supported.

As for your concern about deprecation of the AdWords API, sunset date cannot be extended and will gradually start on April 27. However, if you want to extend the date of using AdWords API, then I would suggest reaching out to your Google representative to help you here.

Regards,

Ernie John Google Ads API Team

ref:_00D1U1174p._5004Q2Ylu7y:ref