It's working now. No problem with v201502.Geo_Performance_Report
On Saturday, 25 April 2015 01:52:34 UTC+8, AdWordsApiUser wrote:
Started getting this error if city, or region is selected (if you select
only country, it works OK) in the GEO_PERFORMANCE_REPORT. API v201409.
--
--
How long does solve take to solve this issue?
May be it's better to remove city/regions fields?
On Monday, April 27, 2015 at 9:35:21 AM UTC+4,
peter.r...@smarter-ecommerce.com wrote:
We've got the same problem! And it happens for other reports too (e.g.
SHOPPING_PERFORMANCE_REPORT). Looks
Getting the same error.
On Monday, April 27, 2015 at 6:26:38 AM UTC+8, Bejan @ MarketFlare wrote:
Also getting this error, only in the Geo Performance Report and Click
Performance requests... v201502
Our reporting software
http://www.marketflare.com/adwords-reporting-tool/ uses oauth2
+1
On Friday, April 24, 2015 at 2:52:34 PM UTC-3, AdWordsApiUser wrote:
Started getting this error if city, or region is selected (if you select
only country, it works OK) in the GEO_PERFORMANCE_REPORT. API v201409.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on
+1
On Monday, April 27, 2015 at 11:54:47 AM UTC-3, Daniel Altman wrote:
+1
On Friday, April 24, 2015 at 2:52:34 PM UTC-3, AdWordsApiUser wrote:
Started getting this error if city, or region is selected (if you select
only country, it works OK) in the GEO_PERFORMANCE_REPORT. API v201409.
Same problem as Daniel. Please feedback, we really use the
click_performance_report.
El lunes, 27 de abril de 2015, 11:54:47 (UTC-3), Daniel Altman escribió:
+1
On Friday, April 24, 2015 at 2:52:34 PM UTC-3, AdWordsApiUser wrote:
Started getting this error if city, or region is selected
Hi folks,
This is a known issue at our end. We have submitted a fix, and it should be
live today. The issue affects GEO_PERFORMANCE_REPORT, or any other report
that requests a GEO column.
Cheers,
Anash P. Oommen,
AdWords API Advisor.
On Monday, April 27, 2015 at 10:59:56 AM UTC-4, Mauro Cohen
Was able to retrieve an instance of GEO_PERFORMANCE_REPORT without issue
just now.
On Monday, April 27, 2015 at 10:55:34 AM UTC-5, Anash P. Oommen (AdWords
API Team) wrote:
Hi folks,
This is a known issue at our end. We have submitted a fix, and it should
be live today. The issue affects
We are having the same issue. GEO_PERFORMANCE_REPORT {Error:
AuthenticationError.AUTHENTICATION_FAILED, Trigger: null, FieldPath: }
On Friday, April 24, 2015 at 12:52:34 PM UTC-5, AdWordsApiUser wrote:
Started getting this error if city, or region is selected (if you select
only country, it
Was having the same issue starting today with v201409,
Geo_Performance_Report.
On Saturday, 25 April 2015 01:52:34 UTC+8, AdWordsApiUser wrote:
Started getting this error if city, or region is selected (if you select
only country, it works OK) in the GEO_PERFORMANCE_REPORT. API v201409.
Confirmed with our toolset as well. Simultaneously downloaded reports using
the same credentials and clients are confirmed good. This suggests that as
others as saying the issue is related specifically to Geography reporting.
This same issue happened back on March 7th, and was resolved by March
Confirming that this is also the error returned for our tools as well.
?xml version=1.0 encoding=UTF-8 standalone=yes?
reportDownloadErrorApiErrortype
AuthenticationError.AUTHENTICATION_FAILED/typetriggerlt;nullgt;
/triggerfieldPath/fieldPath/ApiError/reportDownloadError
Other endpoints with the
This seems to affect v201502 also. It seems similar to the issue that
started showing NOT_ADS_USER for this report last month.
On Friday, April 24, 2015 at 2:52:34 PM UTC-3, AdWordsApiUser wrote:
Started getting this error if city, or region is selected (if you select
only country, it works
Started getting this error if city, or region is selected (if you select
only country, it works OK) in the GEO_PERFORMANCE_REPORT. API v201409.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
I'm getting this exact error with geo reports as well:
AuthenticationError.AUTHENTICATION_FAILED. Other reports work fine with the
same auth parameters, so I don't think it is actually an auth issue.
Interestingly, if I set one of the awql query constraints to something that
doesn't exist
15 matches
Mail list logo
