Back to Bidders

Peak226

Features

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

Overview

Module Name: Peak226 Bidder Adapter
Module Type: Bidder Adapter
Maintainer: support@edge226.com

Description

The Peak226 adapter connects Prebid Server to the Peak226 SSP (Edge226 Ltd) for banner, video and native demand, on both site and app traffic. It speaks OpenRTB 2.6 and forwards standard signals — first-party data, price floors, user.eids, supply chain (schain), deals (imp.pmp), blocking (bcat, badv, bapp, battr) and consent (TCF EU, US Privacy, GPP, COPPA) — from the incoming request with no extra configuration.

Requests are routed to a per-data-center endpoint (US, EU or JP).

Bid Params

Name Scope Description Example Type
publisherId required Your Peak226 publisher/account ID. 'pub-123' string
placementId required Placement ID for this impression. Sent as imp.tagid. 'plc-456' string
region optional Data center to send the request to: 'us', 'eu' or 'jp'. Defaults to 'us'. 'eu' string

Notes

  • Requests are split per region. region selects a data center, so when the impressions in a single request mix regions the adapter emits one outgoing request per distinct region — each carrying only its own impressions — rather than routing everything to the first impression’s region. Regions are requested in first-seen order, and each region group resolves its own effective publisherId.
  • Multiformat impressions are supported. Banner, video and native may be declared on the same impression; all declared formats are forwarded and Peak226 may bid on any of them. No format is dropped and there is no preferred-format selection.
  • ${AUCTION_PRICE} is expanded by the adapter. Peak226 returns the OpenRTB ${AUCTION_PRICE} macro in adm (and nurl) as its counting mechanism and relies on the demand-side adapter to substitute the clearing price. The adapter resolves it before the bid is returned, so no host configuration is needed.
  • Non-bidder impression signals are preserved. Only the bidder key is removed from imp.ext; signals such as gpid, data and tid are forwarded untouched.
  • Zero-value device.ifa is cleared. When the OS reports the all-zero sentinel IFA (00000000-0000-0000-0000-000000000000, e.g. after an iOS ATT opt-out) the adapter clears it rather than forwarding it as though it were a real device ID.
  • No cookie sync. The adapter does not declare a userSync endpoint. GVL 1202 is registered as “Edge226 Ltd” but declares usesCookies: false and does not include Purpose 1 (“store and/or access information on a device”), so a TCF-compliant CMP has no basis to authorize a cookie drop. Bidding is unaffected — Purpose 2 (basic ads) is declared.
  • Bid floors in a currency other than USD are converted before the request is sent.

"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_peak226 hb_bidder_peak226 hb_adid_peak226
hb_size_peak226 hb_source_peak226 hb_format_peak226
hb_cache_host_peak22 hb_cache_id_peak226 hb_uuid_peak226
hb_cache_path_peak22 hb_deal_peak226

Back to Bidders