News for hackers. Stuff that matters.

A comment on Building a more private web: A path towards making third party cookies obsolete. Parent comment

Re:Building a more private web: A path towards making third ... by mattlondon on Wednesday January 15, 2020 @01:37AM (#22052172)
Minor point but the e-commerce site will not be able to read the cookie from Facebook - it will have a special code snippet on the "thank for your purchase" page. When your browser loads this page it also loads the snippet from Facebook (could be a 1x1 pixel or iframe etc etc) and your browser dutifully passes on the cookie as usual to facebook.com when it loads that snippet (i.e. facebook.com is the third party host) then Facebook's servers log the http request with the cookie ID so they mark that as a successful "conversion" (aka sale).

The browser will not make cookies from other sites available to the e-commerce site. There is no chance for the e-commerce site to take a look at what is in the Facebook cookie

[ Parent | on HN ]
Re:Building a more private web: A path towards making third ... by hnick on Wednesday January 15, 2020 @02:17AM (#22052289)
Yeah true,and thanks for that. I unintentionally oversimplified.

I meant the 'page' (including the FB pixel JS on it) could read the pixel but the problem is of course the page is composed of resources from multiple domains and parties.

I'm pretty sure these days the default is just a JS ping to an endpoint, but the eponymous pixel exists under noscript tags for legacy support.

[ Parent | on HN ]