Back to Bidders

Bidtheatre

Features

Bidder Code bidtheatre Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display, video Multi Format Support will-bid-on-any
TCF-EU Support yes IAB GVL ID 30
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 yes Supports Deals yes
Floors Module Support yes First Party Data Support yes
User IDs none ORTB Blocking Support partial
Privacy Sandbox topics

Registration

The Bidtheatre bidding adapter requires manual set up before use. Please contact us at operations@bidtheatre.com if you would like to access Bidtheatre’s demand.

Bid Params

Name Scope Description Example Type
publisherId required Manually set up publisher ID '73b20b3a-12a0-4869-b54e-8d42b55786ee' string

In addition to the required bid param above, Bidtheatre will also enforce the following requirements

  • All ad slots on a page must belong to the same publisher ID
  • The publisher must provide either a client IP and/or explicit geo data in the request

First Party Data

Publishers should use the ortb2 method of setting First Party Data. All standard OpenRTB 2.5 properties are supported, including but not limited to

  • ortb2.site.*
  • ortb2.user.*

ORTB Blocking

bcat, badv and battr are all supported.

Media Types

All standard OpenRTB 2.5 properties are supported for both banner and video. Bidtheatre Bidding adapter will always return VAST 2.0 or lower for video requests.

"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_bidtheatre hb_bidder_bidtheatre hb_adid_bidtheatre
hb_size_bidtheatre hb_source_bidtheatre hb_format_bidtheatre
hb_cache_host_bidthe hb_cache_id_bidtheat hb_uuid_bidtheatre
hb_cache_path_bidthe hb_deal_bidtheatre

Back to Bidders