Enable Index in SpringServe

Publishers can access Index Exchange (Index)'s video demand by enabling Index in SpringServe. Index supports SpringServe's server-side A process where the header bidding takes place on an external server, as opposed to bidding from a browser. This is also called as server-to-server (S2S) header bidding. header bidding Publishers offer their inventory programmatically to multiple ad exchanges before calling their chosen ad server. and client-side A type of header bidding where the auction takes place on the user's browser. header bidding integrations.

Before you begin: You must have a SpringServe UI account. If you do not have an account, contact your SpringServe account manager.

1. Contact Index to begin the integration process and inform us whether you are activating SpringServe’s server-side header bidding or client-side header bidding integration. An Index Representative performs a technical assessment of the integration and verifies if it meets the requirements.

2. After the assessment is complete and approved, Index completes the following:

• Index creates a new account for you. If you are using SpringServe’s client-side header bidding integration and already have an existing client-side Index account, you can request your Index Representative to use this account for the configuration.

• If a new account was created, Index creates a new ads.txt A file that a publisher provides on their site which lists all of the sellers that are authorized to sell their inventory. Ads.txt adheres to the IAB Tech Lab's Authorized Digital Sellers standard that provides transparency into the supply chain, helps prevent domain spoofing, and disallows unauthorized reselling of inventory. and app-ads.txt A file that a publisher provides on their app which lists all of the sellers that are authorized to sell their inventory. App-ads.txt.txt adheres to the IAB Tech Lab's Authorized Digital Sellers standard that provides transparency into the supply chain, helps prevent domain spoofing, and disallows unauthorized reselling of inventory. entry and sends them to you.

• Index creates new SiteIDs according to your requirements and sends them to you.

3. You must add the ads.txt and app-ads.txt entry that you have received from Index as follows:
   • Add the ads.txt entry in the root of the website domain whose inventory you are selling. To learn more about the ads.txt file and format, see the IAB Interactive Advertising Bureau (IAB). An advertising business organization that develops industry standards, conducts research, and provides legal support for the online advertising industry. Tech Lab ads.txt specification.
   • Add the app-ads.txt entry in the root of the domain associated with the app whose inventory you are selling. To learn about the app-ads.txt file and format, see the IAB Tech Lab app-ads.txt specification.

4. In the SpringServe UI, you must add the SiteIDs provided to you by Index. If you have questions about using the SpringServe UI, contact your SpringServe account manager.

5. Index runs a health check to make sure that any discrepancies are minimal and moves your integration to production.