Back to Bidders

Contxtful

Features

Bidder Code contxtful Prebid.org Member yes
Prebid.js Adapter yes Prebid Server Adapter yes
Media Types display, video Multi Format Support check with bidder
TCF-EU Support no IAB GVL ID check with bidder
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 yes Supports Deals check with bidder
Floors Module Support yes First Party Data Support yes
Endpoint Compression check with bidder ORTB Blocking Support yes
User IDs none Privacy Sandbox check with bidder
Prebid Server App Support no

Note

The Contxtful bidder adapter requires some setup. Contact us at contact@contxtful.com

Bid Params

Name Scope Description Example Type
placementId required The placement identifier 'p12345678' string
customerId required The customer identifier 'DEMO123456' string

Configuration

pbjs.setConfig({
   "contxtful":{
      "version":"v1",
      "customer":"<<CUSTOMER_ID_HERE>>"
   },
   "realTimeData":{
      "dataProviders":[
         {
            "name":"contxtful",
            "waitForIt":true,
            "params":{
               "version":"v1",
               "customer":"<<CUSTOMER_ID_HERE>>",
               "bidders":[
                  "contxtful"
               ],
               "adServerTargeting":true
            }
         }
      ]
   }
}
);

First Party Data

Publishers should use the ortb2 method of setting First Party Data. The following fields are supported:

  • ortb2.site.*
  • ortb2.user.*
  • ortb2.device.*

AdUnit-specific data is supported using AdUnit.ortb2Imp.ext.*

AdUnit Format client side

 var adUnitList = [
  {
    code: 'AD_UNIT_NAME_HERE',
    mediaTypes: { /* "<< ENTER_FORMAT_HERE >> */ },
    bids: [{
      bidder: 'contxtful',
      params: {
        placementId: "<<PLACEMENT_ID_HERE>>",
        customerId: "<<CUSTOMER_ID_HERE>>"
      }
    }],
    ortb2Imp: {
      ext: {
        data: {
          divId: "<<EACH_AD_UNIT_DIV_ID>>"
        }
      }
    }
  }
]

User Sync

Contxtful recommends enabling User Syncing to optimize match rate and monetization.

Prebid note: please review with your legal counsel before enabling storageAllowed. Bidders utilizing browser storage may trigger the need for additional disclosures in your privacy policy and may imply that the bid adapter is performing an activity redundant with user ID systems like SharedID. See the ePrivacy Directive article 5(3) reference to ‘comprehensive information’.

// Enable iframe usersync 
pbjs.setConfig({
  userSync: {
    filterSettings: {
      iframe: {
        bidders: '*',   // '*' means all bidders
        filter: 'include'
      }
    }
  }
});

// Allow local storage usage
pbjs.bidderSettings = {
  contxtful: {
    storageAllowed: true
  }
}

Note - the userSync.filterSettings.all field is mutually exclusive and cannot be combined with the userSync.filterSettings.iframe/userSync.filterSettings.image fields in the userSync config. If the fields are used together, this will be considered an invalid config and only image pixels will be permitted.

"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_contxtful hb_bidder_contxtful hb_adid_contxtful
hb_size_contxtful hb_source_contxtful hb_format_contxtful
hb_cache_host_contxt hb_cache_id_contxtfu hb_uuid_contxtful
hb_cache_path_contxt hb_deal_contxtful

Back to Bidders