Back to Bidders

Sortable

Features

Bidder Code sortable Prebid.org Member yes
Media Types display, video, native GDPR TCF Support yes
User IDs none USP/CCPA Support yes
Supply Chain Support yes COPPA Support no
Demand Chain Support no Safeframes OK check with bidder
Supports Deals check with bidder Prebid.js Adapter yes
IAB GVL ID 145 Prebid Server Adapter no
Floors Module Support 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_sortable hb_bidder_sortable hb_adid_sortable
hb_size_sortable hb_source_sortable hb_format_sortable
hb_cache_host_sortab hb_cache_id_sortable hb_uuid_sortable
hb_cache_path_sortab hb_deal_sortable

Table of Contents

Bid params

Name Scope Description Example
tagId required The tag ID from Sortable. "test-pb-leaderboard"
siteId optional Override the global Sortable site ID, see here. Please reach out to your Sortable Account Manager for more details. "example.com"
floor optional The minumum CPM (in USD) requred to participate 0.25
keywords optional Publisher-defined key-value string pairs { "key1": "val1", "key2": "val2" }

Sortable supports the banner features described in:

Configuration

The Sortable site ID should be set globally in order to improve user sync. How to do so:

pbjs.setConfig({
   sortable: {
     siteId: "example.com"
   }
});

The Sortable adapter has the ability to initiate user-sync requests that will improve DSP user ID match rate, with the aim of generating higher bid prices. By default, Sortable sync requests are off. Setting the Sortable site ID globally as described above is required for user-sync requests.

pbjs.setConfig({
   userSync: {
    enabledBidders: ['sortable'],
    iframeEnabled: true
 }});

Note: these configs should be combined with any other UserSync config calls, as subsequent calls to setConfig for the same attribute overwrite each other.

Back to Bidders