You are hereBlogs / Jay Small's blog / Google Analytics crushed by demand
Google Analytics crushed by demand
Like everyone else I know on this planet, and perhaps a few aliens, too, I'm testing the new Google Analytics. So far, whole days are missing from my reports, and the lag to show new data runs much longer than the promised 12 hours.
Google appears alert to the problem. From an announcement on my Settings page:
The demand for Google Analytics surpassed even our highest expectations and as a result some customers may temporarily experience report-update delays. All data continues to be collected and no data has been lost. We are currently adding resources to ensure high-quality service. We apologize for any inconvenience.
Meanwhile, SiteMeter, which gives me most of the same stats albeit in a less-attractive package, chugs right along, reporting in near-real time.
Update: As of Monday morning, Nov. 21, Google Analytics has backfilled the missing days on my reports, and performance overall seems better. I can't argue with the robust report suite, though I can still quibble with things like Safari compatibility issues (dealt with in the comments on this post).
Both blogs
...and Google analytics won't work with Safari, my primary browser, and the browser used by about 10 per cent of the visitors to my site, according to the Sitemeter. I signed up for Analytics on Wednesday nights and so far I've only received one report (for Thursday).
What can you say about a company that introduces a service that forces the user to switch browsers and that can't deliver what it said it will. Given what's happened in the past with the quick uptake of new Google services, I can't believe their "highest expectations" were set so low.
Actually, GA works with Safari, it just isn't supported...
Load up GA in Safari, look at one of your reports, then his CMD+ as if you're increasing the font size. Hit CMD- to make the font size normal again...
Your reports will work in Safari.
I'm more of a Firefox guy anyway, but that's a wild way to get it to work in Safari. I can't argue with success, but I wonder how/why a font size command makes a difference.
Vert weird, but it works. Thanks, John.