5 ms·
For those about to bemoan the breaking of things like Google Analytics: this patch only blocks third party cookies from domains that the user has never visited
by robmil 14y ago
For those about to bemoan the breaking of things like Google Analytics: this patch only blocks third party cookies from domains that the user has never visited before. Since 99% of your visitors will have visited google.com, your Analytics should continue to function even after this update.
- dangrossman 14y agoThe GA script loads from google-analytics.com, not google.com. ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- jsomethings 14y agoSafari already blocks most third-party cookies, yet Google Analytics works in Safari. An explanation of how GA pulls it off can be found here: http://webpolicy.org/2012/02/17/safari-trackers/ http://webpolicy.org/2012/02/17/safari-trackers/
- magicalist 14y agothat looks like they're talking about doubleclick, not google analytics. GA works by setting a first party cookie, so there's no need to work around anything. https://developers.google.com/analytics/devguides/collection/gajs/cookie-usage https://developers.google.com/analytics/devguides/collection... edit: oh, jonknee already mentioned that below.
- cpeterso 14y agoGoogle can just change their analytics domain to google.com. Safari already uses this cookie policy.
- burke 14y agoThat's still a piss-poor heuristic to rely on -- especially because it biases your analytics data toward google-users.
- ihsw 14y agoIt isn't isolated to Google users, it gives control of tracking back to websites that users actually go to.
- jonknee 14y agoExcept Google Analytics doesn't use third party cookies so it's a moot point. https://developers.google.com/analytics/devguides/collection/gajs/cookie-usage https://developers.google.com/analytics/devguides/collection...
- StavrosK 14y agoDoes this mean that GA can't track users across websites?
- Hovertruck 14y agoThey could theoretically do both by having the JS on the page set one cookie on the host domain and having the server response set one on the GA domain. I don't believe they do, however. Shameless self mention: Chartbeat does not do this either.
- StavrosK 14y agoWouldn't that count as a third-party cookie? It depends on whether "third party" is defined as "third party from the server response" or "third party from the domain of the loaded page".
- pommefrites 14y agoGoogle provides a way to do it: https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingSite https://developers.google.com/analytics/devguides/collection...