Page Comparison

...

• Seller Type: Can be defined as PUBLISHER, INTERMEDIARY or BOTH:
  PUBLISHER: Indicates that this entity represents a 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 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 a direct relations 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