Hi,
I was able to replicate this scenario on my end as well. I can file a
feature request on your behalf for "allowing device filtering in reports
without including the device field in the selected fields to prevent
segmentation of results". However, i could not provide a comment whether
this will be implemented or not.
Regards,
Dannison
Google Ads API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
On 02/13/19 09:23:14 [email protected] wrote:
I'm dealing with a specific example in mind in the new Google Ads API
whereby if I include a filter on segments.device in the WHERE clause of the
query, I'm also required to add it to the SELECT clause. In the AdWords
API we were able to add predicates in order to filter data without
affecting the aggregation process. Adding a segment to the SELECT clause
causes the resultant data to be broken down by that segment. This is
undesirable, as it breaks the ability to filter prior to aggregation.
As an example, supposing I wanted to see all ad performance metrics
aggregated by ad id, but only including those of devices (A and B).
Forcing the inclusion of the segmentation in the SELECT clause means I'll
be aggregating by both ad id AND device, meaning multiple line items per id
(if more than 1 device applies). Can anyone confirm this behavior and help
rationalize it for me? Perhaps this is something that's going to change in
the near future. I'd at least like to express my concern here though if
I'm correct about the situation. Thanks.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/adwords-api/5cbf6c4d-23eb-42a0-9abc-0d846607ce87%40googlegroups.com
<https://groups.google.com/d/msgid/adwords-api/5cbf6c4d-23eb-42a0-9abc-0d846607ce87%40googlegroups.com?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/d/optout.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 "AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/00d12gms280000018etshq000i9468z74mj0e9m74o30c1g68qj4cpo%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
