Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-23 Thread SeriousJ
It's still not the answer. All the reasons that you give for not working don't apply to us. We use extensions, not feeds. Extensions are linked to the campaign. And I'm tired of debugging your answers. I'll give you the answer. First you need a query for getting all extensions and their details

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-23 Thread Google Ads API Forum Advisor Prod
Hello, The reason I sent you this query is because I ran this exact query against a few of your company's accounts, and I got back results. I was hoping to work with you privately in order to find out which account was not getting results. You can provide me the account number publicly because

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-23 Thread SeriousJ
I don't want to reply privately as many other programmers are trying to make this work and can find this useful. It's also good to keep a public record of how bad things have become. Your query 'SELECT extension_feed_item.resource_name, extension_feed_item.extension_type, campaign.resource_name

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-22 Thread Google Ads API Forum Advisor Prod
Hello All, I've found the source of the inconsistency, so we can work on finding a resolution. Just so everyone has a summary of the current state, here is it: You can have segments.month, segments.quarter in the SELECT clause with segments.date in the WHERE clause. The result is that you'll ge

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-22 Thread SeriousJ
Don't listen to Google Ads API Team members. They don't have a clue either. So for all of you struggling with this idiotic API, here is a solution: SELECT metrics.cost_micros, campaign.name, *segments.week* FROM campaign WHERE *segments.week* >= '2018-07-01' AND *segments.week* <= '2018-08-07

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-22 Thread SeriousJ
There are many inconsistencies in the language. Really a lot. You want to have fun? Tell me what's the query to get the value of all extension_feed_items belonging to a campaign. This new API is even more obscure than the previous one. No small feat. And of course, it's much much slower. About

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-22 Thread Google Ads API Forum Advisor Prod
Greetings! First of all, thank you so much for helping out here by posting a solution that works. Second, thanks for clearly outlining what appears to be a possible bug in our query language. We shouldn't have date-like segments behaving differently. So, I filed an issue over here to get that r

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-22 Thread SeriousJ
Well, no. This query gets me good results: 1) SELECT metrics.cost_micros, campaign.name, *segments.month* FROM campaign WHERE *segments.date* >= '2018-07-01' AND *segments.date* <= '2018-08-07' whereas this query doesn't get any result: 2) SELECT metrics.cost_micros, campaign.name FROM campa

RE: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-21 Thread Google Ads API Forum Advisor Prod
Hello, While applying where condition for date segment in a query, you have to make sure all the date segments are in the WHERE condition only. Regards, Sai Teja, Google Ads API Team ref:_00D1U1174p._5001UAqFgy:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blo

Re: EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-21 Thread SeriousJ
etrics.gmail_secondary_clicks, metrics.value_per_conversion, > metrics.active_view_cpm, metrics.active_view_ctr, > metrics.active_view_measurable_cost_micros, metrics.cost_micros, > segments.date FROM ad_group_audience_view WHERE segments.date BETWEEN > "2019-05-09" AND "2019-0

EXPECTED_FILTERS_ON_DATE_RANGE

2019-05-10 Thread Alexander
segments.date BETWEEN "2019-05-09" AND "2019-05-09" LIMIT 100 Failure message: errors { error_code { query_error: EXPECTED_FILTERS_ON_DATE_RANGE } message: "Expects filters on the following field to limit a finite date range: \'segments.week\'" }