Back to Bidders

TripleLift

Features

Bidder Code triplelift Prebid.org Member yes
Media Types display, video GDPR TCF Support yes
User IDs criteo, identityLink, unifiedId, pubCommonId USP/CCPA Support yes
Supply Chain Support yes COPPA Support yes
Demand Chain Support no GPP Support no
Supports Deals yes Prebid.js Adapter yes
IAB GVL ID 28 Prebid Server Adapter yes
Floors Module Support yes First Party Data Support yes
Multi Format Support check with bidder ORTB Blocking Support check with bidder
Safeframes OK yes

"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_triplelift hb_bidder_triplelift hb_adid_triplelift
hb_size_triplelift hb_source_triplelift hb_format_triplelift
hb_cache_host_triple hb_cache_id_tripleli hb_uuid_triplelift
hb_cache_path_triple hb_deal_triplelift

Table of Contents

Overview

Publishers may integrate with Triplelift through our Prebid.js and/or Prebid Server adapters. See below for more information.

Bid Params

Name Scope Description Example Type
inventoryCode required TripleLift inventory code for this ad unit (provided to you by your partner manager) 'pubname_top_banner' string
floor optional Bid floor 1.00 float

Video

Triplelift bid params for video mediaTypes are identical, but be sure to include the appropriate video.placement value to indicate instream/outstream format. Speak with your partner manager about which value to place here based on what formats are enabled.

See the Ad Unit Reference for more info.

Name Scope Description Example Type
adUnit.mediaTypes.video.placement required Instream: 1; Outstream: 3, 4, 5. 3 int

Example Configuration

var adUnits = [
    {
        code: 'top-banner',
        mediaTypes: {
            banner: {
                sizes: [
                    [728, 90],
                    [970, 250]
                ]
            }
    },
    bids: [{
        bidder: 'triplelift',
        params: {
            inventoryCode: 'pubname_top_banner'
        }
    }]
}];

Video (Instream)

var videoAdUnit = {
    code: 'video1',
    mediaTypes: {
        video: {
            playerSize: [640, 480],
            context: 'instream',
            placement: 1,
            mimes: ['video/mp4']
        }
    },
    bids: [{
        bidder: 'triplelift',
        params: {
            inventoryCode: 'pubname_instream1'
        }
    }]
};

Video (Outstream)

var videoAdUnit = {
    code: 'video1',
    mediaTypes: {
        video: {
            playerSize: [640, 480],
            context: 'outstream',
            placement: 3,
            mimes: ['video/mp4']
        }
    },
    bids: [{
        bidder: 'triplelift',
        params: {
            inventoryCode: 'pubname_outstream',
        }
    }]
};

First Party Data

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

  • ortb2.site.*: Standard IAB OpenRTB 2.5 site fields
  • ortb2.user.*: Standard IAB OpenRTB 2.5 user fields

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

Back to Bidders