Sellers.JSON Info and Setup

Background

Sellers. JSON and SupplyChain (or SCHAIN) are mechanisms used to identify all intermediaries that participate in the flow of money from the buying platform back to the publisher.

These do not include any intermediary that does not participate in money flow and doesn’t include systems that are paid a fee for their services but don’t pay upstream sellers. In cases of complicated supply chains, this enables increased transparency and the ability to identify and prevent fraudulent or otherwise unacceptable supply sources, according to the business policies of the consume Advertising System (SSPs/DSPs).

Aniview is completely compatible with the Sellers.JSON and SCHIAN protocols; They can be fully set up on the platform and managed with Aniview’s assistance (contact your dedicated Customer Success Manager for more details).

Part 1 - Platform Set Up

Step 1: General Account settings:

Open

Open

• Tag ID (not mandatory): Your TAG ID, if you are TAG certified (for more details: https://www.tagtoday.net/tagregistry/)

• DUNS Number (not mandatory): For more details: https://www.dnb.com/dunsnumber.html

• Version: Set to the latest available version your file supports. 

• Domain: Network domain for operating the sellers.json (your root company domain). Please contact your Client Success Manager to configure this line. 

• Contact email

• Contact Address: Your headquarter company address.

Step 2: Setting up you Publishers or Apps/Sites:

Aligning your Supply with the Sellers.JSON file is done according to the way you manage your Supply on Aniview - either working with (a) Publisher accounts or (b) App/Sites.

(a) If you are working with Publisher Connections:

a.2. In the publisher configuration screen, configure the following fields:

•  Domain: The Publisher's domain (in the case of a publisher that owns and manages multiple sites - enter the company's root domain).

• Seller Type: Can be defined as PUBLISHER, INTERMEDIARY or BOTH:
  PUBLISHER: Indicates that this entity represents direct relations with a site or app (e.g a site or app that is paid directly by you).

  INTERMEDIARY: Indicates that this entity's inventory is not owned by it (e.g an App or Site that is paid via third party that sells you it's inventory; NOT directly by you).

  BOTH: Indicates that this entity sells both types of inventory - direct and third party.

• Seller Name: The name that will appear on the Sellers.JSON file itself (if left blank, the name that will be used is the one that is defined in the Publisher Name).

• Seller ID: Represents the unique ID of the respective seller with your ecosystem; It is used to identify the seller by external buyers (SSPs/DSPs) (if left blank, the ID that will be used is the Publisher ID generated by the system).
  
  

(b) If you are working with App/Sites:

• Seller ID: Represents the unique ID of the respective seller with your ecosystem; It is used to identify the seller by external buyers (SSPs/DSPs) (if left blank, the ID that will be used is the App/Site ID generated by the system).  

• Domain: Domain name that will appear in the Sellers.JSON file.

• Seller Type: Can be defined as PUBLISHER, INTERMEDIARY or BOTH:
  PUBLISHER: Indicates that this entity represents direct relationד with a site or app (e.g a site or app that is paid directly by you).

  INTERMEDIARY: Indicates that this entity's inventory is not owned by it (e.g a site or app that is paid via third party that sells you it's inventory: NOT directly by you).

  BOTH: Indicates that this entity sells both types of inventory - direct and third party. 

• Owned and Operated: Check this box if the App/Site is owned by you. 

Part 2 - Ads.txt Setup

• Each entity within the seller.json file should receive a unique ads.txt line for implementation on their relevant sites' ads.txt pages.

• The ads.txt line ID must match the entity ID as it is listed within the sellers.json file.

• The ads.txt line each corresponding publisher/media company would have to implement are as follows:

• **Ads.txt format:
  your company root domain, unique pub's seller ID as listed in the sellers.json file, relationship type, tag ID