How do HTTP cookies differ from web beacons or tracking pixels?

How do HTTP cookies differ from web beacons or tracking pixels?

• A. Cookies require servers; beacons operate only on the client side.
• B. Cookies store data in the browser; beacons are tiny requests that track whether you opened content or visited a page.
• C. Cookies are only used for analytics; beacons are used for authentication.
• D. Cookies are legal documents; beacons are satellites.

Answer: (B)

The main idea is how data is stored and used: cookies keep small pieces of data in your browser, while web beacons (tracking pixels) are tiny requests that report back to a server about what you did. Cookies hold information like your login state, preferences, or identifiers so the site can recognize you on future visits. Beacons don’t store data in the browser; they trigger a request (often a 1x1 image or small script) to a server to indicate that content was opened or a page was visited, providing data the site can analyze. So cookies are a client-side store that the site reads on subsequent requests, whereas beacons are data-collection signals sent to a server. The other statements aren’t accurate: cookies aren’t limited to servers, beacons aren’t purely client-side, cookies aren’t only for analytics, and beacons aren’t satellites or legal documents.

The main idea is how data is stored and used: cookies keep small pieces of data in your browser, while web beacons (tracking pixels) are tiny requests that report back to a server about what you did. Cookies hold information like your login state, preferences, or identifiers so the site can recognize you on future visits. Beacons don’t store data in the browser; they trigger a request (often a 1x1 image or small script) to a server to indicate that content was opened or a page was visited, providing data the site can analyze. So cookies are a client-side store that the site reads on subsequent requests, whereas beacons are data-collection signals sent to a server. The other statements aren’t accurate: cookies aren’t limited to servers, beacons aren’t purely client-side, cookies aren’t only for analytics, and beacons aren’t satellites or legal documents.