Integrating with Index

The following tables list the integration options that are available with Index Exchange (Index).

Direct integrations

Direct integrations require more technical setup on your side but allow you to have better control over the integration and could help you reduce any potential third party fees. To see the formats that each direct integration type supports, see Formats supported by direct integration options.

Client-side integration options	Description
Prebid.js adapter	Integrate using Prebid.js An open-source library for publishers to implement header bidding on their websites and manage multiple header bidding partners., an open-source library for publishers to implement header bidding Publishers offer their inventory programmatically to multiple ad exchanges before calling their chosen ad server. on their websites and manage multiple header bidding partners.
VAST ad tag	Integrate using a VAST Video ad-serving template (VAST). A communication standard between ad servers and video players in XML-format that describes the video player's expected behavior. ad tag The HTML/JavaScript code that a browser uses to retrieve advertisements from an ad server. to receive video demand from Index for individual non-podded Supply that is monetized with individual video creatives, which is typically short-form video on web or mobile app. The ad displays before (pre-roll), during (mid-roll), or after (post-roll) the video content that the user is viewing. Ads for non-podded video supply are requested through a single ad request. bid requests.
AMP Real Time Config (RTC)	Integrate using AMP Accelerated Mobile Pages (AMP). An open source HTML framework developed by Google. AMP is optimized for mobile web browsing and is intended to help webpages load faster. Index supported formats include standard banner, multi-size, multi-format, and fast fetch/AMPHTML ads. Real Time Config (RTC) to allow Index to receive bid requests and return key-value targeting to the AMP runtime.

Server-side integration options	Description
OpenRTB	Access Index’s omnichannel demand by integrating through a server-to-server OpenRTB An open industry standard for communication between buyers and sellers of online advertising in real-time bidding auctions. It's published by the IAB. connection.

Third-party integrations

When you retrieve demand from Index using a third party, that third party has already integrated with Index so the setup is simplified. An additional third party fee may apply in relation to their services. To see the formats that each third-party integration type supports, see Formats supported by third-party integration options.

Client-side integration options	Description
JW Player	Access outstream An ad placement where the video is not the focal point of the screen and plays with sound-off by default. They can display before, between, or after text, or accompanying streaming content (pre-roll, mid-roll, and post-roll ads), as an interstitial ad, or display as a standalone ad such as slideshows or native feeds. video demand by enabling Index in JW Player.
Vlyby	Access outstream video demand by enabling Index in Vlyby.

Server-side integration options	Description
Amazon TAM	Access banner and video demand by enabling Index in Amazon Transparent Ad Marketplace (TAM).
Google Open Bidding	Access banner and video demand by enabling Index in Google Ad Manager or AdMob.
Prebid Server	Use Prebid Server to retrieve demand from Index and all your other SSPs and exchanges, through one server-to-server parallel bidding integration.
FreeWheel	Access video demand by enabling Index in FreeWheel.
Nimbus	Access banner and video demand by enabling Index in Nimbus.
Publica	Access video demand by enabling Index in Publica.
SpringServe	Access video demand by enabling Index in SpringServe.