Hi Oliver,
Thank you for reaching out. I have reported it as a bug internally to get it
fixed for your concerns. We will keep you updated if there is any progress on
the bug fix. Please also keep an eye on our blog for the announcements and
updates on the new releases. We recommend to continue
Hi Xiaoming,
This is quite a serious deviation from how the Adwords API behaves.
Including a field in the SELECT clause causes segmentation which might not
be wanted. It's perfectly valid to want to filter the data (WHERE) but not
segment it (SELECT). If data is segmented, we can not easily
Hi Xiaoming,
Thank you for your reply.
Will the "expected behavior" be changed someday?
Then I strongly request a feature: GROUP BY clause in GAQL, as I've
requested long before. (
https://groups.google.com/forum/?hl=ja#!topic/adwords-api/WlygUGpMBfM )
regards,
Hiromi
2020年4月16日木曜日 4時34分18
Hi Hiromi,
This is expected behavior in the Google Ads API. Whenever you use a segment
criterion in the WHERE clause it is necessary to put the segment criterion in
the SELECT clause. Please let me know if you have any further concerns.
Thanks and regards,
Xiaoming, Google Ads API Team
ref:_00D
Hi Xiaoming,
Thank you for reply.
But we do not want to segment the report by ad_network_type.
AdWords API allows us to get the report segmented by only date with
ad_network_type filtering.
expected report:
date, impression, clicks, impression_share, ...
2020-04-01, 100, 10, 0.1, ...
2020-04-0
Hi Hiromi,
Thank you for reaching out. If you put segments.ad_network_type in the WHERE
clause you would also have to put it in the SELECT clause in order to
successfully query the data. Please let me know if you have any further
questions.
Thanks and regards,
Xiaoming, Google Ads API Team
ref
