Prebid wants ad servers to bid into the header auction so AdX can compete without GAM seeing the winning price first.

Two auctions were a feature, not a bug, for the ad server

Classic header bidding runs Prebid first, then passes the winning demand into Google Ad Manager. GAM is bundled with AdX, so the house exchange sees the Prebid winner before it prices its own demand. Olly Burns, CTO at Teal and a co-author of the proposal, told AdExchanger that under the old flow Google got a look at the winning bid price of the Prebid auction, which allowed AdX demand to easily outbid the winning Prebid bidder.

That is an information asymmetry on the OpenRTB payload, not a malformed field. Buyers debugging loss reason 102 (timeout) on the Prebid path and wins on the GAM path are looking at two different assemblies of one impression. The Prebid vs TAM vs Open Bidding post is the same pattern with different wrappers: each path can carry different floors, deals, and privacy strings even when the ad unit looks unified in the ad server UI.

Reorienting so ad servers bid into Prebid puts AdX in the same auction as other SSP demand. AdExchanger quotes Burns saying Prebid would run a pre-auction and feed winning bids into GAM where Google's auctions actually took place; the proposed model removes that pre step. Constantine Mirin, CEO at Postindustria, told the outlet it will be interesting whether GAM becomes less dominant as a revenue source when the structural advantage disappears.

What the court asked for versus what Prebid is drafting

Judge Leonie Brinkema's remedies require Google to let AdX demand bid into ad auctions independently of its ad server, integrate its ad server with Prebid via an API or other connection, and provide publishers win and loss data. AdExchanger notes the court did not specify mechanisms. The Prebid working group pitched the ad-server-bids-into-Prebid model in April anticipating a possible GAM breakup; the court decided not to pursue that structural split.

Burns told AdExchanger the framework could satisfy all three requirements because Google's auction would happen alongside everyone else's. That is a stronger claim than logging equivalence on outbound OpenRTB, which is where the remedies compliance post focused: floors, user.eids, schain, and loss codes on the request Prebid Server emits. This week's proposal is about auction topology. Compliance teams still need both: the topology change only matters if the integrated path logs the same fields monitors will compare.

Prebid cannot force Google to integrate through Prebid Server. Brian Sardo, a senior software engineer at Microsoft who led the Summit presentation, told AdExchanger Google could plug into Prebid.js instead. The new framework is built for Prebid Server, so a browser-only integration would not deliver the full reversal. Prebid members speaking on background bet Google will adopt both, and that a ready Server framework before legal wrangling ends makes adoption more likely than a bespoke Google design.

One call instead of two changes latency and logging

Burns told AdExchanger that GAM is one of the worst offenders in slowing the internet down. Today Prebid often requires two calls, one to Prebid and one to GAM. Collapsing to one call pretty much halves the time, he said. For supply path QA, halving calls also halves the places where source.tid, imp.ext.tid, and consent strings can diverge, but only if the single call is the canonical log line your SSP exports.

Publishers evaluating the proposal should ask whether their analytics still attribute revenue to GAM line items when GAM is a bidder inside Prebid Server rather than the clearing house. OpenRTB still needs seat, bidid, and currency on the response. An ad server bid object that omits mtype or returns without a loss reason on no-bid will look like demand failure in dashboards that used to blame Prebid timeouts alone.

Legacy path (two hops):
  Browser -> Prebid auction -> winning bid + price
  Browser -> GAM ad server -> AdX sees Prebid winner, reprices

Proposed path (one hop, Prebid Server):
  Browser -> Prebid Server auction
    <- SSP bids
    <- GAM/AdX bid as ad-server bidder
  Single clearing price, no Prebid winner leaked to GAM first

The diagram is schematic. Real integrations still have mediation, ad rules, and direct line items. The wire consequence AdExchanger emphasizes is AdX competing without forcing publishers to use GAM as the auction host. Whether your stack logs that as one request or two depends on implementation, not press release wording.

Public comment until Q1 2027 is the only fixed date

The proposal is in public comment. Formalization is targeted for end of Q1 2027, then a future Prebid update. Until then, production traffic still follows the pre-auction into GAM pattern. Burns told AdExchanger Prebid wants to be on the front foot so publishers can influence the agenda, citing past Google industry overhauls that stalled despite broad participation.

Buyers should not rewrite OpenRTB validation rules for a bid request shape that is not live. Sellers should use the comment period to document where GAM currently mutates Prebid outcomes: currency on floors, deal IDs stripped on the ad server hop, and identity fields present only on the Prebid leg. Those diffs become the evidence if functional equivalence is argued later.

LG and Magnite agentic home-screen deals, also in this week's trade press, are a different supply path (CTV OEM inventory through a DSP agent). They do not replace the web header-bidding question Prebid is trying to solve. CTV pods still need pod fields on the request; this proposal is about who runs the auction for display and the GAM bundle.

What to log before the integration lands

• Capture paired requests on the same impression today: Prebid client or PBS outbound, and the GAM-bound payload with the Prebid winner attached.
• Record the Prebid winning price field GAM receives and whether AdX bids exceed it on the second hop.
• Diff regs.gpp, user.ext.consent, and user.eids between hops; a single-call future only helps if those strings survive the merge.
• Tag traffic by integration path in warehouse exports so a future Prebid Server ad-server bidder row does not merge with legacy GAM clearing rows.
• Validate OpenRTB in CI on the request your path actually emits; see the bid request tester and CI guide.

RTBlint is independent and not affiliated with Prebid.org, Google, or AdExchanger. It checks whether payloads match OpenRTB and exchange profiles. It does not predict whether Google will integrate through Prebid Server or whether the court will accept the proposal as remedy compliance.

Sources

• AdExchanger: Prebid's proposed auction overhaul (October 14, 2026)
• AdExchanger: Judge Brinkema's remedies decision (TLDR)
• RTBlint: Google ad tech remedies ruling and Prebid Server bid requests
• RTBlint: Prebid vs Amazon TAM vs Open Bidding