Web Beacons are implemented in web analytics usually as 1 pixel by 1 pixel transparent images. By tracking how many times this web beacon is loaded, webmaster can find out how many times the page has been loaded, and other meaningful metrics -like the IP address, cookie information, time the page was accessed, and more. Web beacons are also used extensively in emails to track open rates.
Here are some benefits and disadvantages of using web beacons for web analytics.
Web beacons are easy to implement – mostly using just a simple “IMG” HTML tag. Most of the information processing is done on the server side.
Because most search robots do not execute and load image requests, you can optimize your logs just to track and extract what you need to know about the visitor, without complicate filtering. This also reduces the size of your log files.
The same beacon can be used to collect information across different domains and websites. Since most of the processing is done on the “server” side, you can just collate all the information on one server. Typical web statistics are only stored locally in the server where the domain is hosted.
Many new email programs and already web mail clients have a characterize to have images turned off my default, and since the beacon is essentially an image, you won’t be able to track these visitors.
The typical installation of a beacon requires third party cookies – which is increasingly been afflicted by the strict default privacy settings in new web browsers. Visitors with anti spyware programs will also have these third party cookies deleted making visitors difficult or impossible to track.
Lastly, web beacons have a bad rap as far as the Internet goes because it has been closely identified with browsing privacy issues.