How a first-party cookie works
The browser decides what kind of cookie it is looking at by comparing two things: the domain in the address bar and the domain that set the cookie. When they match, the cookie is first-party. Your shop sets a basket cookie, your site sets a login session, your analytics tag writes an identifier under your own domain — all first-party, because the visitor is on your site at the time.
This is a matter of context, not ownership. The same analytics vendor’s script can produce a first-party cookie on your site and a third-party one elsewhere. What matters is whose address bar the visitor is looking at when the cookie is written. That single test is what separates a cookie the browser treats as ordinary housekeeping from one it treats with suspicion.
Why first-party cookies matter
Browsers have spent years tightening the rules on cookies set by other domains while leaving first-party cookies largely intact. If your measurement depends on a first-party identifier, more of it survives, and it survives in more browsers. That is the whole reason server-side tagging and custom tagging subdomains exist.
They also carry the parts of a site that cannot be given up. A basket, a signed-in state, a saved language, a form that remembers half-typed answers — none of these work without a cookie set by the site itself. This is why blanket advice to “turn off cookies” is unhelpful for a business: the question is never whether to use them, but which ones need permission first.
Where first-party cookies go wrong
The most common misunderstanding is that first-party means permanent. It does not. Safari shortens the life of cookies written by scripts rather than by the server, so an analytics identifier can expire long before its stated date and a returning visitor is counted as a new one. Being first-party helps; it is not immunity.
The second is assuming first-party means consent is not required. It is the purpose that decides. An advertising identifier stored under your own domain is still an advertising identifier, and it belongs behind the banner along with everything else that is not needed to make the page work.
The third is a subdomain mismatch. Set a cookie on the main site and read it from a booking system on a different domain and you have two disconnected visitors, one journey, and a report that makes no sense.
What to do about it
Check which of your cookies really are first-party by opening the site in a private window and reading the domain column in the browser’s storage panel. Anything written under a vendor domain is a third-party cookie, whatever the plugin’s marketing said.
Where measurement matters and Safari traffic is significant, look at whether the identifier is being written by the server rather than by a script, since that is what decides how long it lives. And keep any booking engine, help desk or payment step on the same root domain wherever the platform allows it — a shared root domain is the cheapest fix available for broken analytics and tracking, and it needs no extra infrastructure at all.
