Validate your PB implementation (Web Player)

After following the steps to Set up Player Bidding, you should validate your implementation.

1. On a page that has a player with PB implemented, open your browser's developer tools panel.
2. On the Console tab, type jwplayer().getConfig() at the prompt. The console returns the configuration of the player similar to the following screenshot.

You are now prepared to begin the validation process explained in the following sections.

---

Verify player configuration settings

1. On the Console tab, verify that the advertising.bids object is present.
2. Confirm that the following properties have the correct values:
   • bidders[].id
   • bidders[].name
   • bidders[].pubid
   • settings.buckets
   • settings.mediationLayerAdServer

If you need to change any values, refer to the documentation for your implementation.

---

Verify the SpotX bidder script has loaded

📘

If SpotX is not set as a bidding partner bids.bidders[].name: "SpotX", you can skip this section.

1. On the Network tab, in the filter field, enter js.spotx.tv/directsdk/v1 to locate the value in the network traffic.
2. Clear the filter or search field and enter cdn.spotxcdn.com/integration/directsdk to locate the value in the network traffic.

If both values are present in the network traffic, the SpotX bidder script is loaded.

---

Confirm bid requests are sent and processed correctly

On the Network tab, in the filter field, enter the filter string for a bid partner you are using.

Successful bid requests return a 200 code response. Unsuccessful bid requests return a 204 nobid code response.

Repeat this step for each bid partner you are using.

---

Confirm bid requests are sent and bid responses are received

📘

If your mediation layer is not jwp, you can skip this section.

1. Click the Network tab of the browser developer tools panel.
2. In the filter field, enter e=abq to show the ping request for the bid request. The vpb property contains the bid request information.

3. Clear the filter field and enter, enter e=abr to show the ping request for the bid response. The vpb property contains the bid response.

💡

Alternatively, on the Console tab at the console prompt, enter the following to enable listeners that capture the details of the bid request and bid response: jwplayer().on('adBidRequest adBidResponse', (e) => { console.log(e)})

---

Confirm bidder key-values are present in the ad tag

📘

If your mediation layer is not dfp or jwpdfp, you can skip this section.

1. On the Network tab of the browser developer tools panel, locate your ad tag. You can filter the network traffic by using the identifier from the ad tag.

2. Click on the ad tag to reveal the headers for the ad tag in the Headers tab.

3. In the Query String Parameters section, locate cust_params.

4. Verify that bidder key-values appear in the cust_params parameter. The following table lists the possible bidder partner key-value pairs.

   
   

   Bid partner	Bid price key	Ad key
   Adtelligent	hb_pb_adtelligent	hb_cache_id_adtellig
   AppNexus	hb_pb_appnexus	hb_cache_id_appnexus
   EMX	vpb_emx_bid	vpb_emx_key
   Index Exchange	hb_pb_ix	hb_cache_id_ix
   Media.net	hb_pb_medianet	hb_cache_id_medianet
   MediaGrid	vpb_mediagrid_bid	vpb_mediagrid_key
   OneVideo	hb_pb_oneVideo	hb_cache_id_oneVideo
   OpenX	hb_pb_openx	hb_cache_id_openx
   PubMatic	vpb_pubmatic_bid	vpb_pubmatic_key
   Rubicon	hb_pb_rubicon	hb_cache_id_rubicon
   Sonobi	hb_pb_sonobi	hb_cache_id_sonobi
   SpotX	spotx_bid	spotx_ad_key
   District M	hb_pb_districtmDMX	hb_cache_id_district
   Synacor Media	hb_pb_synacormedia	hb_cache_id_synacorm
   Unruly	hb_pb_unruly	hb_cache_id_unruly

   
   

   

📘

If no bid was received by an SSP bidder bidder.result=0 then no cust_params will be appended to the ad tag for that bidder.