Back to Bidders

AP Stream


Bidder Code apstream Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display Multi Format Support check with bidder
TCF-EU Support no IAB GVL ID 394
GPP Support check with bidder DSA Support check with bidder
USP/CCPA Support check with bidder COPPA Support check with bidder
Supply Chain Support check with bidder Demand Chain Support check with bidder
Safeframes OK check with bidder Supports Deals check with bidder
Floors Module Support check with bidder First Party Data Support check with bidder
User IDs none ORTB Blocking Support check with bidder
Privacy Sandbox check with bidder


Note: This bidder passes consent strings but not the gdprApplies flag to its backend. 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

Bid Params

Name Scope Description Example type
publisherId optional* Publisher Id will be generated on AP Stream. ‘1234’ string
code optional Ad code ‘S1_Leaderboard’ string
adunitId optional Ad unit Id 1234 integer
endpoint optional Endpoint for custom bidder ‘’ string
test optional* Use test endpoint true boolean
sendDsu optional Send DSU to bidder (default true) false boolean

* see description below


Bidder config

Here parameters test and publisherId can be set globally, but will be overrided if set in specific bid.

    bidders: ["apstream"],
    config: {
        appstream: {
            publisherId: '1234
            test: true

"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_apstream hb_bidder_apstream hb_adid_apstream
hb_size_apstream hb_source_apstream hb_format_apstream
hb_cache_host_apstre hb_cache_id_apstream hb_uuid_apstream
hb_cache_path_apstre hb_deal_apstream

Back to Bidders