Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Third-Party Cookies

Cookies set by a domain other than the site visited, used to recognise a browser across sites.
Ad TechtechnologyUpdated

Definition

Every cookie belongs to a domain. A first-party cookie is set by the site in the address bar and is readable only by that site; it remembers a login, a basket, a language choice. A third-party cookie is set by a different domain whose content is embedded in the page, such as an ad tag, a tracking pixel or a social widget. The browser stores it under that other domain and sends it back whenever content from the same domain loads again, on any site.

That cross-site return trip is the whole point. A single ad tech company embedded on many publishers can recognise one browser on all of them, build a history of what that browser looked at, and act on it. It is a browser identifier, not a person identifier: one person on a laptop and a phone is at least two cookies, and clearing cookies makes a browser look new.

What it enabled

Three things that open-web advertising took for granted rested on third-party cookies.

  • Cross-site audiences. Data companies collected browsing signals into segments, sold through a DMP, and ad platforms used cookies to show ads to people who had visited an advertiser's site, the basis of display Remarketing.
  • Frequency capping. Limiting how often one browser sees an ad requires recognising it across the sites where impressions are bought.
  • View-through measurement. Linking an ad seen on one site to a purchase later on another depends on the same identifier appearing in both places, which shaped how Attribution counted display.

Inside programmatic buying, cookie syncing lets a supply-side platform and a buyer's platform match their separate cookie values for the same browser so audience segments can be looked up at auction time. The programmatic ecosystem guide describes that match and why it is partial even where cookies work.

Browsers block or restrict third-party cookies to differing degrees, and their policies have changed more than once, so the share of traffic without a usable cookie is something to measure in a campaign's own reports rather than assume. Consent rules add a second filter: in regions that require it, a cookie used for advertising should only be set once the visitor has agreed. The privacy and consent guide covers how browser changes compound regulatory ones, and why measurement now works from a partial view.

The effects show up in specific places. Audience lists in a demand-side platform shrink, as the DV360 audiences guide explains, because browsers that block these cookies remove their users from most display lists. Reach and frequency become harder to count: a browser that cannot be recognised looks new every time, so reported reach rises and frequency falls, a distortion the cross-platform reach and frequency guide works through. Stack design changes too; the guide to designing a marketing stack notes that the cookie-based data management platform has largely given way to first-party data held by the business.

Third-party versus first-party

The distinction applies to both cookies and data, and the two are easy to blur. A first-party cookie is set by the site being visited; First-Party Data is information a business collects from its own customers, through its site, app, purchases and sign-ups. Third-party cookies and third-party data both come from outside the relationship. The comparison of first-party and third-party data sets out why plans increasingly rest on data the business controls. What replaces third-party cookies is not one technology but a mix: signed-in identity inside large platforms, hashed customer lists, publisher identifiers, contextual targeting based on the page rather than the person, and modelled conversions where direct observation is missing.

Illustrative example — not a real result

A travel insurer's frequency cap stops working

Wigeonquay Travel Insurance sets a frequency cap of three impressions per week on a programmatic display campaign. Its ad server reports an average frequency of 2.6 and reach of 900,000 browsers, which looks well controlled. A panel survey of 1,000 people in its target audience suggests many saw the ads six or more times. The reason is that about 40% of impressions went to browsers that block cross-site cookies, each counted as a new browser at every visit, so the cap never applied to them. The insurer moves that share of budget to contextual deals on travel publishers and to audiences built from its own quote-form visitors, and reports frequency only for the part of delivery it can actually recognise.

First-Party Data is the main replacement for audiences built on third-party cookies. A DMP was the system that stored cookie-based segments, and its role has shrunk with them. Remarketing on the open web depended on cookies to recognise past visitors, and Attribution of display and video lost much of its view-through evidence as cookies became unreliable.

Common confusions

  • All cookies are being blocked. First-party cookies, which keep sites working, are not the target of these restrictions.
  • A cookie identifies a person. It identifies a browser on a device, and only until it is cleared.
  • Consent fixes the problem. Consent permits the cookie; a browser can still block it.
  • The change is finished. Browser policies have shifted more than once and still differ by vendor.
  • Contextual targeting is a lesser fallback. It targets the page instead of the person and needs no identifier at all.

More terms to look up

Where this term is used

Related