Hi Yasar,
Thanks for looking into this! That must have been the issue because I
cannot reproduce it anymore after fixing the dates.
Sorry about that, and thank you for your help!
Best,
Tiana
On Thursday, 9 December 2021 at 10:07:28 UTC+1 adsapi wrote:
> Hi Tiana,
>
> Thanks for getting back
Hi Tiana,
Thanks for getting back to us.
I’ve checked the GAQL used in your initial thread. It appears that the
segments.date >= '2021-11-01' AND segments.date <= '2021-11-30' in the where
clause are mismatching the GAQL used without segments.date. I’ve tried to
generate the same report, and I
Hi Jakeia,
Thanks so much for your help!
I checked the documentation you sent, but seeing the queries I sent
initially it looks like I'm already following the rules as outlined there.
I'm already including `segments.date` in the WHERE clause, for both
requests with and without the segment in t
Hello Tiana,
Thanks for reaching out to the Google Ads API support. There are few
segmentation rules under date segment fields, these rules need to be followed
to get the expected data. If you want to ‘segment.date’ on the SELECT clause,
then the same segments must be specified in the WHERE cla
Hi there,
We're noticing some odd behavior from the API and are wondering if this is
intended.
Basically, the data returned in the SummaryRow is different depending on
whether or not `segments.date` is requested.
Body of request with segments.date:
body: { query: "SELECT
segments.date,metrics