Back to Bidders

Zeta Global

Features

Bidder Code zeta_global Prebid.org Member no
Media Types display GDPR TCF Support yes
User IDs none USP/CCPA Support no
Supply Chain Support no COPPA Support no
Demand Chain Support no Safeframes OK check with bidder
Supports Deals no Prebid.js Adapter yes
IAB GVL ID 469 Prebid Server Adapter no
Floors Module Support no

"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_zeta_global hb_bidder_zeta_globa hb_adid_zeta_global
hb_size_zeta_global hb_source_zeta_globa hb_format_zeta_globa
hb_cache_host_zeta_g hb_cache_id_zeta_glo hb_uuid_zeta_global
hb_cache_path_zeta_g hb_deal_zeta_global

Registration

All references to the OpenRTB spec refer to OpenRtb v2.5 (https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf)

To use this bidder you will need a valid definerId. For further information, please contact jzirbel@disqus.com.

Bid Params

Name Scope Description Example Type
user required The object containing user data (See OpenRTB spec) user: {} object
user.buyeruid required Zeta’s user id "12345" string
device required The object containing device data (See OpenRTB spec) device: {} object
device.ip required The client IP "0.0.0.0" string
device.geo required The object containing geo data (See OpenRTB spec) geo: {} object
device.geo.country required The country code pertinent to the request data "USA" string
definerId required The Definer ID from Zeta Global "12345" string
site optional The object containing site data (See OpenRTB spec) site: {} object
app optional The object containing app data (See OpenRTB spec) app: {} object
test optional Flag which will induce a sample bid response when true; only set to true for testing purposes (1 = true, 0 = false) 1 integer

Back to Bidders