Supply Partners


The TripleLift Server to Server integration is compliant with OpenRTB 2.5. This defines the structure for bid (combination of price, identifier, assets, etc.) request format and bid response format. This documentation will highlight items required by our Server to Server integration. If you are a publisher or supply partner and you would like to connect with Triplelift, there are a few things that we either require or highly recommend.


The Server to Server integration is initiated by a bid request from the client's server to the following endpoint. TL will provide a supplier_id, which will be appended as a query string parameter in bid requests.

Note that our TLX endpoint is already geo-load balanced to the following Data Centers. Using different, region-specific endpoints is not advised as the load-balanced endpoint will direct traffic accordingly and provides failover in the event a region is down.


RegionLocationAWS Region
US EastNorthern Virginiaus-east-1
US WestNorthern Californiaus-west-1
Asia SouthSingaporeap-southeast-1

For more details on structuring the bid request, please see BidRequest Object.

Setting up Placements

During supply partner onboarding, you can work directly with a member of our Publisher Client Services Team in order to review an optimal inventory breakdown.

Setting up Usersync

In order to successfully implement user syncing with Triplelift, the following steps are required:

  1. You provide Triplelift with your user sync redirect domain.
  2. Triplelift adds your sync domain to a sync domain allowlist that is maintained internally.
  3. Triplelift provides you with user sync pixel to drop on your page.

Typically, the supply partner will be responsible for hosting a user match table. The Triplelift user ID (tluid) that is sent back to you during the sync process will need to be set in the user.buyeruid section of the bid request object.

For more details regarding setting user IDs in the bid request, please see [User Object](OpenRTB 2.5).
For more details regarding endpoints, please see Usersync.

Impression Counting Methodologies

Industry standard dictates that in-app impressions must be counted only once 1px of the ad is in view (1px-in-view). For S2S integrations, please inform the integration team what is required (ex., ORTB customizations) from TL in order to abide by this standard. Failure to use this counting methodology in-app will often/eventually result in Buyers blocking the supply.

Web display impressions remain to be counted on render.

Video impressions are counted on video start.