Back to Bidders



Bidder Code viously Member no
Media Types display, video GDPR TCF Support yes
User IDs none USP/CCPA Support yes
Supply Chain Support no COPPA Support no
Demand Chain Support no GPP Support no
Supports Deals no Prebid.js Adapter yes
IAB GVL ID none Prebid Server Adapter no
Floors Module Support no First Party Data Support no
Multi Format Support will-bid-on-one ORTB Blocking Support no
Safeframes OK yes

"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_viously hb_bidder_viously hb_adid_viously
hb_size_viously hb_source_viously hb_format_viously
hb_cache_host_viousl hb_cache_id_viously hb_uuid_viously
hb_cache_path_viousl hb_deal_viously


Viously Header Bidding adapter requires setup and approval. Please reach out to for more details.

Bid params

Name Scope Description Example Type
pid required Your publisher ID. This information will be given to you by the Viously team. 1234 integer

Video Object

Name Scope Description Example Type
context required The video context, either ‘instream’, ‘outstream’. instream String
playerSize required The size (width, height) of the video player on the page, in pixels. [640, 480] Array<integer>
playbackmethod required Defines how the video inventory is initiated following the OpenRTB spec. [4, 5] Array<integer>


var adUnits = [
        code: 'test-viously',
        mediaTypes: {
            video: {
                playerSize: [640, 360],
                context: 'instream',
                playbackmethod: [1, 2, 3, 4, 5, 6]
        bids: [
                bidder: 'viously',
                params: {
                    pid: '20d30b78-43ec-11ed-b878-0242ac120002'

Back to Bidders