01
Bidder alias and adapter selection
Each bidder has a Prebid adapter; some have multiple variants. The adapter version, alias configuration, and bidder-side endpoint URL all affect bid response quality.
Prebid.js is the open-source backbone of header bidding. Implementing it well is the difference between revenue lift and revenue drag.
Prebid yield depends on bidder selection, timeout discipline, price granularity, and GAM key-value alignment. Each one is a tuning choice.
Pub Clarity implements Prebid as engineering. Each choice is tested, documented, and reversible.
Prebid.js is the open-source JavaScript header bidding wrapper used by the majority of header-bidding-active publishers globally. It is not a demand source — it is the framework that runs the parallel auction across whatever demand sources the publisher has configured. The framework is mature, well-documented, and widely adopted; the implementations are usually where things go wrong.
Most Prebid implementations are pasted, not engineered. A publisher inherits a configuration from a previous developer, copies it from a template, or borrows it from a peer site without auditing the choices. The result is bidders that do not respond inside the timeout window, key-values that do not align with GAM line items, and price granularity that wastes both inventory and demand spend.
Pub Clarity implements Prebid as engineering. Every configuration choice is tested against observed bid behaviour. Every change is reversible. Every decision is documented in a publisher-facing config audit trail.
The settings that separate a Prebid setup that performs from one that quietly leaks revenue.
Each bidder has a Prebid adapter; some have multiple variants. The adapter version, alias configuration, and bidder-side endpoint URL all affect bid response quality.
pbjs.requestBids timeout is the global window. Per-bidder timeout overrides handle slow bidders without penalizing fast ones. The default 1500ms is rarely optimal for any specific publisher.
The price bucket configuration in Prebid must align with the line item structure in GAM. A 5-cent bucket in Prebid against $0.10 GAM granularity wastes half the demand.
UserSync registration delays cost identity-driven revenue. Consent gating must run before any UserSync fires. The order of operations matters more than most setups acknowledge.
pbjs.setTargetingForGPTAsync sets the targeting keys GAM reads. The key names, the format (string vs number), and the granularity all must match the GAM line item targeting.
Floor management in Prebid can be static (per-slot) or dynamic (priceFloors module). Dynamic floors are more powerful but require accurate floor data; static is the conservative choice for new publishers.
Bidder-side analytics adapters capture bid-level detail that GAM does not. Pub Clarity uses these for reconciliation; the data is also valuable for the publisher's own audit.
What publishers ask about Prebid configuration and operation.
Yes. We audit, document, and migrate the existing configuration to the Pub Clarity managed setup. Your bidders, your contracts, your relationships — we manage the operational layer.
Yes. The bidder contract is the publisher's. Pub Clarity is the operations layer; we do not insert ourselves between the publisher and the bidder.
currency, consentManagement, priceFloors (optional), userId modules (per identity provider), analytics adapter per bidder. The exact module set depends on the publisher's demand stack.
Prebid releases new major versions roughly twice a year. We track changes, test in staging, and migrate publishers on a quarterly cadence. The publisher does not need to coordinate the upgrade.
Yes. Standard Prebid debug controls (pbjs.getEvents, pbjs.getBidResponses) work in your browser DevTools. Pub Clarity's Real-Time dashboard surfaces a structured view of the same data.
Server-side header bidding is on the Pub Clarity roadmap for Q3. For now, all configurations run client-side via Prebid.js with full identity and consent handling.
Apply or request a consultation with the operations team.
Apply as a publisher →