How-to: Sellers.json

How to: Sellers.json 

Sellers.json provides a mechanism to enable buyers to discover who the entities are that are either direct sellers of or intermediaries in the selling of digital advertising. A published and accessible sellers.json file allows the identity of the final seller of a bid request to be discovered (assuming that they are ads.txt authorized). 

The SupplyChain(schain) object is used in order to pass sellers.json in Prebid logic and enables buyers to see all parties who are selling or reselling a given bid request. . Aggregators who manage Prebid wrappers on behalf of multiple publishers and handle payment on behalf of the publishers need to declare their intermediary status in the Supply Chain Object. As the Supply Chain Object spec prohibits SSPs from adding upstream intermediaries, Prebid requests in this case need to come with the schain information.

There are two ways of setting up sellers.json within our platform: 

  1. Using the same seller_id for all domains. 
  2. Using separate seller_id for each domain.

Using the same seller_id for all domains 

Within our platform, seller_id is a publisher’s id. In this case, there is no need to create new Publisher entity. Once Publisher is activated for your account, you will see an HBMP Auto-Generated default HBMP Publishers with Id (1) and all sites that were created earlier will be tied with this Publisher (2).

 

So the only thing you should do is to provide us with the following information for each domain: 

Where: seller_id - publisher’s ID from Header Bidding platform

name - business name of your publisher

domain - publisher’s domain (e.g, example.com)

seller_type: 

  • PUBLISHER - in case of direct relations with this publisher. 
  • INTERMEDIARY - in case of intermediary relations with this publisher. 

After this, we will add this information to our sellers.json and will handle it on our side. 

Using separate seller_id for each domain

  1. Publishers were created and tied to sites earlier. 

This way everything is pretty simple: the only thing you should do is to provide us with the following information for each domain: 

Where: seller_id - publisher’s ID from Header Bidding platform

name - business name of your publisher

domain - publisher’s domain (e.g, example.com)

seller_type: 

  • PUBLISHER - in case of direct relations with this publisher. 
  • INTERMEDIARY - in case of intermediary relations with this publisher. 

2. Sites were created without Publishers. 

Unfortunately, there is no ability to tie existing site to newly created Publisher. This way you need to: 

  1. Create Publisher

You can create new Publisher on Publisher tab (1) by clicking on the Create button (2).

And on the Publisher’s creating window enter the Publisher name (1) and Publisher description (2, optional parameter). Then click on the Create button. 

  1. Once Publisher is created, you have to create a new site instead of existing one. Please, note that once you archive site all prebid configurations (ad units with connected buyers) will be removed as well. So firstly you need to create a new site with the same configuration. Also, a new script will be generated for this site and you should update it in a code as well. 

How to tie a new site to a Publisher.

On the window of Site creation select a Publisher from a drop-down list of already created Publisher.

  1. After this, the next step is the same - you should to provide us with the following information for each domain: 

Where: seller_id - publisher’s ID from Header Bidding platform

name - business name of your publisher

domain - publisher’s domain (e.g, example.com)

seller_type: 

  • PUBLISHER - in case of direct relations with this publisher. 
  • INTERMEDIARY - in case of intermediary relations with this publisher.