Back to Bidders

vungle

Features

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

Note

The Vungle Bidding adapter requires setup before beginning. Please contact us at vxssp@liftoff.io.

Bid Params

Name Scope Description Example Type
app_store_id required Vungle App ID of the publisher app, as shown in the Vungle dashboard '5123400' string
placement_reference_id required Placement Reference ID of the Vungle placement '912340000' string

Bidding Token

The adapter does not accept the Vungle SDK bidding token as a bid param. Pass the token generated by the Vungle SDK in user.buyeruid, or per bidder in user.ext.prebid.buyeruids.vungle. Requests without a token do not receive bids.

{
  "user": {
    "ext": {
      "prebid": {
        "buyeruids": {
          "vungle": "<Vungle SDK bidding token>"
        }
      }
    }
  }
}

Rendering

The returned adm is a Vungle SDK envelope, not VAST. Render the winning bid with the Vungle SDK.

"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_vungle hb_bidder_vungle hb_adid_vungle
hb_size_vungle hb_source_vungle hb_format_vungle
hb_cache_host_vungle hb_cache_id_vungle hb_uuid_vungle
hb_cache_path_vungle hb_deal_vungle

Back to Bidders