When the user moves from site-one.example to cats.example and later from site-two.example to cars.example, there's no way to track those movements as coming from the same person. The image below shows how third-party cookie blocking is supposed to work. Once tracker.example places itself between enough of the sites a visitor browses, the tracker eventually builds a detailed profile of that activity, including the user's interests and demographics. With that, the tracker.example cookie gets passed through a URL parameter and then gets stashed as a first-party cookie on the landing page. When site.example detects that the tracker.example cookie can't be set, it instead redirects the browser to the tracker.example site, sets a cookie from that domain, and then redirects back to the original page or a new destination. When a browser prevents a website such as site.example from loading a third-party tracking cookie from a domain such as tracker.example, site.example pulls a fast one. Overriding privacyīounce tracking is one of the key ways websites circumvent third-party cookie blocking. The new feature, known as unlinkable bouncing, will roll out for general release in Brave version 1.37 slated for March 29. Now, makers of the Brave browser are taking action.Įarlier this week, Brave Nightly-the testing and development version of the browser-rolled out a feature that's designed to prevent what's known as bounce tracking. Instead of respecting visitors' choice to block third-party cookies-the identifiers that track browsing activity as a user moves from site to site-they find sneaky ways to bypass those settings. Some websites just can't take "no" for an answer.
0 kommentar(er)
