Third-party cookies and AdSense: browser status and revenue effects
Key takeaways
- In April 2025, Google said Chrome would keep its current approach of letting users choose about third-party cookies in settings, and would not roll out a new standalone prompt.
- In October 2025, Google announced it would retire most Privacy Sandbox technologies, including Topics, Protected Audience, Attribution Reporting and Shared Storage, while keeping CHIPS, FedCM and Private State Tokens.
- Safari has blocked third-party cookies by default since March 2020, and Firefox began rolling out Total Cookie Protection, a separate cookie jar per site, by default in June 2022.
- Google says its advertising cookies may be set from domains such as doubleclick.net and googlesyndication.com, and that some, like _gads, are set in the domain of the site the user visits.
- Third-party cookie availability is one of several factors behind AdSense revenue by browser, alongside consent choices, country and device.

As of November 2026, third-party cookies are still available by default in Chrome, which dropped its plan to phase them out. Safari blocks them by default and Firefox isolates them per site. For AdSense publishers there is nothing to implement: Google handles the ad technology. What changes is revenue by browser, where cookie access is one factor among consent, country and device.
This guide is based on announcements from Google, Apple’s WebKit team and Mozilla, and on Google’s cookie documentation. It describes the technical status; it is not legal advice about consent.
What is the status of third-party cookies in each browser?
| Browser | Third-party cookies by default | Source and date |
|---|---|---|
| Chrome | Allowed; users can block them in settings | Google, April 22, 2025 |
| Chrome Incognito | Blocked | Google, April 22, 2025 |
| Safari | Blocked | WebKit, March 24, 2020 |
| Firefox | Partitioned per site (Total Cookie Protection) | Mozilla, June 14, 2022 |
In its April 2025 announcement, Google said it had “made the decision to maintain our current approach to offering users third-party cookie choice in Chrome, and will not be rolling out a new standalone prompt for third-party cookies”. It added that Incognito “already blocks third-party cookies by default”.
The WebKit team wrote in March 2020 that “cookies for cross-site resources are now blocked by default across the board” in Safari. Mozilla’s June 2022 post explains that Total Cookie Protection “works by creating a separate ‘cookie jar’ for each website you visit”, so trackers “just get to see behavior on individual sites”.
What happened to the Privacy Sandbox?
Google’s October 2025 update split the technologies into two groups:
| Kept | Retired |
|---|---|
| CHIPS (partitioned cookies) | Attribution Reporting API (Chrome and Android) |
| FedCM (identity flows) | IP Protection |
| Private State Tokens | Protected Audience (Chrome and Android) |
| Private Aggregation, including Shared Storage | |
| Topics (Chrome and Android) | |
| Related Website Sets, SelectURL, SDK Runtime, On-Device Personalization, Protected App Signals |
How did Chrome’s plan change over time?
Much of the advice still online was written for a Chrome without third-party cookies. The April 2025 announcement summarizes how that plan evolved:
| When | What Google said or did |
|---|---|
| 2019 | Announced the Privacy Sandbox initiative |
| 2022 | Entered a formal engagement with the UK’s CMA and ICO |
| Summer 2024 | Said it was exploring a new approach to third-party cookies in Chrome |
| April 2025 | Kept user choice in settings; no standalone prompt; continued Incognito protections |
| October 2025 | Retired most Privacy Sandbox advertising and measurement technologies |
In April 2025, Google also noted that IP Protection for Incognito was planned for the third quarter of 2025. Six months later, IP Protection appeared in the list of retired technologies. Plans in this area have changed more than once, so date-check any article before acting on it.
Google cited “low levels of adoption” and said it would follow Chrome and Android processes to phase out the retired technologies. For measurement, it pointed to a proposed interoperable Attribution standard developed through the W3C.
Some Google pages have not caught up. The AdSense help article on limited ads still says Google uses the Shared Storage API for invalid traffic detection when limited ads are on. Expect that wording to change; see limited and non-personalized ads.
Which AdSense cookies are third-party?
Google’s advertising technologies page says advertising cookies “may be set from a few different domains, including google.com, doubleclick.net, googlesyndication.com, or googleadservices.com, or the domain of our partners’ sites”. Its cookies page adds that some ad cookies “are set in the domain of the website you visit”, giving _gads as the example.
| Cookie or signal | Party on your site | Affected by third-party cookie blocking? |
|---|---|---|
IDE, id (doubleclick.net, google.com) |
Third-party | Yes, blocked in Safari, partitioned in Firefox |
_gads (your domain) |
First-party | No, but still subject to consent rules |
| IP address, page URL, browser data | Sent with each request | No |
Google also states that “even if cookies are removed or disabled in your browser, Google may use cookie-based information or other advertising technologies to personalize ads” unless users turn off personalized ads in their ad settings. In other words, blocking third-party cookies does not switch ads off; it changes what data is available for targeting and measurement.
What does this mean for AdSense revenue?
Google does not publish AdSense RPM by browser. What you can say from the mechanics:
- Chrome traffic keeps full cookie access unless the user blocks it, so personalization and frequency capping work as before where consent allows.
- Safari and Firefox traffic has less cross-site data. Advertisers bidding on audiences or measuring conversions across sites may bid less.
- Consent outweighs browser in Europe. An EEA visitor on Chrome who refuses consent gets non-personalized or limited ads regardless of cookie availability. See consent mode v2 and AdSense for the signal side.
- Device and country matter more. Safari is the default browser on Apple devices, so browser and device mix overlap, and mobile RPM often differs from desktop. Read RPM by country and device before blaming cookies.
What can visitors control themselves?
Google’s cookies page points users to browser controls: most browsers “allow you to manage how cookies are set and used as you’re browsing, and to clear cookies and browsing data”, and Chrome’s settings let users “delete existing cookies, allow or block all cookies, and set cookie preferences for websites”. The advertising page adds that users can turn off personalized ads in Google’s ad settings. In that case, they “may still see ads based on factors such as your general location derived from your IP address, your browser type, and your search terms”.
For publishers, this means three separate switches decide what an AdSense request can use:
| Switch | Who controls it | Effect on AdSense ads |
|---|---|---|
| Browser cookie settings | Visitor and browser vendor | Limits cross-site identifiers |
| Consent choice in your CMP | Visitor, through your banner | Decides personalized, non-personalized or limited ads in Europe |
| Google ad settings | Visitor, in their Google account | Turns off personalization across Google’s ads |
None of these is something you can override, and you should not try. Accurate disclosure in your privacy policy and a working consent banner are the publisher’s side of the arrangement.
How should a publisher respond?
- Do not add Privacy Sandbox code. The main ad APIs are being retired, and AdSense does not require publishers to implement them.
- Keep a certified CMP for EEA, UK and Swiss traffic; consent rules apply to first-party cookies and other identifiers too.
- Update your privacy policy to describe the cookies and technologies Google actually uses, linking to Google’s pages rather than listing every cookie; see privacy policy for AdSense.
- Segment reports by platform and country to see where revenue differs, and track it over time.
- Invest in content and page experience, which help every browser equally: contextual ads depend on what the page is about.
Common mistakes
- Planning for a “cookieless Chrome” deadline. Google dropped the phase-out in April 2025.
- Installing Topics or Protected Audience scripts. They are being retired and were never required for AdSense.
- Assuming no third-party cookies means no consent needed. First-party identifiers and device access still fall under consent rules.
- Blaming Safari for every revenue gap. Device and country mix often explain more.
- Relying on old blog posts. Much of what was published between 2020 and 2024 described plans that changed.
Frequently asked questions
Is Chrome still phasing out third-party cookies?
No. In April 2025 Google said Chrome would maintain its current approach to third-party cookie choice and would not roll out a new standalone prompt; users keep choosing in Chrome's privacy settings. Incognito mode already blocks third-party cookies by default. In October 2025 Google then announced the retirement of most Privacy Sandbox advertising APIs.
Should I implement Topics or Protected Audience on my AdSense site?
No action is needed from AdSense publishers, and Google announced in October 2025 that it would retire Topics, Protected Audience, Attribution Reporting, Private Aggregation and Shared Storage, among others. AdSense handles ad technology on Google's side. Keep your consent setup, ads.txt and page experience in order instead.
Why do Safari visitors earn less than Chrome visitors?
Several reasons can combine: Safari blocks third-party cookies by default, which limits cross-site personalization and measurement; Safari is the default browser on iPhones and iPads, so browser and device mix overlap; and country mix differs by browser. Compare by device and country in AdSense reports before attributing a gap to cookies alone.
Do I still need consent if browsers block third-party cookies?
Yes, where the law requires it. Consent rules cover storing or accessing information on a device in general, including first-party cookies like _gads and other identifiers, not only third-party cookies. Google's EU user consent policy and certified CMP requirement also apply regardless of browser.
Sources
- Next steps for Privacy Sandbox and tracking protections in Chrome · Privacy Sandbox (Google)
- Update on Plans for Privacy Sandbox Technologies · Privacy Sandbox (Google)
- Full Third-Party Cookie Blocking and More · WebKit
- Firefox rolls out Total Cookie Protection by default to more users worldwide · Mozilla
- How Google uses cookies · Google
- Advertising (Google Privacy & Terms) · Google
Related guides
- Personalized, non-personalized and limited ads: the three AdSense serving modes compared
How AdSense picks personalized, non-personalized or limited ads from consent signals, what each mode still collects, the ad code switches and the setting to check.
- Consent mode v2 and AdSense: two consent signals, one site
Google consent mode v2 explained for AdSense sites: why AdSense reads the TCF string, not consent mode, and how to keep Analytics and AdSense signals aligned.
- Writing a privacy policy for a site that shows AdSense ads
What a privacy policy must say on a site running AdSense: Google as a party, cookies, the link Google requires, consent withdrawal, US opt-outs and a template.
- IAB TCF v2.3 for publishers: what Google requires, what changed from v2.2, and v2.4
TCF v2.3 is mandatory for TC strings created since March 1, 2026. What changed from v2.2, Google's dates, the purposes AdSense needs, and the v2.4 update.