Back to Bidders

TripleLift

Features

Bidder Code triplelift 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 yes IAB GVL ID 28
GPP Support some (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 yes
Floors Module Support yes First Party Data Support yes
Endpoint Compression check with bidder ORTB Blocking Support check with bidder
User IDs criteo, identityLink, unifiedId, pubCommonId Privacy Sandbox check with bidder
Prebid Server App Support yes

Table of Contents

Overview

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

The Triplelift Prebid Server bidding adapter and user sync endpoint require setup before beginning. Please contact us at prebid@triplelift.com.

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
adUnit.mediaTypes.video.playerSize required Video player dimensions or size in pixels [640, 480] integer array

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.*

Programmatic DMP

Triplelift provides audience and contextual targeting via the integration of a Programmatic DMP tag. Please reach out to your Triplelift representative to discuss specifics of the integration.

Requirements

  • Prebid v7.1.0 or later
  • In Prebid’s bidderSettings, the storageAllowed parameter must be set to true. In Prebid v7.0 and later, storageAllowed defaults to false, so you will need to explicitly set this value to true.

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’.

        pbjs.bidderSettings = {
            triplelift: {
                storageAllowed: true
            }
        }
  • The Programmatic DMP tag must be included at the top of every webpage in order to collect audience and contextual information on the respective page.
  • The Programmatic DMP tag should be as high up in <head> as possible.

"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

Back to Bidders