Hacker News Reader

Comment by Animats | Hacker News Reader

Why doesn't this break Google tracking?

1/ Google Analytics uses 1st-party cookies since their scripts execute directly on websites. 2/ Chrome relays its own browsing data.

Can you point me at a link for 2?

Disclaimer: despite working for Google, I don't have a clue about this. I'm deep in the backend.

Ostensibly for SafeBrowsing[1] I believe...

1: https://superuser.com/questions/75841/what-is-1e100-net-and-...

Well to start, there's browser history sync through your Google account. I'm not aware what the privacy policy is on that data, but I'd imagine it allows Google to get aggregate views at least at the domain level, if not the page level.

Also the fact that signing in to any google website automatically signs you in to the browser now.

https://support.google.com/chrome/answer/185277?co=GENIE.Pla... allows you to disable that.

GA usually comes from a Google-domain. Implementing GA on one of your properties always means using 3rd-party cookies (as long as you not configure some CNAME-records to point your own 1st party tracking domain to GA's tracking domain). Where the script is being executed does not matter in this case, the script is just building the tracking request to the tracking app.

They (will) add the samesite decorators.

The intent isn't to break tracking, it's to prevent CSRF.

One of the nice side effects is it will temporarily break tracking, though.

Reply on news.ycombinator.com