Hello! I would appreciate if someone from Google Support would have a look 
on that asap: 

I noticed a weird behaviour when fetching the Search Query Performance 
Report 
<https://developers.google.com/adwords/api/docs/appendix/reports/search-query-performance-report>
 
in an Google Ads script, here is my AWQL Statement:
*SELECT Query, Clicks, Cost FROM SEARCH_QUERY_PERFORMANCE_REPORT *
*WHERE CampaignName CONTAINS "abc" *
*DURING LAST_14_DAYS *

When I run the said AWQL Statement I expect to get numbers for each Query 
<https://developers.google.com/adwords/api/docs/appendix/reports/search-query-performance-report#query>
 
from the Search Query Performance Report aggregated in one row. Let us 
assume we have the Search Query 
<https://developers.google.com/adwords/api/docs/appendix/reports/search-query-performance-report#query>
 
"term xyz", if I fetch said AWQL statement I expect "term xyz "to be unique 
in the *Query 
<https://developers.google.com/adwords/api/docs/appendix/reports/search-query-performance-report#query>*
 
column because there is no other attribute in the SELECT statement that I 
use for grouping, like CampaignName.

*HOWEVER*, my report contains multiple entries for "term xyz", one for 
campaign to be precise. If I remove the WHERE clause *WHERE CampaignName 
CONTAINS "abc"* from the AWQL Query, each Search Query is unique again in 
the report. 

Does someone have an explanation for this - in my case inconvenient 
behaviour - of AWQL? It is inconvenient because I need the numbers grouped 
only by the Query 
<https://developers.google.com/adwords/api/docs/appendix/reports/search-query-performance-report#query>
.
It does not make any sense to me to get results for each occurrence of the 
Search Query per campaign just because I filter for the campaign name in 
the *WHERE* clause without including the CampaignName in the SELECT 
statement. It does especially not make any sense to me because AWQL does 
not offer statements/operators like SQL's SUM 
<https://www.w3schools.com/sql/sql_count_avg_sum.asp> or GROUP BY 
<https://www.w3schools.com/sql/sql_groupby.asp> that would allow me to 
circumvent this behaviour by grouping the metrics explicitly based on the 
Query field only. 

Best regards

Christian

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/2f1b7943-5dff-4a8b-9130-b9c19e938a59n%40googlegroups.com.
  • Se... Christian Kolb
    • ... 'Google Ads API Forum Advisor' via AdWords API and Google Ads API Forum

Reply via email to