Skip to solution.
Whenever I try to open an Engadget article, it will automatically redirect me to
guce.advertising.com/... which is (thankfully) blocked by uBO.
I compared the request header between a normal and private window. There was no cookie sent in a private window. Then, I tried removing the cookie field and resend the request, but I didn’t get any response. I wondered why a cookie is sent even after removing all the cookies and restarted the browser.
The source turned out to be Livemarks addon. It’s a RSS addon, functions similarly to Live Bookmark feature that was removed in Firefox 64. I’m not blaming Livemarks here. Since I subscribe to Engadget’s RSS, immediately after I start the browser, the RSS will be reloaded and a cookie would be set. It seems Engadget would set a cookie, regardless of links.
Block cookie §
Firefox can block cookie by website. To block Engadget from setting a cookie, in Firefox:
- Go to Preferences.
- Navigate to Privacy & Security tab on the left.
- Scroll down to Cookies & Site Data section and open Manage Permissions.
https://www.engadget.comas the address and click Block and save it.
- If you have Clear history when Firefox enabled enabled, make sure Site Preferences is unchecked.
That’s it. If you want to know what is the purpose of
guce.advertising.com, read on.
The previous owner of Engadget, AOL Inc was acquired by Verizon Media (previously known as Oath Inc) in May 2015. With Yahoo! and other media companies as part of its portfolio, Verizon Media can track readers across those websites. One way to do it is through cookie. So,
guce.advertising.com is essentially a cookie consent form (page archived using archive.today).