Back to Bidders
AdHash
Features
| Bidder Code |
adhash |
Prebid.org Member |
no |
| Media Types |
display |
GDPR TCF Support |
yes |
| User IDs |
none |
USP/CCPA Support |
no |
| Supply Chain Support |
no |
COPPA Support |
no |
| Demand Chain Support |
no |
Safeframes OK |
no |
| Supports Deals |
check with bidder |
Prebid.js Adapter |
yes |
| IAB GVL ID |
check with bidder |
Prebid Server Adapter |
no |
| Floors Module Support |
no |
First Party Data Support |
check with bidder |
| Multi Format Support |
check with bidder |
ORTB Blocking Support |
check with bidder |
"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_adhash |
hb_bidder_adhash |
hb_adid_adhash |
hb_size_adhash |
hb_source_adhash |
hb_format_adhash |
hb_cache_host_adhash |
hb_cache_id_adhash |
hb_uuid_adhash |
hb_cache_path_adhash |
hb_deal_adhash |
|
Note
Here is what you need for Prebid integration with AdHash:
- Register with AdHash.
- Once registered and approved, you will receive a Publisher ID and Platform URL.
- Use the Publisher ID and Platform URL as parameters in params.
Please note that a number of AdHash functionalities are not supported in the Prebid.js integration:
- Cookie-less frequency and recency capping;
- Audience segments;
- Price floors and passback tags, as they are not needed in the Preebid.js setup;
- Reservation for direct deals only, as bids are evaluated based on their price.
Bid Params
| Name |
Scope |
Description |
Example |
Type |
publisherId |
required |
Publisher ID |
'0x1234567890123456789012345678901234567890' |
string |
platformURL |
required |
Platform URL |
'https://adhash.org/p/example/' |
string |
Back to Bidders