Beacon is an umbrella for tracking techniques, including tracking pixel , which is a controversial mechanism because it attempts to report access to a message or another individual form of the person accessing it.
Some consider an invasion of privacy because it has no way of knowing that this crawl is occurring and does not have much to defend itself without compromising normal functionality (there are some customers who already have facilities but almost have to be technical to configure in a way proper). Of course a person with technical knowledge and willingness has what to do.
It consists of inserting an invisible pixel that has some unique identifier, when the content is accessed it will be loaded indicating on the server that there was access to the content and it is possible to know who was if the identifier is linked to an identity obtained otherwise .
Do you know that feature of requesting confirmation if the person read the email and can be linked? Some clients do not even respond to this. tracking pixel always works, unless the image load is disabled. This can be used for many types of content, not just emails.
The exact form of implementation may vary, may not be invisible, may not be a pixel, may not have a unique identifier, depends on the need and what is available.
One way to look at it is to treat it as if it were a cookie .
It is a technical tool basically for the marketing service, so other details are not important in our context.
This is implemented in the client (an HTML page somewhere), supported on the server if you want to control the identity. Usually the log is accessed to see what has been accessed. But you can have a server to handle that in a specific way. The process is simple and similar to the cookie .
<img src="http://tracking.dominio.com/pixel.gif?id=1234"/>