Back to Bidders

myTarget

Features

Bidder Code mytarget Prebid.org Member no
Media Types display GDPR TCF Support no
User IDs none USP/CCPA Support no
Supply Chain Support no COPPA Support no
Demand Chain Support no Safeframes OK check with bidder
Supports Deals check with bidder Prebid.js Adapter yes
IAB GVL ID check with bidder Prebid Server Adapter no
Floors Module Support no

"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

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'
   }
});

Back to Bidders