A Prebid Server proposal on GitHub would let publishers connect a third-party campaign server to Prebid Server and serve direct deals without Google Ad Manager. A first architecture draft was posted October 9, and comments were still arriving October 19.
What happened
Issue 4676 in the prebid-server repository was opened February 4, 2026. It states its goal as making Prebid Server “act as a primary ad server / decision making mechanism to enable GAM-less integrations.” The design is an adapter interface: Prebid Server would connect to any third-party direct campaign source and treat it as a black box that handles impression tracking, ad pacing, frequency capping and real-time campaign decisioning.
Contributor ollyburns posted a first-pass architecture draft on October 9. On October 17, a commenter asked how priority should work when several candidates come back, using a bid at priority 4 with no offset against a bid at priority 2 with a plus 3 offset, which resolve to 4 and 5. On October 19, another commenter proposed applying the offsets to final values as a follow-up feature.
Why it matters
Publishers who drop Google Ad Manager still need something that decides between a direct campaign and an open-market bid. The issue leaves open whether more than one campaign source is allowed, what changes for Prebid.js and the SDKs, and whether to build a reference campaign server. Our report on what the ad tech remedies change covers the remedy side.
One detail worth reading closely
In the priority example, an offset flips the order, since 2 plus 3 beats 4. In our reading, publishers adopting this model will set those numbers in configuration, and direct-deal buyers will be ranked against open bids by rules only the publisher can see. Our analysis of the remedies and demand makes a related point about who sets the rules.
