Sellers.JSON Set Up

Part 1 - Platform Set Up

Step 1: General Account settings:

1.1. Go to Account Settings:

1.2. Select your Network name as an instance:

1.3. Under your instance, select the Sellers.JSON section and configure the following fields:

• 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.1. Under Supply >> Publishers, select the relevant Publisher you want to edit (or create a new one):

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:

b.1. Under Supply >> App/Site, select the relevant App/Site you want to edit (or create a new one):

b.2. In the App/Site configuration screen, fill out the following fields:

• 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