Back to Bidders
Engageya
Features
Bidder Code |
engageya |
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 |
GPP Support |
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 |
Safeframes OK |
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_engageya |
hb_bidder_engageya |
hb_adid_engageya |
hb_size_engageya |
hb_source_engageya |
hb_format_engageya |
hb_cache_host_engage |
hb_cache_id_engageya |
hb_uuid_engageya |
hb_cache_path_engage |
hb_deal_engageya |
|
Disclosure
Note: This bidder appears to only consider gdprApplies if a consent string is available. This may result in some incorrect TCF2 processing, such as when the consent string is not yet available but the publisher has decided GDPR always applies. See https://github.com/prebid/Prebid.js/issues/7775
Bid params
Name |
Scope |
Description |
Example |
Type |
widgetId |
required |
Widget ID, provided by Engageya. |
85610 |
integer |
websiteId |
required |
Website ID, provided by Engageya. |
91140 |
integer |
pageUrl |
optional |
Pass current user URL. |
'https://engageya.com' |
String |
Back to Bidders