Google's partner ad opt-out exists because a judge said so
Google launched an opt-out for personalized ads on partner sites, but researchers say it was rushed under a settlement deadline and lacks full integration.
Data
A new privacy control quietly appeared inside Google's account settings pages in recent weeks, offering users the ability to limit personalized advertising on the millions of publisher websites and apps that use Google's technology to serve ads. The launch, spotted by Dr. Timothy Libert, founder of webXray, prompted an immediate question among privacy researchers: was this genuinely voluntary, or the result of legal pressure?
The answer, it turns out, was neither coincidental nor proactive. According to a follow-up post by Libert on LinkedIn, Google was required to add the control under a totally different settlement, and the deadline happened to be right after his audit was released.
That audit matters. The webXray California Privacy Audit, published on April 14, 2026, found that Google, Meta, and Microsoft continued to set advertising cookies on users' browsers even after those users had explicitly activated a Global Privacy Control opt-out signal. Libert's team reviewed traffic across more than 7,000 popular websites accessed from a California residential IP address. The results were stark: 55 percent of the sites set advertising cookies despite the opt-out signal. The aggregate potential liability from that finding was estimated at $5.8 billion. The audit's publication drew attention to long-standing questions about whether opt-out mechanisms work as described, let alone whether new ones will.
What the new partner ad settings control does
The new interface is labelled "Partner ad settings" and is accessible through a Google account. The page describes its purpose in direct terms: millions of partner sites and apps use Google technology to show ads and help fund their content, and the control allows users to choose settings for ads on those sites and apps. A single toggle - "Personalized ads on partner sites & apps" - is presented as the primary switch. Below it sits a section labelled "Related Google account controls" that expands to show more settings.
The distinction between this control and Google's existing personalization settings is significant, and has drawn scrutiny. Don Marti, who writes on privacy and advertising topics, noted in the LinkedIn comments that existing "personalized ads" controls in Google's main settings already exist, raising the question of how the two controls interact. According to Libert, his guess is that the new control should be connected to the main settings and currently is not, because they rushed it.
That observation points to a real technical gap. The new control appears as what Libert described as a pop-up in the main settings - a sign, in his reading, that Google had the feature built but deployed it before the integration with the main privacy and ads settings page was complete. If accurate, that means users who discover the new control and toggle it off may believe their preferences are propagating through Google's systems when, in fact, the signal may not be reaching the main personalization layer.
This is not a hypothetical concern. The RTB settlement approved by a federal judge on March 26, 2026 in the case In re Google RTB Consumer Privacy Litigation includes a specific "RTB Control" that strips user identifiers - including encrypted Google User IDs, device advertising IDs, and IP addresses - from real-time bidding bid requests when activated. That settlement required implementation within 30 days of final approval, creating a concrete legal deadline in late April 2026. The timing of the new Partner ad settings control aligns closely with that window.
The settlement behind the feature
The RTB litigation, which originated from a complaint filed on March 26, 2021, documented the scope of personal data sharing through Google's real-time bidding infrastructure. According to court documents, RTB bid requests include Google IDs for each account holder, IP addresses, cookie-matching services, user-agent information, publisher IDs, page URL content, unique device identifiers, and what the documents describe as "vertical" interests relating to race, religion, health, and sexual orientation. Google's system, according to expert testimony cited in the case, processes auctions across approximately 1.3 million publishers and handles billions of auctions daily.
The settlement reached on September 2, 2025, and approved on March 26, 2026, introduced injunctive relief rather than monetary damages for class members. Attorneys' fees were set at $21,856,239.22, with litigation costs at $3,488,792.96. Each of the seven named class representatives received $15,000. The class itself was estimated at between 169 million and over 200 million U.S. Google account holders.
According to the court order, Google must implement the RTB Control, publish a dedicated webpage describing it, and send a notification email to all currently active individual U.S. Google account holders - all within 30 days of final approval on March 26, 2026. PPC Land has covered the RTB settlement in detail, including analysis of how it interacts with open web display advertising economics.
What happens when the RTB Control is activated
When a user activates the RTB Control - which is what the Partner ad settings control appears to implement - the information that makes advertising inventory valuable to performance advertisers disappears from the bid stream. The control removes encrypted user identifiers from bid requests. It prevents cookie matching. It generalizes user-agent strings down to the major version level only. What remains is essentially contextual: information about the page, but not about the person viewing it.
For publishers, the economics shift accordingly. Targeted impressions command higher prices in programmatic auctions because they allow advertisers to reach specific audience segments. When that targeting data is stripped, the inventory reverts to something closer to contextual buying. The clearing price typically falls. Google's RTB system processes auctions across 1.3 million publishers; even modest adoption rates for the new control would produce distributional effects across that inventory base.
The concern raised by Marti about the relationship between the new Partner ad settings and the older "personalized ads" controls is therefore not merely a UX question. It is a question about whether the legal remedy actually functions as designed. As Marti framed it in the LinkedIn discussion: if someone clicks the RTB privacy control and believes they are done, they may never reach the full personalization control - drawing a parallel to how Apple maintains separate personalization settings distinct from its App Tracking Transparency prompts.
A pattern of deadline-driven privacy releases
Libert's read - that the feature was built in advance but deployed in a hurry - fits a broader pattern. Google's approach to privacy controls has repeatedly followed enforcement timelines rather than product planning cycles. The removal of non-personalized ads account-level controls from European AdSense settings in May 2025 came as regulators intensified scrutiny of how publishers manage user consent in the EEA. The enforcement action disabling conversion tracking for EU advertisers without Consent Mode v2 took effect on July 21, 2025, after years of warnings. The $1.375 billion Texas privacy settlement, finalized October 31, 2025, addressed allegations of unlawful location tracking, incognito browsing monitoring, and biometric data collection without consent.
Libert, who previously worked inside Google's privacy teams, was direct about the structural problem in his LinkedIn post. According to him, the engineering teams and privacy UX are best in the world, but they cannot do their jobs when leadership and legal keeps dumping gasoline on their heads while they are putting out fires. He described a period near the end of his tenure focused on diagnosing remediation stresses placed on engineering and UX teams by what he characterized as bad leadership decisions, and building systems to mitigate those stresses.
His comments are notable not because former employees criticize large companies - they frequently do - but because they describe a specific and verifiable failure mode: technically capable teams forced onto absurd deadlines because strategic and legal decisions produce compliance emergencies rather than allowing planned, integrated implementations. The result, in the case of the Partner ad settings, appears to be a control that exists but may not be properly wired into Google's broader privacy infrastructure.
Where the compliance burden lands
Marti introduced another dimension to the discussion, describing what he called "LiabilityMaxxing" - the practice of placing compliance obligations on smaller companies while the platform retains the structural benefits of the data-sharing system. He linked to a post arguing that publisher-side compliance obligations pile up: implementing consent management platforms, maintaining IAB TCF consent strings, updating partner lists, integrating new Google features as they are released. Meanwhile, the data that makes programmatic auctions function continues to flow from Google's systems.
This observation reflects the practical dynamic that PPC Land has documented across multiple coverage areas. Publishers using AdSense must now navigate the IAB Transparency and Consent Framework, Google's ad technology partner list - which itself is undergoing an experimental reshuffle scheduled to begin on or after April 20, 2026 - Restricted Data Processing mode configurations for individual US states, and Consent Mode v2 signal implementation inside Google Ads. Each layer represents a compliance task. Each task falls, operationally, on the publisher or their technology partners. Google provides the infrastructure and the documentation; the configuration work sits elsewhere.
The June 15, 2026 deadline for Google Analytics to transfer consent control authority entirely to Consent Mode within Google Ads adds another layer to the stack. From that date, the ad_storage signal within Consent Mode becomes the single governing parameter for what Google Ads can and cannot do with data linked from Analytics properties. Organizations without monitoring in place face the possibility of behavior changes they may not immediately detect, particularly given a 48 to 72-hour detection latency in Google's Tag Diagnostics system.
Why this matters for advertising professionals
The ad tech industry is accumulating privacy controls faster than it is integrating them. Google now has an RTB Control, a Partner ad settings toggle, main account personalization settings, My Ad Center, Restricted Data Processing mode, Consent Mode parameters, and Global Privacy Control signal handling - all of which theoretically interact, but which have been built at different times, under different legal pressures, and with varying levels of integration. Whether they collectively produce a coherent privacy experience for users - or a patchwork of overlapping and potentially contradictory settings - is something that auditors like Libert have committed to testing.
According to Libert's original post, he looks forward to verifying the new feature works as stated, at scale, in the next installment of the Global Privacy Audit. That audit will represent the clearest test of whether the new Partner ad settings control functions as a genuine privacy mechanism or as a deadline-compliant checkbox. The previous California audit found an 80 percent ad tech vendor failure rate - 194 of 242 vendors evaluated continued setting advertising cookies after opt-out. The question for the next round is whether Google's own properties perform any differently.
For marketing professionals who operate within Google's advertising ecosystem, the proliferation of user-facing privacy controls has a direct operational consequence. Each control that reduces data sharing in RTB bid requests narrows the audience data available for targeting. As PPC Land has covered previously, the EPIC and ICCL complaint filed with the FTC in January 2025 alleged that Google's RTB system broadcasts data on U.S. individuals approximately 31 billion times per day across 35.4 million websites, 91 percent of Android apps, and 75 percent of iOS apps. Any control that meaningfully interrupts that data flow - if it works - changes the fundamental economics of programmatic advertising at scale.
Timeline
- March 26, 2021 - Original complaint filed in Hewitt v. Google LLC, initiating the Google RTB Consumer Privacy Litigation
- January 16, 2025 - EPIC and ICCL file FTC complaint alleging Google's RTB system broadcasts data on U.S. individuals approximately 31 billion times per day; PPC Land coverage
- May 16, 2025 - Google removes non-personalized ads account-level controls from European AdSense settings; PPC Land coverage
- September 2, 2025 - Google RTB class-action settlement reached in the Northern District of California; PPC Land coverage
- October 31, 2025 - Texas finalizes $1.375 billion privacy settlement with Google; PPC Land coverage
- July 21, 2025 - Google disables conversion tracking for EU advertisers without Consent Mode v2; PPC Land coverage
- March 26, 2026 - Federal judge grants final approval to Google RTB settlement, requiring RTB Control implementation within 30 days; PPC Land coverage
- March-April 2026 - webXray conducts California Privacy Audit across more than 7,000 websites; finds 55 percent set advertising cookies despite GPC opt-out
- April 14, 2026 - webXray California Privacy Audit published; Google, Meta, and Microsoft flagged for continued cookie setting after user opt-out; PPC Land coverage
- April 20, 2026 (on or after) - Google begins experiment reshuffling AdSense ad technology partner list; PPC Land coverage
- Late April 2026 - Google launches "Partner ad settings" control allowing users to toggle personalized ads on partner sites; Dr. Timothy Libert identifies the launch and links it to the RTB settlement deadline
- June 15, 2026 - Google Analytics hands full consent authority to Consent Mode within Google Ads, making ad_storage the sole governing parameter; PPC Land coverage
Summary
Who: Google, Dr. Timothy Libert (Founder, webXray), and Don Marti (privacy researcher and commentator). The development also implicates the class of approximately 169 million to over 200 million U.S. Google account holders covered by the RTB settlement.
What: Google launched a new "Partner ad settings" control allowing users to opt out of personalized advertising on publisher websites and apps that use Google's ad technology. Researchers identified that the feature was required under a court-approved settlement in the Google RTB Consumer Privacy Litigation, not released voluntarily. The control appears not yet integrated with Google's main privacy and personalization settings, raising questions about whether it functions as described.
When: The Partner ad settings control appeared in late April 2026, within the 30-day implementation window mandated by the federal court order approving the RTB settlement on March 26, 2026. Dr. Libert's initial post appeared approximately two weeks before his updated post confirming the settlement connection.
Where: The control is accessible within Google account settings globally. The underlying litigation was filed in the Northern District of California. The webXray audit that brought attention to the issue examined traffic from a California residential IP address across more than 7,000 U.S. websites.
Why: Google was required to implement an RTB Control as part of the injunctive relief in the In re Google RTB Consumer Privacy Litigation settlement, which documented extensive sharing of user data - including identifiers tied to health conditions, religion, ethnicity, and sexual orientation - through the real-time bidding system. The rushed deployment reflects a recurring tension between legal deadlines and the engineering timelines needed for full integration of privacy controls into existing settings infrastructure.