The story. Judge Leonie Brinkema’s ad tech remedies opinion was unsealed on September 16, and it means more than the 12-and-15-month build clock the market already knew about. Filed under seal on September 2, it adds a six-year compliance monitor, global scope, and specific nondiscrimination terms for AdX. (AdExchanger, “The Court Just Unsealed Judge Brinkema’s Remedies Decision In The Google Ad Tech Antitrust Case. Here’s Your TL;DR,” 16 September 2026)
01What happened
- The opinion sat sealed for two weeks. Brinkema filed it September 2. Both sides had 14 days to flag confidential material; neither did, and it went public, unredacted, on September 16.
- The interoperability bar is stricter than “connect it.” Google must link AdX and DFP to Prebid through integrations the court calls “functionally equivalent” — closing off a token connection that exists on paper but underperforms.
- AdX now owes rival ad servers the same bid terms DFP gets. It must submit real-time bids to competing ad servers on those terms. Google must also share win/loss bid data with publishers and document how DFP picks a winner.
- The monitor is real, but shorter than the DOJ wanted. The court set the monitor’s term at 6 years, down from 15 years — the term DOJ had requested — with full access to Google’s staff, systems and source code.
- DV360 stays untouched; everything else is global. The court found too thin a link between DV360 and the anticompetitive conduct to regulate it. The rest of the order applies worldwide, not just to US publishers.
- Two near-term dates now sit on the calendar. Both sides owe proposed final judgments by October 2. The remedies take effect 60 days after Brinkema signs the order — both ahead of the 12-and-15-month build work.
02What it means inside a GAM network
The 12-and-15-month deadlines are the number every publisher already has on a calendar. The opinion’s real enforcement teeth sit in the details around them. “Functionally equivalent” is the phrase worth underlining: the court pre-empted the obvious shortcut, a Prebid link that exists but routes bids worse than DFP’s own path. Paired with the same-terms rule on AdX’s bids into rival ad servers, that’s a nondiscrimination standard a GAM operator can hold a partner to once the build starts — not a vague promise of “access.” The six-year monitor, with source-code visibility, is a longer commitment than most behavioral antitrust remedies carry. It changes how much weight a publisher should put on a Google compliance claim in year one versus year four. And because the obligations are global, a European or Turkish GAM operator isn’t a bystander here. The interoperability mandate reaches their AdX and DFP setup the same as a US publisher’s.
The headline number — 12 months to open AdX, 12 to 15 to wire in Prebid — was public almost as soon as the ruling leaked in oral form.
03What publishers should do about it
04The bottom line
The headline number — 12 months to open AdX, 12 to 15 to wire in Prebid — was public almost as soon as the ruling leaked in oral form. The unsealed opinion adds the mechanics that make those deadlines enforceable: “functionally equivalent” integration language, same-terms bid access, a six-year monitor with source-code reach, and global scope. The build clock hasn’t changed. What Google can get away with while it runs has gotten narrower.