tracking pixel
Categories
(Core :: Privacy: Anti-Tracking, enhancement)
Tracking
()
People
(Reporter: Crashdows, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
tracking pixel (also called 1x1 pixel or pixel tag) is a graphic with dimensions of 1x1 pixels that is loaded when a user visits a webpage or opens an email. Because it is so small, it can hardly be seen by visitors of a website or email recipients. These tracking pixels are partly or fully designed to be transparent, or camouflaged in the background color of the website so that they don't stand out to users. Users are usually not supposed to see the tracking pixel. The focus is mainly on the processes that are initiated by downloading the tracking pixel.
Tracking pixels within the source code might look like this:
<img style="“position: absolute;" src="“Tracking">
<img style="“display: none”;" src="“Tracking">
<img src="“Tracking" width="“0”" height="“0”">
The tracking pixel URL is the memory location on the server. When the user visits a website, the image with the tag is loaded from this server. Optical properties such as visibility, or a very small size are defined using the style attribute.
Actual results:
The website operator or sender of an email adds the tracking pixel using a code in the website’s HTML code or email. This code contains an external link to the pixel server. If a user visits the destination website, the HTML code is processed by the client – usually the user’s browser. The browser follows the link and opens the (invisible) graphic. This is registered and noted in the server’s log files.
In addition, various information about the user is also transmitted using this method. To some extent, combination with JavaScript is necessary in order to collect information about the operating system or browser type.
The following data can be acquired and analyzed with a tracking pixel.
Operating system used (gives information on the use of mobile devices)
Type of website or email used, for example on mobile or desktop
Type of client used, for example a browser or mail program.
Client’s screen resolution
Time the email was read or website was visited
Activities on the website during a session (when using multiple tracking pixels)
IP address (gives information on the Internet Service Provider and location).
also please visit this sites for more information:
https://en.ryte.com/wiki/Tracking_Pixel
https://www.indeed.com/career-advice/career-development/what-is-tracking-pixel
Expected results:
add the Smart Anti-Tracking feature(blocking tracking by pixel) and It will allow users to block tracking by using small pixel images like samsung internet browser.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Layout' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
Thanks for reporting the tracking vector. The tracking pixel is a well-known tracking technique and Firefox has Enhanced Tracking Protection to protect our users from tracking pixels if they are from known trackers. Firefox will block cookie/storage access of third-party trackers, so tracking pixels won't be able to use third-party cookies as an identifier to identify users.
For unknown trackers, we have Total Cookie Protection that partitions third-party cookie/storage by the first-party domain. And together with URL Query String Stripping, we can neutralize the threat from tracking pixels. We are experimenting with these two features in Nightly channel. Hopefully, we can get these two features into the release channel, but we don't have a clear plan yet.
(In reply to Tim Huang[:timhuang] from comment #2)
Thanks for reporting the tracking vector. The tracking pixel is a well-known tracking technique and Firefox has Enhanced Tracking Protection to protect our users from tracking pixels if they are from known trackers. Firefox will block cookie/storage access of third-party trackers, so tracking pixels won't be able to use third-party cookies as an identifier to identify users.
For unknown trackers, we have Total Cookie Protection that partitions third-party cookie/storage by the first-party domain. And together with URL Query String Stripping, we can neutralize the threat from tracking pixels. We are experimenting with these two features in Nightly channel. Hopefully, we can get these two features into the release channel, but we don't have a clear plan yet.
Thank you for your care, but adding another level of protection is always better.
I mean that Total cookie protection and enhanced tracking protection are good but if you add another pixel protection make it flawless.
Description
•