You want five SSPs bidding on your page. You could paste five vendor tags and hope they do not collide, fight over the same slot, and tank your page speed. Or you use one piece of software that runs them all in one orderly auction. That software is Prebid.js.
Prebid.js is the dominant open-source wrapper (also called a container). One library that orchestrates the whole header-bidding auction across all your demand partners, so you manage one thing instead of N.
Why a wrapper, not N tags
- Without one: every SSP tag has its own timeout, its own way to break, and they race each other for the same ad slot. No single auction, no single result.
- With a wrapper: one global timeout, one orderly auction, one normalized winner handed to the ad server. Maintainable, and far kinder to page speed.
The component model
| Component | What it does |
|---|---|
| Prebid core | The auction engine: fires the bidders, collects responses, picks the winner. |
| Bid adapters | One per SSP. Translates your generic ad unit to and from that SSP’s exact request. |
| Analytics adapters | Report what happened in the auction to an analytics endpoint. |
| Modules | Optional features you opt into: identity, price floors, consent, currency, and more. |
Key idea
A Prebid build is core plus the adapters and modules you choose. You ship only what you need, because every adapter is more code in the page, and page weight is real money.
Quick check
Why run one managed wrapper instead of pasting five SSP tags by hand?
Note
Bidcliq Academy reads a real Prebid config in the Analyze tool, and Inspect reads the live one straight off a running page.