Back to Bidders

Kargo

Features

Bidder Code kargo Prebid.org Member yes
Media Types display, video, native GDPR TCF Support yes
User IDs unifiedId USP/CCPA Support yes
Supply Chain Support yes COPPA Support no
Demand Chain Support yes GPP Support no
Supports Deals yes Prebid.js Adapter yes
IAB GVL ID 972 Prebid Server Adapter yes
Floors Module Support yes First Party Data Support no
Multi Format Support will-bid-on-any ORTB Blocking Support check with bidder
Safeframes OK no

"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_kargo hb_bidder_kargo hb_adid_kargo
hb_size_kargo hb_source_kargo hb_format_kargo
hb_cache_host_kargo hb_cache_id_kargo hb_uuid_kargo
hb_cache_path_kargo hb_deal_kargo

Disclosure:

This adapter is known to use an HTTP 1 endpoint. Header bidding often generates multiple requests to the same host and bidders are encouraged to change to HTTP 2 or above to help improve publisher page performance via multiplexing.

Note:

Kargo is an invitation-only marketplace. Please reach out to your Kargo account manager to get setup. Also, you must test on a mobile device, or emulate a mobile device by manipulating the user agent string sent to the server.

Bidder Settings

The Kargo bid adapter uses browser local storage. Since Prebid.js 7.x, the access to it must be explicitly set.

// https://docs.prebid.org/dev-docs/publisher-api-reference/bidderSettings.html
pbjs.bidderSettings = {
  kargo: {
    storageAllowed: true
  }
}

Bid Params:

Name Scope Description Example Type
placementId required The placementId of the ad slot. '_jWuc8Hks' string

Back to Bidders