Forgot to mention: we are using v13 of the Ads API
kol...@exito.de schrieb am Mittwoch, 17. Mai 2023 um 16:08:29 UTC+2:
> Hi all,
>
> in one Ads account we've got four discovery campaigns, three older one
> which are currently paused and a new one which started at the en
Hi all,
in one Ads account we've got four discovery campaigns, three older one
which are currently paused and a new one which started at the end of April
and already generated a lot of impressions, clicks and costs. The latter
one just doesn't keep showing up in a 'campaign' report (no filters
Hi all,
we've got the following problem: some campaigns have labels attached which
were created on the account level, on the MCC level (groups of accounts of
the same client) and on our top MCC level (our agency). In the Ads UI all
those labels can be seen to the corresponding campaign. However
Seems to work again without problems, we didn't have a single 500 error
this morning. Thanks!
sc...@lionhurst.com schrieb am Donnerstag, 25. März 2021 um 19:53:49 UTC+1:
> Based on the queries I'm doing, this appears to be resolved. Thanks.
>
> Scott
>
> On Thursday, March 25, 2021 at 1:42:01 PM
Do you have any timeline when the bug will finally be fixed? We still get
many many 500 errors during the day.
TBH: This is quite annoying because the problem has been dragging on for
more than two weeks. As it's still not possible to retrieve older change
event data ("The requested start date
We get also tons of 500 errors since we switched to API v6.1 We didn't
have any such problems with v6
It does not seem be restricted tochange_event.changed_fields
I just left this field out of a request and still get 500 errors.
Here's some error info:
RequestId: qjX8ZXQsgwLcDN9CFXc
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:5
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:5
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
> private
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 sec
We are using the Python client library because we don't want to write all
the basic stuff.
In the meantime I found out how you can directly convert the API result to
a pandas dataframe in Python:
from pandas import json_normalize
from google.protobuf.json_format import MessageToJson
...
result
11 matches
Mail list logo
