Back to Bidders

Etarget

Features

Bidder Code etarget Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display, video Multi Format Support check with bidder
TCF-EU Support yes IAB GVL ID 29
GPP Support check with bidder DSA Support check with bidder
USP/CCPA Support yes COPPA Support check with bidder
Supply Chain Support check with bidder Demand Chain Support check with bidder
Safeframes OK check with bidder Supports Deals check with bidder
Floors Module Support check with bidder First Party Data Support yes
Endpoint Compression check with bidder ORTB Blocking Support check with bidder
User IDs none Privacy Sandbox check with bidder

Bid Params

Name Scope Description Example
refid required Placement ID 12345
country required Country domain 1
options optional Additional data {site:'example.com'}

First Party Data

In release 5.0 and later, publishers should use the ortb2 method of setting First Party Data. The following fields are supported:

  • ortb2.site.ext.data.*
  • ortb2.site.keywords
  • ortb2.site.content.data[]
  • ortb2.user.ext.data.*
  • ortb2.user.data[]

The ETARGET exchange supports the IAB standard Audience Taxonomy v1.1 and Content Taxonomy v2.2.

Example first party data that’s available to all bidders and all adunits:

pbjs.setConfig({
  ortb2: {
    site: {
      keywords: "kw1,kw2",            
      ext: {
        data: {
           prodtype: ["tech","mobile"] 
        }
      }
    },
    user: {
      ext: {
        data: {
          ucat:["new"]                 
        }
      }
    }
  }
};

Example of first party data available only to the ETARGET bidder. Applies across all ad units.

pbjs.setBidderConfig({
  bidders: ["etarget"],
  config: {
    ortb2: {
      site: {
        keywords: "kw1,kw2",             
        ext: {
          data: {
            prodtype: ["tech","mobile"]  
          }
        }
      },
      user: {
        ext: {
          data: {
            ucat:["new"]                 
          }
        }
      }
    }
  }
};

"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_etarget hb_bidder_etarget hb_adid_etarget
hb_size_etarget hb_source_etarget hb_format_etarget
hb_cache_host_etarge hb_cache_id_etarget hb_uuid_etarget
hb_cache_path_etarge hb_deal_etarget

Back to Bidders