Hi Caihua,
Thanks for your feedback, I have filed requests with the respective teams to
fix the Query builder tool and the reference documentation.
Cheers
Anash
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
Thank you for looking into this, Anash!
I think the confusion part is that we are able to use those two Enum values
from interactive query builder, so we thought this should be a valid query
(please check the screenshot below).
Also from the public documentation we don't see any specific
Hi team,
Can you please let us know who can help with this? This issue is blocking
us to use Google Ads API and we have reported for more than 2 months.
Your help is highly appreciated, thank you!
Caihua.
On Mon, Jan 18, 2021 at 9:13 PM Caihua Du wrote:
> Hi Anash,
>
> Can you please take a
Hi,
The "stream removed" issue is most likely unrelated to this issue. Could you
kindly open an issue with the client library that you are using if this issue
is consistently replicable?
Cheers
Anash
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Hi,
I am also facing same.
SELECT change_event.resource_name, change_event.change_date_time,
change_event.change_resource_name, change_event.user_email,
change_event.client_type, change_event.change_resource_type,
change_event.old_resource, change_event.new_resource,
Hi Anash,
Can you please take a look and let me know if you have any findings?
To me this is a P0 bug that the status predict does not support NOT_IN
syntax.
On Tue, Jan 12, 2021 at 10:32 PM Caihua Du wrote:
> Hi Anash,
>
> Unfortunately, this is still not working. Here is the latest request
Hi Anash,
Unfortunately, this is still not working. Here is the latest request id
from my client. Please take a look. Thanks a lot!
[2021-01-13 06:30:29Z] - Request made: Host:
https://googleads.googleapis.com, Method:
/google.ads.googleads.v6.services.GoogleAdsService/Search,
ClientCustomerID:
Hi Caihua,
The fix also went live around the time your request ID came in. If you can
replicate the issue, could you send me a newer request ID?
Cheers
Anash
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
Adding the team alias here. Can you please help to check more of the
request I provided earlier? Thank you’
On Wed, Dec 9, 2020 at 10:49 AM Caihua Du wrote:
> Thanks Anash. Unfortunately this issue still persists. I have pasted the
> latest debugging log from my side for your reference:
>
>
This is still happening from our side and I have provided request id
privately about one month ago, there is no update yet. Can you pleas look
into this? thank you!
On Wednesday, December 9, 2020 at 10:55:35 PM UTC-8 Mat wrote:
> Hi Anash,
>
> I've now fetched the change_history of >200 client
Hi Anash,
I've now fetched the change_history of >200 client accounts for the last 30
days and did not run into an error.
So I think it's safe to say that the error I reported on November, 11 has
been fixed.
Thank you!
Regards
Mat
adsapiforumadvisor schrieb am Mittwoch, 9. Dezember 2020 um
Thanks for the update. Unfortunately we still see this error from our side.
I have replied privately with the request id for further investigation.
Thanks!
On Wednesday, December 9, 2020 at 7:58:49 AM UTC-8 adsapiforumadvisor wrote:
> Hi Caihua,
>
> We pushed a fix to our servers, so could
Hi Caihua,
We pushed a fix to our servers, so could you please confirm if the issue is
addressed? If it persists, please respond with a fresh log and I'll follow up
with the relevant teams again.
Cheers
Anash
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
Hi team,
Do we have any update on this? We suspect this is an regression from Google
Ads and would like to double confirm with you.
On Thursday, December 3, 2020 at 10:33:28 PM UTC-8 duca...@gmail.com wrote:
> Hi there,
>
> Do we have any update? Looks like we started to see new failures
Hi there,
Do we have any update? Looks like we started to see new failures from early
this week due to similar errors.
If our query include "NOT IN" as the condition, it will always fail with
"invalid argument " error. For instance the following query will fail for
sure. Do we have any
Hi Anash,
great, thank you!
Regards
Mat
adsapiforumadvisor schrieb am Freitag, 20. November 2020 um 20:54:33 UTC+1:
> Hi Mat,
>
> Thanks for reporting this issue. We identified and fixed an issue at our
> end, and it should go live in the next server update. I'll update you once
> the fix is
Hi Mat,
Thanks for reporting this issue. We identified and fixed an issue at our end,
and it should go live in the next server update. I'll update you once the fix
is live.
Cheers
Anash
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on
Hi Mat,
I just found out that you already provided the necessary details on a separate
thread.
Let me also discuss this information with rest of the team. Please keep an eye
on this forum thread as we will provide updates here about the issue.
Regards,
Ernie John Blanca Tacata
Google Ads API
Hi Mat,
Could you provide the following details via Reply privately to author option to
investigate?
customer ID
complete request and response logs
request ID
If the Reply privately to author option is disabled on your end, please send it
on this email address instead
Hi Thomas,
Thanks for providing further details.
Allow me to discuss the issue to the rest of the team. We will revert back to
you with updates about the issue.
Regards,
Ernie John Blanca Tacata
Google Ads API Team
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
Hi there,
I'm encountering a similar error while requesting a change_event report on
an account where ads have been modified. I'll send a pm with the log to you.
Regards
Mat
adsapiforumadvisor schrieb am Mittwoch, 18. November 2020 um 03:24:06 UTC+1:
> Hi,
>
> Thank you for providing further
Hi,
Thank you for providing further details about your issue.
To investigate the issue and the behavior that you've mentioned, please provide
the requested details on this email address googleadsapi-supp...@google.com so
that we can receive it privately.
Regards,
Ernie John Blanca Tacata
The problem seems to be restricted to the AD level, so if you filter it out
then the API request works without problems (at least for our 200+ active
accounts):
WHERE change_event.change_resource_type NOT IN ('AD')
kol...@exito.de schrieb am Montag, 16. November 2020 um 18:52:17 UTC+1:
The problems seem to be restricted to the AD level, so if you filter it out
then the APIrequest works without problems (at least for our 200+ active
accounts):
WHERE change_event.change_resource_type NOT IN ('AD')
kol...@exito.de schrieb am Montag, 16. November 2020 um 18:52:17 UTC+1:
>
I'm not authorized to reply to the author although I'm logged in. Any
suggestions to fix this?
adsapiforumadvisor schrieb am Dienstag, 17. November 2020 um 09:24:10 UTC+1:
> Hi,
>
> Thanks for posting your concern.
>
> To investigate, could you provide the following details via *Reply
>
Hi,
Thanks for posting your concern.
To investigate, could you provide the following details via Reply privately to
author option?
customer ID
complete request and response logs
request ID
Regards,
Ernie John Blanca Tacata
Google Ads API Team
ref:_00D1U1174p._5004Q27uEVS:ref
--
--
Hey Googlers,
calls to the "change_event" report of the Ads API (v6) always fail when any
of these three fields is included in the API query ...
change_event.old_resource
change_event.new_resource
change_event.changed_fields
... and the changes made in the Ads account include changes to the
27 matches
Mail list logo