Forum Discussion
Google Analytics Request failed (403) Error
Hey folks,
This appears to be because the developer of the data source/GA connector reaches their daily query limit, as it's their API credentials being used to connect to GA accounts.
The solution would need to be either:
a) The developers of the source (even if part of Microsoft) need to get their daily query limit increased
b) PowerBI Team allow us to connect up our own API accounts so everyone has their own daily limits, not shared limits
Ali
alisymewrote:
This appears to be because the developer of the data source/GA connector reaches their daily query limit, as it's their API credentials being used to connect to GA accounts.
I really, really, hope this is not the case. That would be a massive oversight; surely they wouldn't expect all Power BI users to flow through the same API account for all GA requests.
I think it's unfortunately the case. I tried to access the project in console that appears in the error message and it wasn't in my existing API console (meaning it's an API credential owned by someone else).
https://developers.google.com/analytics/devguides/config/mgmt/v3/limits-quotas#additional_quota
The devs can request an increase, and I'd guess that when it was created they didn't foresee the popularity (?)
Well, that's unfortunate.
I'm perfectly fine with using my own API credentials if they'd give us the option. Ideally, they'll get the source for the custom connector up on GitHub. Not really sure to ping here to resolve this; in the meantime, I suppose I'll start working on that connector. If I get something working, I'll post it here.
Hi all,
I mean the issue started at the same time as the credential error maybe is related.Power BI:
Customers who attempt to create a new query or edit their credentials for Google Analytics data sources may get an authentication error when entering their Google account information. In addition, some customers may get authentication errors when refreshing datasets that access Google Analytics data. Engineers are working on the fix to mitigate the issue.Next Update:03/15/2018 2:00 PM PST.
Best,
J.
