Back to Bidders

Limelight Digital

Features

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

"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_limelightDigit hb_bidder_limelightD hb_adid_limelightDig
hb_size_limelightDig hb_source_limelightD hb_format_limelightD
hb_cache_host_limeli hb_cache_id_limeligh hb_uuid_limelightDig
hb_cache_path_limeli hb_deal_limelightDig

Bid Params

Name Scope Description Example Type
host required Ad network’s RTB host 'exchange.ortb.net' string
adUnitId required Ad Unit Id will be generated on Limelight Digital Platform. 42 integer
adUnitType required Type of Ad Unit ('video', 'banner') 'banner' string
publisherId required Publisher ID '12345' string
custom1 optional Custom targeting field 1 'custom1' string
custom2 optional Custom targeting field 2 'custom2' string
custom3 optional Custom targeting field 3 'custom3' string
custom4 optional Custom targeting field 4 'custom4' string
custom5 optional Custom targeting field 5 'custom5' string

Limelight Digital server-side Prebid Server adapter requires only publisherId and host parameters. But Limelight Digital client-side Prebid.js adapter requires only host, adUnitId, adUnitType.

Limelight Digital server-side Prebid Server adapter supports only banner, video, audio, native media types. But Limelight Digital client-side Prebid.js adapter supports only banner and video media types, doesn’t support audio and native.

Back to Bidders