Prebid.js is the open-source JavaScript library publishers use to run header bidding in the page. Prebid.org maintains the API. bidtune does not publish a fork of it.
An ad unit in Prebid is the slot you want to fill: a code, the media type and sizes, and the bidders invited to that slot. Each bidder entry names an adapter that was compiled into your build, plus the parameters that adapter expects. Those parameters are the bidder's, not Prebid's, and not bidtune's.
The library's other half is configuration: auction timeout, price floors, bid caching, user sync, and what gets sent to the ad server. Those are the decision docs in this section. The vocabulary around the auction - SSP, DSP, OpenRTB - lives in the glossary.
Prebid's own description of the library is on What is Prebid.js?. Prebid Server is different software. It runs auctions off the page. This page is the browser library only.
Ad units are registered, then requestBids runs the auction. The bids array is where each adapter's parameters go. Copy them from that bidder's Prebid doc. A placeholder here would be a fake placement.
var adUnits = [{
code: "div-1",
mediaTypes: {
banner: { sizes: [[300, 250]] }
},
bids: [{
bidder: "bidderCode",
params: {}
}]
}];
pbjs.que.push(function () {
pbjs.addAdUnits(adUnits);
pbjs.requestBids({ bidsBackHandler: sendAdServerRequest });
});One library, one auction, and a public API. Adapters are open, so a publisher can see which bidders were actually compiled into the build they ship.
A build that includes every adapter is a large script. A build that omits the Price Floors module will ignore a floors config. Version upgrades move defaults - bid caching, for example, changed default in Prebid.js 2.0. Pin the version you mean to run.