Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by fs111 on Tuesday February 18, 2020 @02:30PM
(#22359446)
why is this link doing a redirect through some ad network?
[ Parent
| on HN ]
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by dang on Tuesday February 18, 2020 @03:14PM
(#22359868)
We've since changed the link, which originally was https://techcrunch.com/2020/02/18/how-spotify-ran-the-larges....
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by C14L on Tuesday February 18, 2020 @03:19PM
(#22359922)
Becasue more and more browsers are limiting access to cookies not only depending on first-party context but also third-party context. So tracking users by web bugs becomes less reliable. By redirecting throught the domain, they can set and access cockies in a first-party context.
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by Swtrz on Tuesday February 18, 2020 @02:36PM
(#22359506)
I wonder why I never see this behavior despite every other person mentioning it
Re:How Spotify ran a large Google Dataflow job for Wrapped 2019
by jdormit on Tuesday February 18, 2020 @02:53PM
(#22359660)
It's really quick. Open the network tab and check the "persist logs" checkbox to ensure that the request logs don't disappear after every redirect, then clear your cookies for advertising.com and guce.techcrunch.com and reload the page. You'll see the request for techcrunch.com redirect to guce.techcrunch.com, which redirects to guce.advertising.com, which redirects back to techcrunch.com. It happens so fast it's not noticeable on page load.