Back to Bidders

myTarget

Features

Bidder Code mytarget Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display Multi Format Support check with bidder
TCF-EU Support no IAB GVL ID check with bidder
GPP Support check with bidder DSA Support check with bidder
USP/CCPA Support check with bidder 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 check with bidder
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 Type
placementId required The slot ID from myTarget. '379783' string
bidfloor optional Bid floor 10000 number
position optional Ad position on screen. See details below. 1 number
response optional Bid response type. 0 - ad url (default), 1 - ad markup. 1 number

Position

The following values are defined in the ORTB 2.5 spec.

  • 0 : Unknown
  • 1 : Above the Fold
  • 3 : Below the Fold
  • 4 : Header
  • 5 : Footer
  • 6 : Sidebar
  • 7 : Full Screen

Configuration

The myTarget ‘sitename’ could be set globally:

pbjs.setConfig({
   mytarget: {
     sitename: 'example.com'
   }
});

"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_mytarget hb_bidder_mytarget hb_adid_mytarget
hb_size_mytarget hb_source_mytarget hb_format_mytarget
hb_cache_host_mytarg hb_cache_id_mytarget hb_uuid_mytarget
hb_cache_path_mytarg hb_deal_mytarget

Back to Bidders