Analytics and Tracking

Third-Party Cookie

Also called 3P cookie, cross-site cookie

One set by a domain other than the site being viewed, which is how vendors once followed browsers across the web.

Quick facts: Third-Party Cookie

Category
Analytics and Tracking
Also called
3P cookie, cross-site cookie
Level
Beginner
Affects
Retargeting reach, view-through conversions, cross-site frequency capping
Where to see it
Browser developer tools in Safari and Chrome, Meta Events Manager, Google Ads audience manager
In this article4
  1. How a third-party cookie works
  2. Why third-party cookies matter now
  3. Where third-party cookies go wrong
  4. What to do about it

Pages load resources from other domains all the time: an advertising pixel, an embedded video, a chat widget, a font. Each of those requests can carry a cookie belonging to the domain that served it. Because the visitor is on your site rather than the vendor’s, the browser files that cookie as third-party.

The reason it became so valuable to advertisers is repetition. The same vendor’s code sits on thousands of unrelated sites, and the same cookie is returned on every one of them, so one company can watch a single browser move across the web. That capability — not the storage of a little text — is what made third-party cookies the centre of two decades of privacy argument.

Why third-party cookies matter now

Mainly because you can no longer rely on them. Safari and Firefox block them by default, and have for years. Chrome still allows them by default after Google reversed its plan to remove them, but it has added its own controls and the direction of travel is clear. Anything in your measurement or advertising that quietly depends on one is already failing for a large slice of your audience, and the reporting rarely tells you so.

The practical damage shows up as retargeting audiences that fill slowly, view-through conversions that disappear, and cross-site frequency capping that no longer caps anything. For most small businesses those symptoms arrive gradually and get blamed on the market rather than on the browser.

Where third-party cookies go wrong

The first trap is a vendor claiming full recovery. There is no configuration setting that restores cross-site tracking in a browser that has decided against it, and any tool promising complete accuracy is describing something browsers no longer permit. Treat that claim as a reason to ask harder questions.

The second is confusing them with first-party cookies. A pixel that writes an identifier under your own domain is not affected by third-party blocking, so “cookies are dead” is far too broad a statement to plan around. The third is failing to test. Owners check their site in Chrome, see the numbers they expect, and never open Safari, where a meaningful share of their traffic actually is.

What to do about it

Start by finding out how much you depend on them. Open your own site in Safari with the developer tools showing, complete a real conversion, and see which tags still record it. That test takes minutes and usually answers the question better than any vendor dashboard.

Then move the work you can onto first-party foundations: identifiers set under your own domain, conversions sent from your server rather than the browser, and audiences built from your own customer lists instead of borrowed browsing history. If retargeting is central to how you sell, plan around shorter windows and smaller audiences, and lean more on your own email marketing list, which no browser update can take away from you.

Do and do not

Do

  • Test a real conversion in Safari, not only in Chrome
  • Move conversion sending to your server where possible
  • Build audiences from your own customer lists

Do not

  • Believe any tool that promises full cross-site recovery
  • Assume all cookies are blocked — first-party ones are not
  • Plan retargeting budgets on audience sizes from years ago

Questions people ask about this

Are third-party cookies blocked everywhere?

Not everywhere, but in enough places to matter. Safari and Firefox block them by default. Chrome still permits them by default after Google stepped back from removing them, though it offers users their own controls. If your audience skews towards iPhone, assume a large part of it is already invisible to any cross-site cookie.

What breaks when third-party cookies stop working?

Mostly the things that need to recognise a browser across different websites: retargeting audience building, view-through conversion counting, and frequency capping across publishers. Your own site keeps working normally, because logins, baskets and on-site analytics rely on cookies set under your own domain rather than a vendor's.

Is server-side tracking a replacement?

It is a partial one. Sending conversions from your server improves what reaches the ad platform and reduces losses to blockers, but it cannot recreate a record of someone's browsing on other people's websites. Use it to protect the measurement of your own customers, and expect cross-site audiences to stay smaller than they once were.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.