Quantcast StorefrontBacktalk » Blog Archive » Google Analytics Blowup Likely By End Of Summer?
advertisement
advertisement

Google Analytics Blowup Likely By End Of Summer?

Written by Evan Schuman
April 8th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

A web analytics train wreck is expected later this year, when an old version of Google Analytics—still being used by a huge number of retail sites—gets phased out, according to a report issued Wednesday (April 8) from Pingdom. The report was a survey that looked at the top 10,000 Web sites and it discovered two interesting figures: 50 percent of all of those sites use Google Analytics, which in and of itself is fairly mind-blowing; and a full 40 percent of those sites are using an expired version of Google Analytics.

“Google switched its development over to ga.js well over a year ago. It’s truly remarkable that almost half of the sites using Google Analytics have yet to migrate to the new ga.js script,” the report said. “The question is, for how long will urchin.js keep working? Back when Google made the switch it was widely believed that Google would stop supporting the old script after 12-18 months. If that is the case, the end for urchin.js is getting near.” The report speculated that “urchin.js will be decommissioned sometime this summer” and, when that switchover happens, all of the sites using the older version will “start returning a 404 error (file not found) and therefore stop registering traffic.” (Update: Google is now officially denying that they plan an end-of-summer cutoff. Is Google telling the truth? Most likely. The denial is too explicit.)


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...