Back to Bidders

Yahoo SSP

Features

Bidder Code yahoossp Prebid.org Member yes
Media Types display, video GDPR TCF Support no
User IDs All USP/CCPA Support yes
Supply Chain Support yes COPPA Support yes
Demand Chain Support no GPP Support no
Supports Deals check with bidder Prebid.js Adapter yes
IAB GVL ID 25 Prebid Server Adapter yes
Floors Module Support no First Party Data Support check with bidder
Multi Format Support check with bidder ORTB Blocking Support check with bidder
Safeframes OK check with bidder

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_yahoossp hb_bidder_yahoossp hb_adid_yahoossp
hb_size_yahoossp hb_source_yahoossp hb_format_yahoossp
hb_cache_host_yahoos hb_cache_id_yahoossp hb_uuid_yahoossp
hb_cache_path_yahoos hb_deal_yahoossp

Disclosure

This adapter may not handle user syncs for TCF2 or GPP correctly. The user sync consent querystring parameters are generated at the time of the bid request and might be stale at the time of the user sync. See https://github.com/prebid/Prebid.js/pull/9345#issuecomment-1362887086

Important Notice (JS vs PBS)

There are differences between our Prebid.js & Prebid-Server Yahoo SSP adapters. The Prebid-server adapter currently does not support:

  1. Integration via the pubId method.

yahoossp Prebid.js Mandatory Bid Params

The ‘yahoossp’ bid adapter supports 2 alternate integration types:

  1. dcn & pos (Site/App & Position explicit targeting) - For legacy “aol”, “oneMobile” adapter partners/publishers.
  2. pubId (Publisher ID) - For New partners/publishers joining Yahoo SSP and legacy “oneVideo” partners/publishers migrating to the Yahoo SSP.

    yahoossp Prebid-Server Mandatory Bid Params

    Prebid-server adapter supports one integration method:

    • dcn & pos (Site/App & Position explicit targeting) - For legacy “aol”, “oneMobile” adapter partners/publishers.

      DCN & POS Integration Parameters (JS & PBS)

      For legacy “aol”, “oneMobile” adapter partners/publishers.

Name Scope Description Example Type
dcn Required Site ID provided by Yahoo SSP ‘site1’ string
pos Required Placement ID provided by Yahoo SSP ‘placement1’ string

PubId Integration Parameters (JS Only)

For New partners/publishers joining Yahoo SSP floors_supported: true and legacy “oneVideo” partners/publishers migrating to the Yahoo SSP.

Name Scope Description Example Type
pubId Required Your Publisher External ID provided by Yahoo SSP ‘DemoPublisher’ string
siteId Optional Ability to target a specific Site using an External ID provided by Yahoo SSP ‘1234567’ string
placementId Optional Ability to target a specific Placement using an External ID provided by Yahoo SSP ‘header’ string

Prebid.js Adapter Supported Features

For further setup details & examples please see https://github.com/prebid/Prebid.js/blob/master/modules/yahoosspBidAdapter.md

  • Media Types: Banner & Video
  • Outstream renderer
  • Multi-format adUnits
  • Schain module
  • Price floors module
  • Advertiser domains
  • End-2-End self-served testing mode
  • Outstream renderer/Player
  • User ID Modules - ConnectId and others
  • First Party Data (ortb2 & ortb2Imp)
  • Custom TTL (time to live)

Thanks you, Yahoo SSP

Back to Bidders