Back to Bidders

TrustX

Features

Bidder Code trustx Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter yes
Media Types display, video Multi Format Support will-bid-on-any
TCF-EU Support yes IAB GVL ID 686 (grid)
GPP Support check with bidder DSA Support check with bidder
USP/CCPA Support yes COPPA Support yes
Supply Chain Support yes Demand Chain Support check with bidder
Safeframes OK check with bidder Supports Deals check with bidder
Floors Module Support yes First Party Data Support yes
User IDs all ORTB Blocking Support check with bidder
Privacy Sandbox check with bidder Prebid Server App Support check with bidder

Table of Contents

Bid Params

Name Scope Description Example Type
uid required Represents the TrustX bidder system Ad Slot ID associated with the respective div id from the site page. 42 integer
keywords optional A set of key-value pairs applied to all ad slots on the page. Values can be empty. keywords: { topic: ['stress', 'fear'] } object
bidFloor optional Floor of the impression opportunity. If present in the request overrides XML info. 0.8 float

Parameter keywords must have following format:

{
   "site":{
      "publisher1":[
         {
            "name":"SomeKeywordsBlockName",
            "segment1Name":[
               "segment2Value"
            ],
            "segment2Name":[
               "segment2Value1",
               "segment2Value2",
               ...
            ],
            ...
         }
      ],
      ...
   }
}

Bidder Config

You can allow writing in localStorage pbjs.setBidderConfig for the bidder trustx

pbjs.setBidderConfig({
    bidders: ["trustx"],
    config: {
        localStorageWriteAllowed: true
    }
})

If it will be “true” this allow TheMediaGrid Bid Adapter to write userId in first party localStorage

If you want to make alias on TrustX Bid Adapter, you must set forceBidderName in bidderConfig as "trustx".

pbjs.setBidderConfig({
    bidders: ["aliasName"],
    config: {
        forceBidderName: 'trustx'
    }
})

First Party Data

Publishers should use the ortb2 method of setting First Party Data.

Global site or user data using setConfig(), or Bidder-specific using setBidderConfig() supports following fields:

  • ortb2.user.data[]: Standard IAB segment taxonomy user data
  • ortb2.user.ext.device: Non standard arbitrary user device
  • ortb2.user.keywords: Standard IAB OpenRTB 2.5 user.keywords field. It will be included in ext.keywords.user.ortb2
  • ortb2.site.keywords: Standard IAB OpenRTB 2.5 site.keywords field. It will be included in ext.keywords.site.ortb2
  • ortb2.site.cat[]: Standard IAB OpenRTB 2.5 site.cat field. It will be sent as part of site.cat array
  • ortb2.site.pagecat[]: Standard IAB OpenRTB 2.5 site.pagecat field. It will be sent as part of site.cat array
  • ortb2.site.content.genre: Standard IAB OpenRTB 2.5 site.content.genre field

AdUnit-specific data using AdUnit.ortb2Imp supports following fields:

  • ortb2.imp[].ext.data.*
  • ortb2.imp[].instl

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_trustx hb_bidder_trustx hb_adid_trustx
hb_size_trustx hb_source_trustx hb_format_trustx
hb_cache_host_trustx hb_cache_id_trustx hb_uuid_trustx
hb_cache_path_trustx hb_deal_trustx

Back to Bidders