ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
np
Yeah, I know that we have a cookie for the login/session stuff to work here currently, but my understanding of how GA worked is that loads some javascript from google-analytics.com, and that will cause GA.com to set its own cookie as well:
-Mike
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania |
|
|
No, they're first-party cookies.
The JS might be loaded from Google, but the JS inserts it into the current page. So the cookies it sets belong to the domain of the current page.
If you were loading *markup* from google-analytics.com, then yes, it could set cookies in that domain. That's, roughly, how ads set their own cookies and they're called third-party cookies. Wade. Just Add Story http://justaddstory.wordpress.com/
|
Something you might have noticed...
- (mvitale)
- (6)
- Feb. 28, 2012, 11:39:34 PM EST
Thanks for the heads up.
- (static)
- (2)
- Feb. 29, 2012, 01:02:11 AM EST
np
- (mvitale)
- (1)
- Feb. 29, 2012, 06:38:35 AM EST
No, they're first-party cookies.
- (static)
- March 1, 2012, 01:11:37 AM EST
Thanks. You should turn on Google's ads, too, IMHO. :-)
-NT
- (Another Scott)
- (2)
- Feb. 29, 2012, 07:30:44 AM EST
They were never really worth the bother, to be honest...
-NT
- (malraux)
- (1)
- Feb. 29, 2012, 01:10:57 PM EST
Ok. And I guess that makes sense, given the low traffic.
-NT
- (Another Scott)
- March 1, 2012, 07:07:38 AM EST
