Impactify
Features
Bidder Code | impactify | Prebid.org Member | no |
---|---|---|---|
Media Types | display, video | GDPR TCF Support | yes |
User IDs | criteo, id5Id, pubCommonId, unifiedId, uid2, netId | USP/CCPA Support | yes |
Supply Chain Support | yes | COPPA Support | yes |
Demand Chain Support | no | GPP Support | no |
Supports Deals | check with bidder | Prebid.js Adapter | yes |
IAB GVL ID | 606 | Prebid Server Adapter | yes |
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_impactify |
hb_bidder_impactify |
hb_adid_impactify |
hb_size_impactify |
hb_source_impactify |
hb_format_impactify |
hb_cache_host_impact |
hb_cache_id_impactif |
hb_uuid_impactify |
hb_cache_path_impact |
hb_deal_impactify |
Note:
The Impactify adaptator requires setup and validation from the Impactify team. Simply email us your contact details at support@impactify.io and we’ll make sure we’ll connect you within 48h.
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
appId |
required | Impactify publisher id (Contact us) | 'example.com' |
string |
format |
required | Impactify ad format (screen or display) | 'screen' |
string |
style |
required | Impactify ad style (inline, impact or static) | 'impact' |
string |
Configuration
Impactify recommends the UserSync configuration below. Without it, the Impactify adapter will not be able to perform user syncs, which lowers match rate and reduces monetization.
For Prebid.js v1.15.0 and later:
pbjs.setConfig({
userSync: {
filterSettings: {
iframe: {
bidders: '*', // '*' represents all bidders
filter: 'include'
}
}
}
});
For Prebid.js v1.14.0 and before:
pbjs.setConfig({
userSync: {
iframeEnabled: true,
enabledBidders: ['impactify']
}});
Note: Combine the above configuration with any other UserSync configuration. Multiple setConfig() calls overwrite each other and only the last call for a given attribute will take effect.