AuthenicationError.NOT_ADS_USER - but only for single report type.

[Alex Jones]

We are experiencing issues with requesting a Geography Report from the API. Strangely, we use the same code to process all of our other reports, which completed successfully both before and after the failing Geography Report. We've waited several hours and then requested the report again, to no avail. I'm hoping you have some insight into this issue. This is the same production code we've been executing for some time now with no issues, and configurations have not been altered recently either. We rely on this data, and not having it available is very inconvenient for us. We'd appreciate any help you can provide. 

[Brad Ruderman]

I am having the same issue with the "CLICK_PERFORMANCE_REPORT", however the "AD_PERFORMANCE_REPORT" is working just fine. I even upgraded to 201502. Here is a repo in Python:

https://gist.github.com/BradRuderman/81fc37a16a9f8a9d45d1

The strange thing I note, is when I remove all the columns but GclId from the click perf report, it seems to work. 

Thanks,

Brad

[Brad Ruderman]

It appears if i remove the following fields from the report, it starts working agin:

CityCriteriaId
CountryCriteriaId
MetroCriteriaId
RegionCriteriaId

Looks like its a bug in the adwords API that is affecting both the 201502 and the 201409 versions.

Thanks!

[Bejan @ MarketFlare]

Same issue here with the Geo performance report using AdWords API v201409. It worked fine when we ran it last week, and now the geo performance report returns the error:

Error: AuthenticationError.NOT_ADS_USER, Trigger: <null>, FieldPath:

Account performance and other reports work fine.

On Saturday, March 7, 2015 at 9:24:03 AM UTC-8, Alex Jones wrote:

[peter.r...@smarter-ecommerce.com]

We experience the same problems since a few days. It is unpredictable if the error occurs or not. The same request sometimes fails (with the NOT_ADS_USER error) and sometimes succeeds. Test requests were issued right after each other (first succeeded, second failed, third succeeded, ...)

[Daniel Altman]

Same issue here, please fix it asap!

[Roman Kredentser]

oh thanks you very much , you just made my day!

воскресенье, 8 марта 2015 г., 10:01:22 UTC+2 пользователь Brad Ruderman написал:

[Mark McKelvey]

We've got the same problem.  Seems like a bug.  Or at least an incorrect error message is being returned.

[Johnny O]

On Saturday, March 7, 2015 at 11:24:03 AM UTC-6, Alex Jones wrote:

We are experiencing issues with requesting a Geography Report from the API. Strangely, we use the same code to process all of our other reports, which completed successfully both before and after the failing Geography Report. We've waited several hours and then requested the report again, to no avail. I'm hoping you have some insight into this issue. This is the same production code we've been executing for some time now with no issues, and configurations have not been altered recently either. We rely on this data, and not having it available is very inconvenient for us. We'd appreciate any help you can provide. 

A report we are downloading: GEO_PERFORMANCE_REPORT is throwing the same exception you are getting too. 

[Michiel]

Exactly the same thing happened to us. It looks like it happened after the new version release. It's a serious bug and causing issues for our clients...

[Chris]

Same here.  No code changes.  We have a service that runs nightly.  Worked fine on 3/6, started failing 3/7 and continues to fail.

[Caleb Hyde]

I'm in the same boat -- we have production code that pulls several Adwords reports. The other reports still work, but this is failing, though from reading the release notes (https://developers.google.com/adwords/api/docs/reference/) for v201502, nothing in the configured report seems incorrect -- we're using 'CountryCriteriaId' and 'RegionCriteriaId', which should be fin.

For reference, we use the Python 'googleads' library (https://github.com/googleads/googleads-python-lib), on version 3.1.1

[di...@singular.net]

Hi,

We also started experiencing this issue a few days ago for all of our clients, please fix this.

Meanwhile, is there an alternative geo report that can be pulled that can be used to breakdown campaign performance per country?

[Chris]

Been doing some testing here.  I found that I had to specify at least CountryCriteriaId to get it to work, but if I specify any of the other fields it fails.  

Hopefully there will be a fix for this ASAP as it is vital part of our internal process.

*** Works for this set of fields

AdGroupId

AdGroupName

CampaignId

CampaignName

Clicks

Cost

CountryCriteriaId

Date

*** Fails if I add RegionCriteriaId to the above

*** Fails if I add MostSpecificCriteriaId to the above

*** Fails if I add CityCriteriaId to the above

*** Fails if I add MetroCriteriaId to the above

[Anash P. Oommen (AdWords API Team)]

Folks,

Thanks for reporting this issue, we are looking into it. Can someone use the "Reply to Author" to send me a failing request and response HTTP logs? I cannot replicate this on my test account, so I suspect that not all accounts are affected (yet).

Cheers,
Anash P. Oommen,
AdWords API Advisor.

[Anash P. Oommen (AdWords API Team)]

Hi everyone,

We have pushed a fix for this issue, so the errors should go away now. Please update this thread if you continue seeing errors.

Cheers,

Anash

[Brad Ruderman]

I have confirmed it is working for me.

Thanks!