Anatomy of Google analytics cookies(devblog.eduhub.nl)
devblog.eduhub.nl
Anatomy of Google analytics cookies
http://devblog.eduhub.nl/anatomy-of-google-analytics-cookies
3 comments
Since Google is so keen on improving the speed of the internet (and good for them for that) I'm looking forward to the day when they'll only use one cookie for all their tracking (if that's even possible). GA is, by Google's standards, a speed hog right now, and Page speed always complains about it ...
Just wondering: Why doesn't a webserver encrypt the cookie value with a server-side key? This way, the information in the cookie (timestamps, pageviews, number of sessions etc.) can be safe from wireshark sniffers.
That would have to be done on Google's end, that is not something webmasters using Google Analytics are able to do by themselves.
Yep. I'm wondering why Google, in this case, wouldn't encrypt the value stored in its cookie. Is there any technical reason other than laziness?
I believe the cookies are set and manipulated by JavaScript, as such I'm not even sure it would be a good idea...
Nice, I always wondered how they worked.