Intro to web bugs

Perspective: Web

What is it?
It is generally an electronic image (aka single-pixel GIF, web bug, pixel tag, clear GIF, tracking beacon, web beacon, or tracking pixel).
- Generally transparent or white with 1x1 pixel dimensions.
- used in conjunction with cookies

Where is it applicable?
- web pages
- rtf mail
- mobile (wap)

What purpose does it serve?
- allows a web site to count users who have visited that page, or
- access certain cookies (how)?
- measure and improve the effectiveness of certain advertising.
- collects info such as demographic and usage information (IP address, the time and for how long, browser type and previously set cookie values)
- used by third parties to monitor the activity of a site.

How does it work?
Every time a page is opened, it also causes a 'hit' on the site hosting the 'tracking pixel'. Along with the fetch for the data, that site has access to page/navigation info, cookies and other such info. If you add parameters to the img src, you can also start sharing/collecting addl. info.

Performance impact?
tbd

What can I do about it?
-- detect by looking at the source code for the web page - look for img tags that are sourced from sites different from the rest of the page
-- turn off browser cookies - you will still be tracked as a visitor - but at least you will be anonymous
-- block the sites that are being pointed to - to totally disable it

Industry acceptance:
-- All the major companies have got together and put together a policy on this
-- Here's what the EFF has to say on this

Other:
An email header that is similar to is: Disposition-Notification-To ref: RFC 4021

Perspective: Mobile

How is it being used for the mobile?
-- used by WAP sites in a manner similar to the web