A title bidding wrapper is a Javascript label that resides on the publisher’s webpage and makes asynchronous calls to demand mates. A wrapper is basically used to organize multiple demand mates and set the rules for running the transaction.
Using a wrapper ensures that all demand mates have their shot requests touched off at the same time. In addition, the wrapper enforces downtime settings, i.e., how long the cybersurfer will stay for stab to respond. In short, wrappers streamline the perpetration of title bidding.
Basis their function, header bidding wrappers can be client-side, server-side, or hybrid. And depending on who built it, they can be open-source, paid, self-serve, and managed.
As we ’ve explained, wrappers live to make title bidding perpetration easier for publishers. With a wrapper, rather of adding and managing the law for each demand mate collectively, a publisher can just add or drop demand mates from the wrapper as demanded.
Wrappers can also contain announcement label canons for services similar as shadowing, analytics, and viewability that are to be run on publisher runners. Though their primary function is generating shot requests, collecting flings, and communicating them to the announcement garçon.
Generally speaking, these are the steps involved in how that process works:
Still, you can suppose about wrappers as label operation tools for managing demand sources, If you're familiar with label operation software. While using a wrapper isn't obligatory for setting up title bidding, it makes easy work of working with multiple demand mates and simplifies communication with the announcement garçon.