← Back to Blog

Third-Party Cookies Survived in Chrome — Safari and Firefox Already Killed Them

Quick Answer: Chrome is the only major browser that still allows third-party cookies by default after Google dropped its removal plan in 2025 (Search Engine Land, 2025). But Safari caps script-set cookies at 7 days under ITP, Firefox partitions or blocks cookies for known trackers, and Brave blocks them outright (Cookie Status, 2026). Even Chrome restricts cookie lifetime to a maximum of 400 days. Treat a meaningful share of your audience as cookieless today — the browsers that block cookies already cover it.

Which browser still allows third-party cookies by default?

Chrome is the one major browser with no restrictions on third-party cookies, after Google dropped its plan to remove them (Cookie Status, 2026). That decision, confirmed in 2025, made Chrome the outlier — every other major browser had already blocked or partitioned third-party cookies years earlier.

The “cookies are back” headlines that followed Google’s reversal created a dangerous assumption: that cross-browser tracking is working fine. It isn’t. Chrome keeping cookies means Chrome-only tracking works. It says nothing about Safari, Firefox, or Brave, which together handle a significant share of your WooCommerce traffic — especially on mobile, where Safari dominates.

The real picture is a split web. Chrome users get full cookie-based tracking. Everyone else gets degraded or no cookie-based tracking. If your measurement strategy depends on cookies alone, you’re measuring only the Chrome segment of your audience accurately.

Chrome confirmed in 2025 it would keep third-party cookies, scrapping a planned consent prompt (Search Engine Land, 2025).

Do Safari and Firefox block third-party cookies?

Yes — Safari blocks third-party cookie access entirely and Firefox partitions or blocks it for known trackers by default (Cookie Status, 2026). This isn’t new. Safari’s Intelligent Tracking Prevention has blocked third-party cookies since 2017. Firefox’s Enhanced Tracking Protection has done the same since 2019.

The difference between the two is mechanism. Safari uses a classifier that identifies cross-site trackers and blocks their cookie access entirely — no exceptions, no partitioning. Firefox partitions cookies by top-level site for known trackers on the Disconnect list, which means a tracker can set a cookie but it’s scoped to each site individually and can’t be used for cross-site identification.

For WooCommerce measurement, the practical effect is the same: no cross-site tracking on either browser. Your ad platform cookies can’t follow a user from your site to another and back. Attribution breaks. Retargeting audiences shrink. Conversion windows shorten to whatever the first-party cookie limit allows.

Related: The Privacy Browser Trifecta: How Brave, Firefox, and Safari Combined Are Costing You 15–20% of Tracking Data

What does Safari’s ITP do to first-party cookies?

Safari deletes a tracker’s site data after 30 days of browser use without interaction, and caps script-set cookies at 7 days (Cookie Status, 2026). This is the part most “cookies are fine” takes miss entirely — Safari doesn’t just block third-party cookies, it actively shortens first-party ones.

The 7-day cap applies to cookies set via JavaScript (document.cookie), which is how most analytics and ad platforms set their client-side cookies. Your GA4 _ga cookie, your Google Ads _gcl_aw cookie, your attribution cookies — all capped at 7 days on Safari. A customer who visits on Monday and converts the following Tuesday is a new user in your analytics because the cookie expired.

Server-set cookies (HTTP response headers from your own domain) are exempt from the 7-day cap. That’s the technical reason server-side tracking recovers Safari data: the cookie is set by the server, not by a script, and Safari treats it as a genuine first-party interaction rather than a tracker’s workaround.

Safari’s ITP caps script-set first-party cookies at 7 days (Cookie Status, 2026).

Yes — Chrome restricts cookies to a maximum lifetime of 400 days even while allowing third-party cookies (Cookie Status, 2026). This is rarely the binding constraint for WooCommerce tracking — most attribution windows are measured in days or weeks, not months — but it means even Chrome isn’t truly unlimited.

The 400-day cap was introduced quietly as part of Chrome’s privacy adjustments and aligns with the maximum Max-Age and Expires values the browser will honour. Set a cookie for 2 years and Chrome silently reduces it to 400 days. For most tracking use cases, this changes nothing. For long-cycle B2B or high-consideration purchases where the sales cycle exceeds 13 months, it could clip your longest attribution paths.

How much of the web already runs without third-party cookies?

Safari, Firefox, and Brave have blocked them for years, so a large share of traffic is already cookieless regardless of Chrome (IAPP, 2025). The exact percentage depends on your audience mix, but for a typical WooCommerce store, non-Chrome browsers account for 25–45% of sessions.

Mobile Safari alone is the biggest contributor. On a store with 60% mobile traffic and 40% iOS share within that, you’re looking at roughly 24% of total sessions on a browser that blocks third-party cookies and caps first-party ones at 7 days. Add Firefox and Brave desktop users and the cookieless share climbs higher.

Here’s the thing — Chrome’s decision to keep cookies didn’t restore anything. It preserved the status quo for one browser. The other browsers were already cookieless. The gap that existed before Google’s announcement still exists. If you weren’t measuring Safari and Firefox users accurately before, nothing changed for them.

Related: Chrome Kept Third-Party Cookies — So Why Is Your WooCommerce Store Still Losing Conversion Data?

When did Chrome confirm it would keep cookies?

Chrome confirmed it would maintain third-party cookie choice in 2025, scrapping a planned standalone consent prompt (Search Engine Land, 2025). Google originally intended to phase out third-party cookies in 2024, then delayed to 2025, then replaced the phase-out with a user-choice prompt, and finally dropped the prompt too.

The decision came after years of industry pushback and regulatory uncertainty. Google’s Privacy Sandbox was supposed to replace cookies with privacy-preserving APIs, but advertiser adoption was low and the alternatives weren’t mature enough to fill the gap.

