Fixed
Status Update
No update yet.
Comments
ia...@gmail.com
i have same iusse
ke...@google.com
Hi all,
Please check your inboxes after a few minutes. I'll send a separate email to each one so we can discuss your concern privately.
Regards,
Kevin Soriano, Analytics API Team
Please check your inboxes after a few minutes. I'll send a separate email to each one so we can discuss your concern privately.
Regards,
Kevin Soriano, Analytics API Team
jo...@audioboom.com
@kevin can I also be contacted please ? Our requests either time out after a minute of waiting, or return rateLimitExceeded errors.
bv...@gmail.com
Same thing. We have also been getting random timeouts on several calls for a few days.
Solution ?
Solution ?
[Deleted User] <[Deleted User]>
@Kevin, I was also following this thread to see any updates and solutions. Could you please contact me too with the details, or share them in this ticket?
ke...@google.com
Hi all,
I'll check with our team if they have any further insights on this slow response time. I'll update this thread once I have more information or reach out to everyone if we need more information.
Regards,
Kevin Soriano, Analytics API Team
I'll check with our team if they have any further insights on this slow response time. I'll update this thread once I have more information or reach out to everyone if we need more information.
Regards,
Kevin Soriano, Analytics API Team
[Deleted User] <[Deleted User]>
Hi guys,
Same issue here. In the past few days we have seen average latency drops from 500ms to a full minute (still talking average).
Could you please get in touch with us as well? This is a showstopper for our entire company.
david.gyori@innonic.com and adammolnar.dev@innonic.com
Appreciate your help, Kevin!
Same issue here. In the past few days we have seen average latency drops from 500ms to a full minute (still talking average).
Could you please get in touch with us as well? This is a showstopper for our entire company.
david.gyori@innonic.com and adammolnar.dev@innonic.com
Appreciate your help, Kevin!
m....@gmail.com
We have the same issue with this too, where the whole request would timeout after 60 seconds. Can we be contacted with a solution as well? Cheers!
ru...@frieslandcampina.com
Huge performance issues since 21st Dec. E.g. P99 latency has risen from 4sec to 9 min! Often API calls result in time-outs.
ia...@gmail.com
but why doesn't google give us an explanation about it? the problem is causing disservice!
[Deleted User] <[Deleted User]>
Hi guys,
Issue is still here. And the situation looks critical, we have lots of complaints from our clients. And there is not any progress.
Could you help us somehow?
Issue is still here. And the situation looks critical, we have lots of complaints from our clients. And there is not any progress.
Could you help us somehow?
ar...@whatagraph.com
Hello everyone, Kevin,
We started facing the same issue around the same time - December 21st, December 22nd. Some responses from reporting API v3 are quick, up to a second or two, and some requests take 4 or even 8 minutes to respond! We have carefully checked all of the quotas, we also have implemented a quotaUser param, and exponential back-off, but it's not even trying to back off the requests or anything, it seems Google itself is throttling the request. The context for the request are very simple indeed (i've hidden the externad_id and quotaUser parameters):
dimensions ga:pageTitle
external_id xxxxxxxxx
fetch data
from 2020-11-29
metrics ga:sessions,ga:pageviews,ga:users
quotaUser xxxxxxxxx
sort -ga:sessions
till 2020-12-28
The response for this request took 8 minutes! And it does so randomly, sometimes it responds in a second, then 4 minutes, then 8, then a second again, then 8 minutes again - for the same request.
And it actually shows in the API console, that some requests take a second or two, and some randomly take 8 minutes to respond, and we can actually see from the average latency that it is rising to extremely high levels.
This affects all of our users, so Kevin could you please take a look at our case and contact me with an explanation or a solution?
Thank you!
We started facing the same issue around the same time - December 21st, December 22nd. Some responses from reporting API v3 are quick, up to a second or two, and some requests take 4 or even 8 minutes to respond! We have carefully checked all of the quotas, we also have implemented a quotaUser param, and exponential back-off, but it's not even trying to back off the requests or anything, it seems Google itself is throttling the request. The context for the request are very simple indeed (i've hidden the externad_id and quotaUser parameters):
dimensions ga:pageTitle
external_id xxxxxxxxx
fetch data
from 2020-11-29
metrics ga:sessions,ga:pageviews,ga:users
quotaUser xxxxxxxxx
sort -ga:sessions
till 2020-12-28
The response for this request took 8 minutes! And it does so randomly, sometimes it responds in a second, then 4 minutes, then 8, then a second again, then 8 minutes again - for the same request.
And it actually shows in the API console, that some requests take a second or two, and some randomly take 8 minutes to respond, and we can actually see from the average latency that it is rising to extremely high levels.
This affects all of our users, so Kevin could you please take a look at our case and contact me with an explanation or a solution?
Thank you!
ke...@google.com
Hi All,
I can confirm that there is indeed a system wide issue since December 21st. Rest assured that our team is aware of the issue and is still actively working on a fix for this. I'll update this thread as soon as we have more information.
Regards,
Kevin Soriano, Analytics API Team
I can confirm that there is indeed a system wide issue since December 21st. Rest assured that our team is aware of the issue and is still actively working on a fix for this. I'll update this thread as soon as we have more information.
Regards,
Kevin Soriano, Analytics API Team
ar...@whatagraph.com
Kevin, thank you for your response and confirmation.
One question though, do you have a possible ETA on this? We're thinking of whether we should figure out some additional caching or some other workaround until you fix this issue. Are we talking hours, days, weeks as an ETA?
Our users can't really use our application at the moment.
One question though, do you have a possible ETA on this? We're thinking of whether we should figure out some additional caching or some other workaround until you fix this issue. Are we talking hours, days, weeks as an ETA?
Our users can't really use our application at the moment.
ar...@whatagraph.com
Kevin, we actually have multiple subdomains sending requests to Google Analytics API, but it seems only one of them is not having any issues - it seems you have it allowlisted somehow, could it be a way to workaround this issue to route all traffic through that single subdomain? Could you send me an email so we could discuss privately the possible workarounds for this? I'm only considering my options since the ETA is not clear.
ke...@google.com
Hi,
I'm unable to provide an ETA at the moment. I'll try to check if I can get one.
Regards,
Kevin Soriano, Analytics API Team
I'm unable to provide an ETA at the moment. I'll try to check if I can get one.
Regards,
Kevin Soriano, Analytics API Team
ke...@google.com
Hi Arturas,
I'm afraid that there's no allowlist available to work around this issue. Also, it's still unclear on when this would be fixed, but this is definitely a priority for our team.
Regards,
Kevin Soriano, Analytics API Team
I'm afraid that there's no allowlist available to work around this issue. Also, it's still unclear on when this would be fixed, but this is definitely a priority for our team.
Regards,
Kevin Soriano, Analytics API Team
bl...@agencyanalytics.com
Any update on this?...this is seriously affecting our customers
jo...@gmail.com
Hi all,
I'm having the same issue for a week now, but managed to make the impact smaller:
My temporary solution when getting rate limit/quota errors (because it takes ~24h to recover from it): I created another Google API project via the developer console with it's own set of API keys, but the same apps/permissions/auth screen. My code now switches between the two projects based on which one is (not) generating errors. Not ideal, but since I'm heavily using the Realtime API, at least the gaps in my data will be significantly less now.
Another thing you could try is switching between servers (IPs) that are sending the API requests to Google Analytics. The errors seem to be bound to the IP (for example, if your request is failing, the exact same query will work just fine when you try it out via the API Explorer page on the official Google developer website...)
- Jordi
I'm having the same issue for a week now, but managed to make the impact smaller:
My temporary solution when getting rate limit/quota errors (because it takes ~24h to recover from it): I created another Google API project via the developer console with it's own set of API keys, but the same apps/permissions/auth screen. My code now switches between the two projects based on which one is (not) generating errors. Not ideal, but since I'm heavily using the Realtime API, at least the gaps in my data will be significantly less now.
Another thing you could try is switching between servers (IPs) that are sending the API requests to Google Analytics. The errors seem to be bound to the IP (for example, if your request is failing, the exact same query will work just fine when you try it out via the API Explorer page on the official Google developer website...)
- Jordi
mv...@rtcsoftware.ru
Hi everybody,
Any progress here? Our service is based on Google Analytics API and it is not working properly for last week. Our clients are outraged. We are loosing them.
It's ridiculous that a team of Google professionals can't solve such serious API problem.
Any progress here? Our service is based on Google Analytics API and it is not working properly for last week. Our clients are outraged. We are loosing them.
It's ridiculous that a team of Google professionals can't solve such serious API problem.
jo...@audioboom.com
I’d also like to echo frustration, our services used the reporting API for a lot of our analytics, and our customers are pretty angry that they’ve been unable to access them for 10 days.
Increasing the client libraries timeout from 1 minute to 20 minutes has improved our number of successful requests a little, but we eventually start getting 403s complaining that the “Number of recent failed reporting API requests is too high,”. I’m not seeing these failed requests, I’m not sure if the error message is incorrect or they’re referring to some internal error. Our service is then blocked for the rest of the day, when the rate limit resets.
Increasing the client libraries timeout from 1 minute to 20 minutes has improved our number of successful requests a little, but we eventually start getting 403s complaining that the “Number of recent failed reporting API requests is too high,”. I’m not seeing these failed requests, I’m not sure if the error message is incorrect or they’re referring to some internal error. Our service is then blocked for the rest of the day, when the rate limit resets.
je...@gmail.com
Any update? Can't understand why a system wide issue like this isn't being reported on a status page somewhere.
tl...@mv-group.fr
Might be related to
Since the 21th of december, we see the 95th percentile for latency going regularly to 9 minutes, see screenshot
tl...@mv-group.fr
Does anyone knows if the v4 api has the same issue ?
jo...@audioboom.com
> https://issuetracker.google.com/issues/176032263#comment27
We're using v4, same problems.
>https://issuetracker.google.com/issues/176032263#comment22
Thanks for the suggestion of using multiple projects to get around the rate-limit errors. I've started using this to try & mitigate the problem.
We're using v4, same problems.
>
Thanks for the suggestion of using multiple projects to get around the rate-limit errors. I've started using this to try & mitigate the problem.
fr...@gmail.com
Hello same issue using V3 API.
I've been using the same script for 3 years.
Sometimes get Limit quota error...sometimes not
report = new gapi.analytics.report.Data({
query: {
'ids': 'ga:XXXXXXXX',
'start-date': '2020-05-22,
'end-date': 'yesterday',
'metrics': 'ga:pageviews',
'dimensions': 'ga:yearMonth',
'filters':'ga:pagePath=~(Rustico)|(Rustic)|(Landhäuser)|(Старинные);ga:pagePath=~(Umbria)|(Umbria)|(Umbrien)|(Умбрия)',
'sort':'ga:yearMonth'
}
});
I've been using the same script for 3 years.
Sometimes get Limit quota error...sometimes not
report = new gapi.analytics.report.Data({
query: {
'ids': 'ga:XXXXXXXX',
'start-date': '2020-05-22,
'end-date': 'yesterday',
'metrics': 'ga:pageviews',
'dimensions': 'ga:yearMonth',
'filters':'ga:pagePath=~(Rustico)|(Rustic)|(Landhäuser)|(Старинные);ga:pagePath=~(Umbria)|(Umbria)|(Umbrien)|(Умбрия)',
'sort':'ga:yearMonth'
}
});
zi...@google.com
Hi all,
This is still currently being worked on by the team as a priority issue. Some changes had already been made in the backend in order to hopefully alleviate this concern, but do kindly report back if you are still experiencing problems with the Analytics API.
In the meantime, you may want to use the
ne...@gmail.com
Hi,
So far, I haven't seen any improvement.
Can you give us an estimated date of resolution of this problem?
So far, I haven't seen any improvement.
Can you give us an estimated date of resolution of this problem?
si...@outlook.com
Echoing other comments. We've not seen any improvement either.
zi...@google.com
Hi all,
Thank you for updating us on the concern. I'm afraid that we are not able to provide any timelines on this, though rest assured that I'm seeing bug fixing activity every day within the related internal bug ticket. We'll keep you posted on this.
jo...@audioboom.com
Our percentage of failed requests (HTTP 403 or 502) does seem to have reduced in the past day or so - from (approximately) 30% failed requests down to only 3%.
The slow request times don't seem to have improved, though. There's a curious distribution to them - we do see a lot of fast responses (from 0-20 seconds), but then there's a grouping of responses around 240 seconds, 480 seconds, 720 and 960. I don't see an obvious correlation with the metrics/dimensions/daterange that is used.
Approximately 80% of our requests do complete in under a minute.
(Sadly we weren't logging GA's response times in such detail until a week or so ago, so can't compare our numbers to before 21st December.)
The slow request times don't seem to have improved, though. There's a curious distribution to them - we do see a lot of fast responses (from 0-20 seconds), but then there's a grouping of responses around 240 seconds, 480 seconds, 720 and 960. I don't see an obvious correlation with the metrics/dimensions/daterange that is used.
Approximately 80% of our requests do complete in under a minute.
(Sadly we weren't logging GA's response times in such detail until a week or so ago, so can't compare our numbers to before 21st December.)
sc...@bgeniustemp.com
Subscribing this thread. We have these issues for a while now. Responses are very slow and timeout at some point.
bl...@agencyanalytics.com
we are now getting a bogus rate limit exceeded for the majority if our api requests
zi...@google.com
Hi all,
Thank you for your patience on this concern. The team is still actively working on fixing the issue; we'll keep you updated for new developments on this.
[Deleted User] <[Deleted User]>
Hi gang,
Unfortunately, we still see slow and stuck requests.
We appreciate your regular updates, would love to see more details on the root cause and troubleshooting process.
Keep up the great work!
David and all the bright minds at Conversific
Unfortunately, we still see slow and stuck requests.
We appreciate your regular updates, would love to see more details on the root cause and troubleshooting process.
Keep up the great work!
David and all the bright minds at Conversific
ko...@exito.de
No real improvements here. Tonight (CET) we had a report which completed in 6,5 hours while this morning another report (with different dimensions and metrics but far more data) completed in 18 minutes (starting at 07:30). It is totally unpredictable and very annoying.
ko...@exito.de
And still all sorts of server errors:
<p><b>502.</b> <ins>That’s an error.</ins>
<p>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. <ins>That’s all we know.</ins>
Server error: (500) Internal Server Error
<p><b>502.</b> <ins>That’s an error.</ins>
<p>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. <ins>That’s all we know.</ins>
Server error: (500) Internal Server Error
st...@gmail.com
I have same problem :-(
st...@gmail.com
We have problems from 21 dec. 2020.
ko...@exito.de
I strongly doubt the accuracy of display in the Google Developers Console (see attached screenshot). In the screenshot it appears that we had the last severe problems on Jan 3rd. That's far from reality. Several scripts have been running extremely slow yesterday and today. We've constantly been having such problems in the last 3-4 weeks and not only on those 7 "peak days" like in the latency chart.
ia...@gmail.com
how long do we have to wait? do you have any idea of the damage done to those who work there?!!!!!!!
[Deleted User] <[Deleted User]>
come on Google! This is getting ridiculous
bo...@gmail.com
Hello,
What is the expected time to have this issue fixed? The delays heavily decrease user experience of our service. It has been working perfectly since 2010, but from around Dec 23 we see a lot of delays and GA API response timeouts till today. Please share shed some light to us when we can expect to have it fixed. Thank you!
What is the expected time to have this issue fixed? The delays heavily decrease user experience of our service. It has been working perfectly since 2010, but from around Dec 23 we see a lot of delays and GA API response timeouts till today. Please share shed some light to us when we can expect to have it fixed. Thank you!
se...@pollackphoto.com
I'm curious why this is marked priority P4. This is breaking many Google Analytics customers.
zi...@google.com
Hi all,
We understand your frustrations. If at all applicable, you may try upgrading to Google Analytics 4 and using the Data API as a workaround for this. We ask for your patience on this as we continuously work towards fixing this issue. We will keep you updated.
mv...@alytics-team.com
Hi
We have hundreds of GA profiles connected to our system (uses GA API3). And we have confirmation that "Quota Error: Rate Limit Exceeded" occurs randomly.
For example, 'profile_id': '189154725' is connected to our system from two users "quotaUser=150509" and "quotaUser=196242". Yesterday there was Quota Error: Rate Limit Exceeded at 2021-01-07 04:23:39.046 MSK. But in our logs i see that qps rate for that quotaUsers is less than 1 qps for previous hours.
It looks like after it appears several times for some profile - we have "Quota Error: Number of recent failed reporting API requests is too high, please implement exponential back off.". So we cannot fetch GA data till next day for such profiles. We have already implemented exponential backoff, we use quotaUser but it not helps and last two weeks we have many profiles that are always blocked with "number of recent failed reporting API is too high".
We think that this is more serious problem than API timeouts that is discussed inhttps://issuetracker.google.com/issues/176625345 . Our application retries hanged requests with exponential backoff but get banned. Maybe quotaUser parameter no longer works.
We have hundreds of GA profiles connected to our system (uses GA API3). And we have confirmation that "Quota Error: Rate Limit Exceeded" occurs randomly.
For example, 'profile_id': '189154725' is connected to our system from two users "quotaUser=150509" and "quotaUser=196242". Yesterday there was Quota Error: Rate Limit Exceeded at 2021-01-07 04:23:39.046 MSK. But in our logs i see that qps rate for that quotaUsers is less than 1 qps for previous hours.
It looks like after it appears several times for some profile - we have "Quota Error: Number of recent failed reporting API requests is too high, please implement exponential back off.". So we cannot fetch GA data till next day for such profiles. We have already implemented exponential backoff, we use quotaUser but it not helps and last two weeks we have many profiles that are always blocked with "number of recent failed reporting API is too high".
We think that this is more serious problem than API timeouts that is discussed in
ia...@gmail.com
is there any news?
ne...@gmail.com
Hi,
We saw a marked improvement yesterday around 6:10 pm (UTC +1), with times returning to normal. This improvement did not last over time and in the hours that followed, the problem of latency returned.
We saw a marked improvement yesterday around 6:10 pm (UTC +1), with times returning to normal. This improvement did not last over time and in the hours that followed, the problem of latency returned.
ko...@exito.de
Finally a glimmer of hope ...
One of the Google people in this thread suggested: "If at all applicable, you may try upgrading to Google Analytics 4 and using the Data API as a workaround for this"
We use R to access the Analytics API. To this end we've made use of the RGA package (https://github.com/artemklevtsov/RGA ) which was last updated in April 2016 and "is designed to work with the Google Analytics API V3 in R." Until three weeks ago this worked perfectly well. But unfortunately the current problems persist up until today with a huge latency still.
So I managed to find another much more recent R package which supports v3 and v4 of the Analytics API:https://code.markedmondson.me/googleAnalyticsR/
Here's a nice beginner's guide for this package:https://www.rubenvezzoli.online/googleanalyticsr-beginners-guide/
So I rewrote one of the bigger scripts to use googleAnalyticsR instead, making v4 requests. Just some numbers: Nine reports, ten analytics views each, monthly data over three years ... it took altogether a bit more than an hour when I ran the new script about an hour ago. In the last two weeks, using v3 with the old script, each report took about 6-8 hours ... if it completed at all.
Hopefully it was not only a streak of luck with the new v4 requests ... ;-)
One of the Google people in this thread suggested: "If at all applicable, you may try upgrading to Google Analytics 4 and using the Data API as a workaround for this"
We use R to access the Analytics API. To this end we've made use of the RGA package (
So I managed to find another much more recent R package which supports v3 and v4 of the Analytics API:
Here's a nice beginner's guide for this package:
So I rewrote one of the bigger scripts to use googleAnalyticsR instead, making v4 requests. Just some numbers: Nine reports, ten analytics views each, monthly data over three years ... it took altogether a bit more than an hour when I ran the new script about an hour ago. In the last two weeks, using v3 with the old script, each report took about 6-8 hours ... if it completed at all.
Hopefully it was not only a streak of luck with the new v4 requests ... ;-)
bo...@gmail.com
And how much did it take for old v3 script to run this task before the bug was present, i.e. before December 20th?
In other words: is v4 faster than v3 before problems?
Chris.
In other words: is v4 faster than v3 before problems?
Chris.
ko...@exito.de
Hi Chris,
I can't give you a comparison for the monthly reports mentioned before because I only started to implement that script about 2-3 weeks ago. I can give you, however, some numbers for a similar script: same nine reports, same ten views, retrieving data for the last 36 days (up until "yesterday") on a daily basis. Before the API problems started, this script took about 60 minutes to complete in the morning (starting at 06:50 CET). I just rewrote this script to work with the new R package and v4. Result: 22 minutes (16:42 to 17:04 CET).
I can't give you a comparison for the monthly reports mentioned before because I only started to implement that script about 2-3 weeks ago. I can give you, however, some numbers for a similar script: same nine reports, same ten views, retrieving data for the last 36 days (up until "yesterday") on a daily basis. Before the API problems started, this script took about 60 minutes to complete in the morning (starting at 06:50 CET). I just rewrote this script to work with the new R package and v4. Result: 22 minutes (16:42 to 17:04 CET).
zi...@google.com
Hi all,
Thank you for your patience on this issue.
Just to provide a small update on this: there have been a great number of changes in the backend in the past few days that may contribute into alleviating this issue. We understand that this issue is not completely resolved yet, and will still keep working on it in the meantime. Again, we ask everyone for their patience on this as we strive to develop a more permanent fix for this.
bo...@gmail.com
Seems that today GA API works much much better. Delays are still visible (up to 240sec), but there are less of them. Let's wait another 24h to see whether it's a constant improvement :)))). Thank you for your hard work on this!
Anyway, it's also good time to think about migration to v4 which probably (as mentioned above - thank you!) is much faster in general! :)
Anyway, it's also good time to think about migration to v4 which probably (as mentioned above - thank you!) is much faster in general! :)
ne...@gmail.com
Hi,
Today, we do not find any improvement on our side. It is still very slow.
Today, we do not find any improvement on our side. It is still very slow.
ko...@exito.de
This morning v3 was also very slow on our side. A small report which usually takes about 2 mins, completed in 2 hours. Other v3 scripts had similar problems.
The scripts which we had already migrated to v4 worked without any problems. We've now migrated all our scripts to v4.
The scripts which we had already migrated to v4 worked without any problems. We've now migrated all our scripts to v4.
[Deleted User] <[Deleted User]>
Hi, we are experiencing the same with high impact to our product.
I created a video to reproduce it in google analytics API explorer tool.
We are experiencing the same using API.
Same request takes less than a second and then randomly takes 4 minutes.
Video:https://youtu.be/ozQt6fMOcCw
I created a video to reproduce it in google analytics API explorer tool.
We are experiencing the same using API.
Same request takes less than a second and then randomly takes 4 minutes.
Video:
al...@gmail.com
In some cases simpler solution is to create batch request for multiple requedts or cacheing fetched results, but it is only workaround and the solution for the while only if your code is not extensive
zi...@google.com
Hi all,
Thank you for providing further reports on this. It helps the team in identifying the relevant issues and fixes surrounding this slowdown.
Rest assured that the team is working on this, and applying various fixes, every day. In the meantime, migrating to the Analytics Reporting v4 API (or the Analytics Data API) might help in alleviating the issue.
er...@gmak.nl
Hi,
Is there any indication on when this issue is getting picked up? We have an analytics integration in our product that uses the v3 API. We perform many API calls per day and most of those now take 240 seconds to complete.
It seems that when a call doesnt succeed within a few seconds it always takes around 240 seconds to complete. I tried retrying requests taking longer than 3 seconds, but then im hitting a "failed request" quota pretty quickly.
Thanks in advance
Is there any indication on when this issue is getting picked up? We have an analytics integration in our product that uses the v3 API. We perform many API calls per day and most of those now take 240 seconds to complete.
It seems that when a call doesnt succeed within a few seconds it always takes around 240 seconds to complete. I tried retrying requests taking longer than 3 seconds, but then im hitting a "failed request" quota pretty quickly.
Thanks in advance
[Deleted User] <[Deleted User]>
I agree on #62, it might be non-trivial to upgrade to v4 if there are breaking changes.
We tried similar strategy of retrying a request after 20sec timeout but with no gain, seems that the issue is even getting worse.
Can we have an ETA on the issue please, so we can consider what are our options between potential 4.0 upgrade and waiting for issue to be resolved?
We tried similar strategy of retrying a request after 20sec timeout but with no gain, seems that the issue is even getting worse.
Can we have an ETA on the issue please, so we can consider what are our options between potential 4.0 upgrade and waiting for issue to be resolved?
zi...@google.com
Hi all,
Thank you for your patience on this issue.
While I'm afraid that we are not able to provide any ETA for this at the moment, rest assured that the team is working on fixing this everyday. We will continue to keep you updated on this.
mi...@gmail.com
THANK YOU!!!! Working all day around from the globe!
zi...@google.com
Hi all,
Thank you for your patience on this issue.
The team has declared this issue fixed, but we are also still monitoring the performance of the API as well. Kindly try doing queries on the API once more, and do not hesitate to reach out to us again if you still encounter any issues with this.
bo...@gmail.com
I also confirm that everything works like a charm again. Big Thanks :)
mk...@google.com
ne...@gmail.com
Hi,
Thank you very much for this good news. It's ok with us too.
Thank you very much for this good news. It's ok with us too.
Description
If you have an issue with the Google Analytics UI or product, use the “Send Feedback” action under the ⋮ menu on
The best place to ask questions about using and developing with Google Analytics APIs, libraries, and SDKs is on Stack Overflow. Make sure to use the “google-analytics” or “google-analytics-api” tags.
This is the place to report bugs or feature requests with the Google Analytics API. If that does not describe your use case, please review the other resources available here:
------------ ✂ ------------
Summary:
Hello,
for a few weeks now, I have noticed problems with slowness when retrieving data via the Google Analytics API.
For example, in May, to retrieve the previous month's data for 455 different sites, we took 35 minutes. Today we have passed to several hours. We are currently using the V3 API
Expected Behavior:
Normal response time
Steps to Reproduce:
Start a process that runs 10 Analytics data retrieval queries at the same time against a array containing about 120 queries including paging.
Example of a query:
{
"dateStart":"2020-04-01",
"dateEnd":"2020-04-30",
"options":{
"dimensions":"ga:hostname,ga:fullReferrer,ga:medium,ga:deviceCategory,ga:adDistributionNetwork",
"include-empty-rows":true,
"max-results":10000,
"start-index":1,
"filters":"ga:hostname!~^*.
},
"metric":"ga:sessions,ga:bounces,ga:bounceRate,ga:avgSessionDuration,ga:pageviews,ga:uniquePageviews,ga:goalCompletionsAll,ga:entrances,ga:avgTimeOnPage"
}