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.
...
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:
...
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.
...