Back to Bidders

Invibes

Features

Bidder Code invibes Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter yes
Media Types display, native Multi Format Support will-bid-on-any
TCF-EU Support yes IAB GVL ID 436
GPP Support tcfeu DSA Support check with bidder
USP/CCPA Support no COPPA Support no
Supply Chain Support no Demand Chain Support no
Safeframes OK no Supports Deals no
Floors Module Support no First Party Data Support no
User IDs none ORTB Blocking Support no
Privacy Sandbox check with bidder Prebid Server App Support no

Disclosure

The bidder will use the Local Storage if allowed by the publisher and user gives consent on page with the following purposes: - set an internal Invibes ID - get the internal Invibes ID if it was set priorly for the user

The bidder will NOT set any cookies. The bidder will also try to read from Cookies if publisher gibes the internal ID if this wasn’t found in LocalStorage.

Bid Params

Name Scope Description Example Type
placementId required The Invibes placement ID '1234567' string
domainId optional Id of domain 1001 integer
customEndpoint optional Custom test domain https://bid.videostep.com/Bid/VideoAdContent integer
debug optional Debug paramentes (only prebid server) { "testBvid": "1234", "testLog": true } object

"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_invibes hb_bidder_invibes hb_adid_invibes
hb_size_invibes hb_source_invibes hb_format_invibes
hb_cache_host_invibe hb_cache_id_invibes hb_uuid_invibes
hb_cache_path_invibe hb_deal_invibes

Back to Bidders