What cookieless actually refers to
The word is shorthand for a group of separate changes that arrived at different times. Safari and Firefox block third-party cookies by default. Safari’s Intelligent Tracking Prevention also shortens the life of some first-party cookies when they are written by JavaScript. Chrome’s plans for third-party cookies have been announced, delayed and revised more than once. Alongside that, consent rules in many markets stop any non-essential cookie being written until a visitor agrees.
None of that removes first-party cookies. Your login session, your shopping cart and the identifier GA4 writes for your own domain all still work. What has gone, or is going, is the ability of a company on another domain to recognise the same browser as it moves around the web — which is why the honest phrase is third-party cookie restrictions, not “cookieless”.
Why the wording matters
Loose wording leads to bad decisions. Business owners hear that cookies are finished and conclude that analytics no longer works, that remarketing is impossible, or that a consent banner has become pointless. None of those follow. Remarketing on your own site data, conversion measurement and audience reporting all still function.
It also creates a market for products sold as “cookieless tracking” that in practice write a first-party cookie from a server, or that identify visitors by combining browser characteristics. The first is a reasonable technique with a misleading name. The second raises exactly the privacy questions the restrictions were introduced to address, and consent law tends to cover it regardless of how the identifier is stored.
Where the cookieless claim goes wrong
The most damaging mistake is assuming cookieless means consent is no longer needed. Consent rules apply to storing or reading anything on a visitor’s device and, separately, to processing personal data. Changing the storage mechanism does not remove the obligation.
The second is buying a tool on the promise that it restores complete measurement. Nothing does. Server-side tagging moves where a cookie is set and can extend how long it survives in some browsers, which narrows the gap, but visitors who refuse consent or block requests are still invisible.
What to do about it
Say what you mean. In a proposal or a report, write “third-party cookie restrictions” or name the specific browser behaviour, so the reader can check the claim. Vague words hide whether a problem is real.
Then strengthen what you own. Collect first-party data with a clear reason for the visitor to hand it over, pass conversions to platforms from your own server where it is worth the effort, and implement consent properly so the modelled figures that fill the gaps are based on a signal the platform can read. Expect measurement to remain incomplete and plan reports around that, rather than around a tool that claims otherwise. If you are unsure which of these your site already does, an independent check of your tracking is a sensible first step.
