What is a third-party cookie?

A cookie set by a domain other than the site being visited, used to track users across sites for ad targeting and measurement.

Why are third-party cookies going away?

Privacy regulation and browser policy — Safari and Firefox block them by default, and Chrome has been phasing down support.

First-party data, server-side tagging and conversion APIs, contextual targeting, privacy-preserving APIs, and incrementality methods like geo holdouts.

Growth Marketing Glossary

Third-Party Cookie

third-par·ty cook·ie/θəɹd ˈpɑɹti ˈkʊki/noun

The quiet passenger that followed you from site to site — and the deprecation of it is rewriting how all of digital advertising works.

Schematic — the cross-site cookie

Term: Third-Party Cookie
Set by: A domain other than the one visited
Powered: Cross-site targeting, retargeting, measurement
Status: Blocked by Safari/Firefox; Chrome phasing down

Forms & parts of speech

3P cookie · clipped

The cross-site tracker.

"Our retargeting leans on 3P cookies — that pool shrinks every quarter."

Definition in plain terms

A third-party cookie is a small data file set by a domain DIFFERENT from the website a user is visiting — typically an ad-tech or analytics vendor — that follows the user across many sites. For two decades these cookies were the connective tissue of digital advertising: they powered cross-site retargeting, audience building, frequency capping, and conversion attribution. FIRST-party cookies (set by the site you're actually on) remain fine; it's the cross-site third-party kind that privacy regulation and browsers have turned against.

The mechanics

The dismantling is well underway: Safari (ITP, 2017) and Firefox block third-party cookies by default, and Chrome — the majority browser — has been phasing down support (a years-long, repeatedly-revised process). The consequences ripple through everything cross-site tracking enabled: retargeting pools shrink, third-party audience segments degrade, cross-site frequency capping breaks, and last-click attribution loses its plumbing. The replacements form the post-cookie stack: FIRST-PARTY DATA (your own customer data — the durable asset), server-side tagging and conversion APIs (sending data directly rather than via browser cookies), privacy-preserving APIs (Google's Privacy Sandbox), contextual targeting's revival, and incrementality methods (geo holdouts) that don't need user-level tracking at all.

When it matters

The third-party cookie's decline is the defining infrastructure shift of modern digital marketing — it matters to every team that retargets, builds audiences, or measures cross-site conversions. The strategic response separates the prepared from the scrambling: invest in first-party data collection (the asset that appreciates as cookies depreciate), adopt server-side measurement, lean on contextual and platform-native targeting, and validate everything with incrementality rather than cookie-based attribution. The teams treating it as an emergency in 2024 are the ones who ignored a decade of warning.

Worked example. A DTC brand built its entire acquisition on third-party-cookie retargeting — and watches performance erode quarter over quarter as the addressable pool shrinks. The post-cookie rebuild reallocates around durable signals: an aggressive first-party data program (email capture, accounts, a loyalty mechanic) builds owned audiences, the conversions API replaces pixel-only tracking server-side, contextual and broad-targeting creative does the prospecting the cookie used to, and a quarterly geo holdout validates the true incremental effect. Eighteen months on, the brand's measurement and targeting rest on assets it owns — while competitors still chasing the cookie's ghost watch their retargeting quietly die.

Failure modes to watch. Treating cookie deprecation as a sudden surprise rather than a decade-long shift; relying on third-party audience segments that degrade; measuring with cookie-based attribution as the pool shrinks; and failing to build the first-party data asset that replaces it.

Synonyms & antonyms

Synonyms

third-party cookie3P cookiecross-site cookie

Antonyms

first-party cookiefirst-party data (the durable replacement)

Origin & history

The HTTP cookie was invented by Lou Montulli at Netscape in 1994; the third-party (cross-site) use for ad tracking grew through the 2000s ad-network era. Its dismantling began with Safari's Intelligent Tracking Prevention (2017) and Firefox's default blocking (2019), with Google's Chrome phase-down (announced 2020, repeatedly delayed) the industry-defining event.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is a third-party cookie?: A cookie set by a domain other than the site being visited, used to track users across sites for ad targeting and measurement.
Why are third-party cookies going away?: Privacy regulation and browser policy — Safari and Firefox block them by default, and Chrome has been phasing down support.
What replaces them?: First-party data, server-side tagging and conversion APIs, contextual targeting, privacy-preserving APIs, and incrementality methods like geo holdouts.

Related tools & calculators

toolCAC calculator
toolLTV-to-CAC ratio

Resources & people to follow

referenceGoogle Privacy Sandbox documentation
referenceApple ITP / Safari tracking-prevention notes
referenceRGM analysis — first-party data is the asset that appreciates as cookies depreciate

Curated, non-competitor resources verified per term.

Related training

moduleMarketing analytics

Disciplines

Areas of marketing where third-party cookie is a core concern:

MeasurementGrowth strategy

Sources

trendsGoogle Trends — "third party cookie"