How to Add a New Video Bidder Adapter
At a high level, a bidder adapter is responsible for:
- Sending out bid requests to the ad server
- Registering the bids that are returned with Prebid.js
This page has instructions for writing your own video-enabled bidder adapter. The instructions here try to walk you through some of the code you’ll need to write for your adapter.
When in doubt, use an adapter that already has support for video for reference, such as the AppNexus AST adapter in the Github repo. (The code samples and descriptions below are based on it.)
- Step 1: Prepare prerequisites for a pull request
- Step 2: Add a new bidder JS file
- Step 3: Design your bid params
- Step 4: Send out bid requests
- Step 5: Register bid responses
- Helper functions
- Further Reading
Step 1: Prepare prerequisites for a pull request
In your PR to add the new adapter, please provide the following information:
- The contact email of the adapter’s maintainer.
- A test ad unit that will consistently return test creatives. This helps us to ensure future Prebid.js updates do not break your adapter.
- Any other information listed as required in CONTRIBUTING.md.
Step 2: Add a new bidder JS file
Create a JS file under
moduleswith the name of the bidder suffixed with ‘BidAdapter’, e.g.,
Your adapter should export the
callBidsfunction. Prebid.js executes this function when the page asks to send out bid requests.
Step 3: Design your bid params
bid.params object for defining the parameters of your ad request. You can include tag ID, site ID, ad size, keywords, and other data, such as video bidding information.
For more information about the kinds of information that can be passed using these parameters, see the list of bidder parameters.
In order to make sure your adapter supports video, you’ll need to:
videoobject to your adapter’s bid parameters like the one in the AppNexus AST adapter. To see an example showing how those video params are processed and added to the ad tag, see the AST adapter’s implementation of the
Your bidder will have to support returning a VAST URL somewhere in its bid response. Each new bidder adapter added to Prebid.js will have to support its own video URL. For more information, see the implementation of pbjs.buildMasterVideoTagFromAdserverTag.
Step 4: Send out bid requests
When the page asks Prebid.js to send out bid requests, your bidder’s
callBids(bidRequest) function will be executed, sending out bid requests to your bidder.
bidRequest object contains information about the bids in the request as shown below. This example uses an AppNexus AST video bid request, so keep in mind not everything will be the same for your own bidder.
Note that you should keep track of the
adUnitCode in bid requests (this is also known as the “placement code” by some bidders). You’ll need this later on when you register the bid response with the bid manager.
Step 5: Register bid responses
When the bid response(s) are available, notify Prebid.js immediately, so that your bid can get into the auction as soon as possible. A bidder’s API will usually have an event listener that notifies you when the bid responses are back.
IMPORTANT NOTE FOR VIDEO BIDDERS
If your bidder supports serving video ads, it needs to provide a VAST video URL in its response. On the adapter side, your implementation of
createBid needs to add the VAST URL to the bid. For an example implementation, see the implementation of
createBid in the AppNexus AST adapter.
Create the bid response object
If the bid is valid, create the bid response as shown below, matching the bid request/response pair. For details about the status codes, see constants.json.
If the bid is invalid (no fill or error), create the
bidObject as shown below.
Add info to the bid response
Once you’ve created the bid response, assuming it’s valid, you must add more video-specific information:
- Player width
- Player height
- VAST URL
Note that you’ll have to modify the example code below to match the parameters returned by your bidder. We’ve also omitted a lot of error-checking. You can refer to the AppNexus AST adapter implementation for details.
Register the bid response with the bid manager
Now that you’ve added the required information to the bid response, you must register the response with the bid manager by calling the
bidmanager.addBidResponse(adUnitCode, bidObject) function. To register multiple bid responses, call the function multiple times.
In bidder API’s callback, there’ll be ID(s) that tie back to the request params in the
bid object. Building a map from
adUnitCode to the request param(s)/ID(s) will help you retrieve the
adUnitCode based on the callback.
adloader.loadScript(scriptURL, callback, cacheRequest)
Note that loading external code into your adapter will be prohibited starting with Prebid 1.0.
Load a script asynchronously. The callback function will be executed when the script finishes loading.
Use this with the
cacheRequest argument set to
true if the script you’re loading is a library or something else that doesn’t change between requests. It will cache the script so you don’t have to wait for it to load before firing the supplied callback.