Back to Bidders

RelevateHealth

Features

Bidder Code relevatehealth 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 usstate_all DSA Support no
USP/CCPA Support yes COPPA Support yes
Supply Chain Support no Demand Chain Support check with bidder
Safeframes OK no Supports Deals yes
Floors Module Support yes First Party Data Support check with bidder
Endpoint Compression check with bidder ORTB Blocking Support no
User IDs none Privacy Sandbox check with bidder

Bid Params

Name Scope Description Example Type
placement_id mandatory Placement Id 110011 number
height optional Height of the creative 600 number
width optional Width of the creative 160 number
domain optional Domain 'domain.com' string
bid_floor optional Bid Floor Price 0.5 decimal

AdUnit Format for Banner

var adUnits = [
            {
                code: 'banner-ad',
                mediaTypes: {
                    banner: {
                        sizes: [[160, 600]]
                    }
                },
                bids: [{
                    bidder: 'relevatehealth',
                    params: {
                        placement_id: 110011,
                        user_id: '',
                        height: 600,
                        width: 160,
                        domain: '',
                        bid_floor: 0.5
                    }
                }]
            }
        ];

First Party Data

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

  • ortb2.user.id
  • ortb2.user.buyeruid
  • ortb2.user.keywords
  • ortb2.user.ext.*

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

pbjs.setConfig({
  ortb2: {
    user: {
      id: 123456789,        // Unique pseudonymized ID for the user (e.g., NPI).
      buyeruid: 987654321,  // DSP-assigned user ID for identity resolution.
      keywords: "kw1,kw2",  // Interest or specialty tags (e.g., oncology, cardiology)
      ext: {
        key1: "values",    // Custom healthcare metadata (e.g., icd10), single or comma seperated.
        key2: "values"     // Additional campaign context (e.g., ndc), single or comma seperated.
      }
    }
  }
});

"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_relevatehealth hb_bidder_relevatehe hb_adid_relevateheal
hb_size_relevateheal hb_source_relevatehe hb_format_relevatehe
hb_cache_host_releva hb_cache_id_relevate hb_uuid_relevateheal
hb_cache_path_releva hb_deal_relevateheal

Back to Bidders