Prebid opened its code in 2015, not its boardroom

The revenue mechanism

Header bidding is a way for a publisher to offer the same ad impression to several exchanges at once instead of trying them one after another, so that the highest of several competing bids can win rather than whichever single exchange happened to be asked first. Prebid.org's own About page and its documentation site's Introduction to Header Bidding, both read as retrieved on 16 September 2026, describe how that technique moved from proprietary, single-vendor code into a shared open-source project.

What the documents show

The About page states “Prebid.js launched in 2015 to make header bidding easy for publishers by bringing conformity and simplicity to the header bidding process,” and characterises the environment before launch as “dominated by bad practices, closed proprietary tech, poor standards, and little to no cooperation amongst competing companies.” Rather than one exchange controlling the integration code, Prebid.js is described as “a simple, open tech layer upon which companies could add their code to a standard but optimised foundation,” a structure the page says made it, by the retrieval date, “the most widely used header bidding ‘container’ or ‘wrapper’ on the web.” The introduction document explains the mechanical change: a publisher's ad server had operated as a “black box” that made it hard to verify pricing or quality, whereas header bidding lets a site “gather bids from multiple sources that will then compete directly with bids from the ad server,” rather than waiting for each demand source in turn.

The assumptions exposed

“Open source” describes the code layer, not a guarantee every company using it competes on equal terms; Prebid.org's own governance description gives its Technology and Publisher committees one voted board seat each per year, while the rest of the board is the largest member companies, so influence is not evenly distributed. A publisher who assumes header bidding removes the ad server's discretion is over-reading the documents: bids from multiple sources compete alongside the ad server's own inventory, not in its place. Neither document states a revenue lift a publisher should expect from adopting it.

What to check before you rely on it

This is an editorial checklist. Confirm which version of Prebid.js, or which wrapper built on it, a current ad-ops setup runs, since the open project has kept changing since 2015. Check whether demand partners connected through a wrapper are ones a site's audience actually attracts bids from, since access to the code is not access to demand. Treat governance influence as concentrated among larger member companies, not evenly shared, when weighing whose priorities shape the roadmap.

• Which version of the open-source wrapper is running on the site today, and when was it last updated?
• Does the current bidder list reflect real, competitive demand for this site's inventory, not just a long list of connected names?
• Who sits on Prebid.org's board for the categories that represent this site's interests, and how much influence does that give a small publisher?

The most common over-read is treating open source as evidence of equal governance; Prebid.org's own description of its board structure shows influence still concentrated among its largest member companies.