Back to Bidders

Optidigital

Features

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

Bid Params

Name Scope Description Example Type
publisherId required Unique id of the publisher 'p1234' string
placementId required Identifier for specific ad placement or ad tag 'Billboard_Top' string
divId optional Id of the div containing the ad slot 'Billboard_Top_3c5425' string
pageTemplate optional Page template name of the current page 'home' string
badv optional Blocked advertiser domains ['example.com'] array of strings
bcat optional Blocked advertiser categories ['IAB1-1', 'IAB1-2'] array of strings
bapp optional Blocked advertiser mobile app bundles ['com.blocked'] array of strings
battr optional Blocked creative attributes [1, 2] array of integers

Note

The Optidigital Bidding adapter requires setup before beginning. Please contact us at prebid@optidigital.com. The following test parameters can be used to verify that the Optidigital adapter is working properly. This example includes an test publisherId and placementId that would return the test creative.

AdUnits configuration example

    var adUnits = [{
      code: 'your-slot_1-div', // use exactly the same code as your slot div id.
      mediaTypes: {
        banner: {
            sizes: [[300,600]]
        }
      },
      bids: [{
          bidder: 'optidigital',
          params: {
            publisherId: 'test',
            placementId: 'Billboard_Top',
            divId: 'Billboard_Top_3c5425', // optional parameter
            pageTemplate: 'home', // optional parameter
            badv: ['example.com'], // optional parameter
            bcat: ['IAB1-1', 'IAB1-2'], // optional parameter
            bapp: ['com.blocked'], // optional parameter 
            battr: [1, 2] // optional parameter 
          }
      }]
    }];

UserSync example

To optimize UserSync functionality and ensure optimal match rates and monetization with the Optidigital adapter, we strongly advise implementing the UserSync configuration through iFrame as provided below. Failure to do so may result in reduced match rates and monetization capabilities.

pbjs.setConfig({
  userSync: {
    filterSettings: {
      iframe: {
        bidders: '*', // '*' represents all bidders
        filter: 'include'
      }
    }
  }
});

Note: be aware that when using this configuration, you can combine it with other UserSync configurations as needed. Keep in mind that if you make multiple setConfig() calls, the last one for a specific attribute will take precedence and overwrite any previous configurations.

"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_optidigital hb_bidder_optidigita hb_adid_optidigital
hb_size_optidigital hb_source_optidigita hb_format_optidigita
hb_cache_host_optidi hb_cache_id_optidigi hb_uuid_optidigital
hb_cache_path_optidi hb_deal_optidigital

Back to Bidders