Schain - Supply Chain Object Module
Last edited: 2024/06/24
What are Schain and sellers.json in Prebid?
Sellers.json and SupplyChain are mechanisms designed to identify all intermediaries involved in the flow of money from the buying platform to the publisher.
Service providers that manage Prebid wrappers for multiple publishers and handle their payments must declare their intermediary status in the Supply Chain (SChain) object. According to the IAB OpenRTB SupplyChain Object Specification, SSPs are not allowed to add upstream intermediaries. Therefore, publishers or Prebid.js managed service providers are responsible for specifying the SChain information.
In complex supply chains, these mechanisms enhance transparency and help identify and prevent fraudulent or otherwise unacceptable supply sources, based on the business policies of the advertising consumer.
How to include Schain information in Prebid Stack?
In the Old Platform
- First, define a new ad network:
- Go to Prebid Stack > Setup > Ad networks
- Click on Add new .
- You will be redirected to a page, where you have to add:
- Ad network name - The name of the schain, used for your own convenience only, it will not be used outside of Yieldbird Platform.
- Ad network ASI - The canonical domain name of the SSP, Exchange, Header Wrapper, etc. system that bidders connect to. This may be the operational domain of the system, if that is different than the parent corporate domain, to facilitate WHOIS and reverse IP lookups to establish clear ownership of the delegate system. This should be the same value as used to identify sellers in an ads.txt file if one exists.
- Click Save
- Add Domain SIDs
- Go to Prebid Stack > Inventory > Domains > the domain you want to edit > Ad networks SID
- Input the SID of the given Domain (as provided by the ad network)
- Add Bidders that belong to a third party:
When adding or editing bidder in Own bidders select the ad network it belongs to by changing the <Relationship> from Direct to Ad Network, and specifying which ad network this bidder belongs to. Remember to fill in <Bidder SID>.
In the New Platform:
- First, define a new supply chain:
- Go to Global setup > Schain and click Add new.
- You will be redirected to a view where you can create a new schain. Input Supply chain name, ASI and Default Domain SID and click Save.
- Supply chain name - The name of the schain, used for your own convenience only, it will not be used outside of Yieldbird Platform.
- ASI - The canonical domain name of the SSP, Exchange, Header Wrapper, etc. system that bidders connect to. This may be the operational domain of the system, if that is different than the parent corporate domain, to facilitate WHOIS and reverse IP lookups to establish clear ownership of the delegate system. This should be the same value as used to identify sellers in an ads.txt file if one exists.
- Default Domain SID - The identifier associated with the seller or reseller account within the advertising system. This must contain the same value used in transactions (i.e. OpenRTB bid requests) in the field specified by the SSP/exchange.
- Optionally customize Domain SIDs for particular Domains.
- Go to Global setup > Schain. In the overview table click on the schain where you want to update Domain SIDs (you can also click on Actions > Edit)
- Go to Domain SIDs tab
- Here you can add specific domain SIDs for this particular schain. If the Custom Domain SID field is left blank, it means that the default Domain SID is applied.
- After editing click Save.
- Add Bidders or Amazon UAM / TAM account that belongs to a third party.
After creating a schain, to make it operational you have to add Third party provider bidders to the schain.