What is the difference between a cookie, a tracking pixel and server-side tagging?
They are three different mechanisms for the same job — recognising visitors and recording what they did — operating at different layers.
A cookie is a small file a website stores in your browser. First-party cookies are set by the site you are on, and do useful work: keeping you logged in, remembering a basket, storing preferences. Third-party cookies are set by a different domain embedded in the page, typically an advertising network, and are what allowed tracking across unrelated sites. Browsers have progressively restricted them — Safari and Firefox block them by default, and Chrome's plans have shifted repeatedly — which is the single biggest disruption to digital advertising in years.
A tracking pixel is a tiny piece of code, historically a 1×1 transparent image, that fires a request to a third party when a page loads or an action occurs. Loading the pixel tells the advertiser you were there. Pixels are how conversion tracking, retargeting audiences and analytics events are usually implemented, and they typically set or read cookies as part of the process. Email open tracking works the same way, which is why blocking remote images blocks it.
Server-side tagging moves the collection off the browser. Instead of the visitor's browser sending data directly to a dozen third parties, it sends one request to a server you control, which then forwards data onward.
Why server-side has grown: it survives browser tracking restrictions and ad blockers better, improves page speed by removing third-party scripts, and gives you control over what leaves your infrastructure.
The honest caveat: it also makes tracking less visible to the user and harder to block, which is precisely why privacy advocates object. Consent obligations under GDPR and similar laws apply to what you do with the data, not to where the code runs — moving collection server-side does not remove the need for lawful basis and consent.