Glossary
What is Header bidding wrapper?
Also called: wrapper, Prebid wrapper, managed wrapper
A header bidding wrapper is the code that runs the header auction on a page, managing bidders, the timeout and the hand-off to the ad server.
हिंदी में पढ़ेंA wrapper wraps many demand partners into one auction. It sends bid requests to each SSP, waits until a timeout, picks the best bids and passes them to the ad server as key-values. Prebid.js is a widely used open-source wrapper.
Running a wrapper is ongoing work: choosing bid adapters and builds, upgrading at least every six months, setting up line items, consent, analytics and timeouts, and adding an ads.txt line for each bidder. Prebid’s code is free; the work around it is not.
Publishers either self-host Prebid or use a managed wrapper, where an outside company installs and runs Prebid for them, usually for a revenue share or fee and often using its own SSP accounts. Teams with engineers often self-host; small teams often use a partner. Before signing, ask three things: the fee, whose SSP accounts are used, and whether you get bidder-level reporting.
Example
A wrapper calls 4 SSPs with a 1,000 ms timeout. Three answer in time with $1.90, $2.30 and $2.05; the fourth answers at 1,200 ms and is ignored. The wrapper passes $2.30 to the ad server.
Why it matters to publishers
The wrapper decides which bids reach your ad server, so who runs it and how it is configured shapes both revenue and page speed.