The practical effect: Chrome’s third-party cookie behaviour stays as it is. No removal, no prompt, no user-facing change. Advertisers who track through Chrome see no difference. Advertisers who need cross-browser measurement see no improvement — the Safari and Firefox gaps remain exactly where they were.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

Does CHIPS change the picture?

Partly — CHIPS keeps an opt-in mechanism for partitioned cookies, one of only two Privacy Sandbox technologies Google retained (Privacy Sandbox, 2025). CHIPS (Cookies Having Independent Partitioned State) lets a third-party service set cookies that are scoped to the top-level site, which survives partition-based blocking in browsers that support it.

For WooCommerce, CHIPS matters if you embed third-party widgets — payment processors, chat tools, embedded checkouts — that need to maintain state across visits. Without CHIPS, those widgets lose their cookies every time a user returns to your site on a partitioning browser. With CHIPS, the cookie persists but is isolated to your domain.

CHIPS doesn’t restore cross-site tracking. A partitioned cookie by definition can’t be used to identify a user across different sites. It solves the legitimate use case of embedded services maintaining session state on your specific site, not the advertising use case of following users across the web.

CHIPS is one of only two Privacy Sandbox technologies Google retained (Privacy Sandbox, 2025).

What’s the practical takeaway for measurement?

Treat a meaningful slice of your audience as cookieless today, because the browsers that block cookies already cover it (Cookie Status, 2026). Server-side collection and first-party data strategies aren’t future-proofing — they’re present-day requirements for accurate measurement.

BrowserThird-party cookiesFirst-party cookie capKey restriction
ChromeAllowed400 daysNo cross-site tracking restriction
SafariBlocked7 days (script-set)ITP deletes tracker data after 30 days without interaction
FirefoxPartitioned/BlockedNo specific capEnhanced Tracking Protection blocks known trackers
BraveBlockedNo specific capAggressive blocking of all cross-site trackers

The fix for the non-Chrome gap is server-side first-party collection — setting cookies from your own server rather than from JavaScript, and routing events through your own domain rather than through third-party endpoints. Server-set cookies bypass Safari’s 7-day cap. First-party routing survives Firefox’s tracker blocking. A managed solution like Transmute Engine handles both — server-side cookie setting and first-party event routing for WooCommerce — recovering the conversion data that client-side tracking loses on every non-Chrome browser.

The question isn’t whether cookies are dead. They’re alive in Chrome and dead everywhere else. The question is whether your measurement strategy works for the browsers where cookies are already gone. For most WooCommerce stores, it doesn’t — and Chrome keeping cookies only masks how much data you’re missing.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • Chrome is the outlier: it’s the only major browser that still allows third-party cookies after Google’s 2025 reversal.
  • Safari caps at 7 days: script-set first-party cookies expire within a week, fragmenting returning visitor data.
  • Firefox partitions known trackers: third-party cookies exist but are scoped per-site, breaking cross-site attribution.
  • Chrome’s 400-day cap: even Chrome limits cookie lifetime, though it rarely binds for typical attribution windows.
  • 25–45% of WooCommerce traffic is already cookieless: Safari, Firefox, and Brave users are invisible to cookie-only tracking.
  • Server-side collection is the fix: server-set cookies bypass ITP’s 7-day cap and first-party routing survives tracker blocking.
Which browser still allows third-party cookies by default?

Chrome is the one major browser with no restrictions on third-party cookies, after Google dropped its plan to remove them (Cookie Status, 2026). Every other major browser — Safari, Firefox, and Brave — blocks or partitions them by default.

Do Safari and Firefox block third-party cookies?

Yes — Safari blocks third-party cookie access entirely and Firefox partitions or blocks it for known trackers by default (Cookie Status, 2026). This has been the case for years, regardless of Chrome’s decision.

What does Safari’s ITP do to first-party cookies?

Safari deletes a tracker’s site data after 30 days of browser use without interaction, and caps script-set cookies at 7 days (Cookie Status, 2026). This means your GA4 and ad platform cookies expire within a week on Safari, fragmenting returning visitor data.

Does Chrome cap cookie lifetime at all?

Yes — Chrome restricts cookies to a maximum lifetime of 400 days even while allowing third-party cookies (Cookie Status, 2026). This is rarely the binding constraint for tracking, but it means even Chrome isn’t unlimited.

How much of the web already runs without third-party cookies?

Safari, Firefox, and Brave have blocked them for years, so a large share of traffic is already cookieless regardless of Chrome (IAPP, 2025). The exact percentage depends on your audience, but mobile Safari alone typically accounts for 25-40% of e-commerce traffic.

When did Chrome confirm it would keep cookies?

Chrome confirmed it would maintain third-party cookie choice in 2025, scrapping a planned standalone consent prompt (Search Engine Land, 2025). Google chose to keep cookies and let users manage preferences through existing Chrome settings instead.

Does CHIPS change the picture?

Partly — CHIPS keeps an opt-in mechanism for partitioned cookies, one of only two Sandbox technologies Google retained (Privacy Sandbox, 2025). CHIPS gives sites a way to set cookies that are scoped to the top-level site, which survives partition-based blocking.

What’s the practical takeaway for measurement?

Treat a meaningful slice of your audience as cookieless today, because the browsers that block cookies already cover it (Cookie Status, 2026). Server-side collection and first-party data strategies aren’t future-proofing — they’re present-day requirements.

References

  1. Cookie Status (2026). Browser tracking protections compared. Source
  2. IAPP (2025). Google ends third-party cookie phaseout plans. Source
  3. Search Engine Land (2025). Google scraps new cookie prompt in Chrome. Source
  4. Privacy Sandbox (2025). Update on plans for Privacy Sandbox technologies. Source