Back to Bidders

Adlivetech

Features

Bidder Code adlivetech 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 no
Floors Module Support yes First Party Data Support yes
Multi Format Support check with bidder ORTB Blocking Support check with bidder
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_adlivetech hb_bidder_adlivetech hb_adid_adlivetech
hb_size_adlivetech hb_source_adlivetech hb_format_adlivetech
hb_cache_host_adlive hb_cache_id_adlivete hb_uuid_adlivetech
hb_cache_path_adlive hb_deal_adlivetech

Table of Contents

Bid Params

Name Scope Description Example Type
uid required Represents the Adlivetech bidder system Ad Slot ID associated with the respective div id from the site page. 1 integer
keywords optional A set of key-value pairs applied to all ad slots on the page. Values can be empty. keywords: { topic: ['stress', 'fear'] } object
bidFloor optional Floor of the impression opportunity. If present in the request overrides XML info. 0.8 float

Bidder Config

You can allow writing in localStorage pbjs.setBidderConfig for the bidder adlivetech

pbjs.setBidderConfig({
    bidders: ["adlivetech"],
    config: {
        localStorageWriteAllowed: true
    }
})

If it will be “true” this allow Adlivetech Bid Adapter to write userId in first party localStorage

First Party Data

Publishers should use the ortb2 method of setting First Party Data.

Global site or user data using setConfig(), or Bidder-specific using setBidderConfig() supports following fields:

  • ortb2.user.data[]: Standard IAB segment taxonomy user data
  • ortb2.user.ext.device: Non standard arbitrary user device
  • ortb2.user.keywords: Standard IAB OpenRTB 2.5 user.keywords field. It will be included in ext.keywords.user.ortb2
  • ortb2.site.keywords: Standard IAB OpenRTB 2.5 site.keywords field. It will be included in ext.keywords.site.ortb2
  • ortb2.site.cat[]: Standard IAB OpenRTB 2.5 site.cat field. It will be sent as part of site.cat array
  • ortb2.site.pagecat[]: Standard IAB OpenRTB 2.5 site.pagecat field. It will be sent as part of site.cat array
  • ortb2.site.content.genre: Standard IAB OpenRTB 2.5 site.content.genre field

AdUnit-specific data using AdUnit.ortb2Imp supports following fields:

  • ortb2.imp[].ext.data.*
  • ortb2.imp[].instl

Back to Bidders