A third-party cookie is a cookie set by a site other than the one in the address bar. Advertisers and analytics tools use them to follow a person from site to site. The status differs by browser. Safari and Firefox block them by default. Chrome still allows them and leaves the choice to the user, per Google’s latest update found for this entry, dated August 14, 2026.
What are third-party cookies?
A cookie is first-party when its domain matches the page the person is viewing. When the domain differs, it is a third-party cookie, also called a cross-site cookie (MDN). Browsers send third-party cookies when a page embeds content from another site, such as an image, a frame or an ad. They also send them when a person clicks a link from one site to another.
MDN gives a plain example. A company runs a shop, a forum and a service site on three domains. Each embeds a sign-in widget hosted on a fourth domain. The widget sets one cookie, so a person who signs in on one site is signed in on all three (MDN).
Other uses include analytics across sites and counting ad impressions to serve more relevant ads. One use fits loyalty well. An affiliate link can set a cookie so that a partner site shows a reward banner or credits a commission (MDN).
The same tool has a darker use. Third-party servers can combine cookies set across many sites to build a profile of a person’s browsing history, interests and habits. MDN calls cookies used this way tracking cookies (MDN).
Are third-party cookies going away?
Not everywhere. Each browser maker has made its own call, and the dates matter:
| Browser | Status | Date and source |
|---|---|---|
| Safari | Blocked by default | March 24, 2020 (WebKit) |
| Firefox | Total Cookie Protection by default | June 14, 2022 (Mozilla) |
| Chrome | Allowed, with a user setting | April 22, 2025 (Google) |
| Chrome Incognito | Blocked by default | April 22, 2025 (Google) |
| Edge | Blocks trackers from unvisited sites and known harmful trackers | MDN |
| Brave | Blocks tracking cookies by default | MDN |
Chrome took the longest road. In March 2020 WebKit noted that Chrome had announced full blocking by 2022 (WebKit). That plan changed. In July 2024 Google proposed to replace deprecation with a new experience that lets people make an informed choice (Google, July 22, 2024).
On April 22, 2025 Google decided to maintain its current approach to third-party cookie choice. It said it would not roll out a new standalone prompt (Google, April 22, 2025).
On October 17, 2025 Google said Chrome will keep that approach. It also retired ten tools in the Privacy Sandbox. Google cited low adoption (Google, October 17, 2025). The status page, last updated August 14, 2026, lists them for removal (Privacy Sandbox status).
Firefox’s Total Cookie Protection keeps each cookie in the site where it was created. That stops tracking companies from using it to follow a person from site to site (Mozilla). Safari lets an embedded service ask for cookie access through the Storage Access API, and the user must approve (WebKit).
Chrome supports two tools that work with cookies instead of against them. CHIPS, partitioned cookies, ships by default from Chrome 114 (status page). FedCM, for sign-in flows, has seen broad adoption. Google said in October 2025 that it will keep supporting both (Google).
Guides written before April 2025 describe a phase-out that did not happen. Check the date on any source. Our post on first-party data strategy makes the wider point: the cookie deadline was never the real reason to build first-party data.
What rules apply to third-party cookies?
In the EU, the ePrivacy Directive covers cookies. Article 5(3) allows a business to store data on a device, or read what is stored there, only with consent or for a listed need (EDPB Guidelines 2/2023). One listed need is a service the user explicitly asked for.
Regulators test banners against that rule. In September 2025 the CNIL fined SHEIN 150 million euros. It found ad cookies placed before a visitor touched the banner (CNIL).
In California, sharing means passing data to a third party for ads that follow a person across brands and sites (CCPA § 1798.140).
A business that shares data must treat an opt-out preference signal as a valid opt-out (11 CCR § 7025).
What do loyalty programs use instead?
Loyalty programs hold a better key than a cookie: a signed-in member. The program’s own data is tied to a verified member, so it survives device changes and browser policies, as the first-party data page explains. A cookie sees one browser. A member ID sees the person across devices and the store.
A first-party cookie is not the same as first-party data. A first-party cookie is set by the site a person is visiting. First-party data is what a company collects from its customers, in its own channels (first-party data strategy).
A shopper browses a retailer’s site on three devices and then pays cash for a lamp in the store. A cookie sees four strangers. After she joins the program at the till, the retailer has one member (first-party data strategy).
Starbucks shows the mix in its privacy notice. It says it uses first- and third-party cookies. Advertising technologies can be set by Starbucks or its advertising partners. On certain sites, members can opt out through a “Do Not Sell or Share” link or a Cookie Preferences link (Starbucks Privacy Notice).
For illustration, a program has 2,000,000 members, and 1,400,000 of them agree to ad matching. A partner match finds 40% of them. The program reaches 560,000 known members, with no third-party cookie involved. The same numbers hold in Safari, Firefox and Chrome, because the match runs on the member record.
How should a loyalty team plan for browsers that block cookies?
For a loyalty team, three states need a plan. Safari and Firefox visitors carry no cross-site cookies. Chrome visitors can keep them. In the EU, every non-essential cookie needs consent first. A campaign that works in only one of the three is a risk.
A cookie audit is a sensible first step. List every third-party cookie on member pages. Tie each to a purpose. Check that it fires only after the matching consent. Remove the ones nobody can explain.
Four checks guide the audit. Which cookies break when a browser blocks them? Which ones need consent in the EU? Which tools can ask for a sign-in instead? Which can be dropped? The answers set the order of work.
Three jobs replace what the cookie did. Login and consented email give identity. Controlled tests and shared environments, such as a data clean room, give measurement. Owned channels give reach first. Partner audiences matched with consent add to it.
How GRAVTY handles third-party cookies
Loyalty Juggernaut says program data beats rented data. Its first-party data page says program data is tied to a verified member instead of a cookie. It also lists a patented approach to making first-party data from what members do.
Frequently asked questions
Does Chrome still allow third-party cookies?
Yes. Google decided in April 2025 to keep its current approach, which leaves the choice to users in Chrome settings. Its October 2025 update repeated that Chrome will maintain that approach (Google).
What is the difference between first-party and third-party cookies?
A first-party cookie comes from the site the person is viewing, and a third-party cookie comes from a different site. MDN draws the line at the cookie’s domain and scheme (MDN).
Which browsers block third-party cookies by default?
Safari and Firefox block them by default, and Chrome blocks them in Incognito. Safari has done so since March 2020 (WebKit). Firefox made Total Cookie Protection the default in June 2022 (Mozilla).
Do third-party cookies need consent?
In the EU, yes. The exception is a cookie strictly necessary for a service the user asked for. Article 5(3) of the ePrivacy Directive allows reading or storing data on a device only with consent or for a listed need (EDPB).
What happened to the Privacy Sandbox?
Google retired ten of its ad tools in October 2025. It named Topics and Protected Audience among them, and it said adoption was low (Google).
