Platform & Technology

How Header Bidding Works

Header bidding runs a simultaneous open auction across all demand partners before GAM is called, ensuring every buyer competes fairly rather than getting structural last-look.

Our Tech Stack

hb.js, Prebid.js v11.4.0, GPT, Google Ad Manager, AdX dynamic allocation, Bunny edge ingest, and a Node.js real-time server — every layer of the Advlume stack explained.

How Ads Are Served

The complete impression lifecycle: slot discovery, viewport filtering, traffic quality gate, Prebid auction, lazy load trigger, creative render, viewability measurement, and smart refresh.

Consent Management (CMP)

How Advlume collects and forwards GDPR/TCF, GPP, and CCPA consent signals using the InMobi Choice CMP — and what that means for you as a publisher.

Supply Chain Transparency (sellers.json & schain)

How Advlume implements sellers.json, ads.txt, and the OpenRTB SupplyChain object (schain) to give DSPs verified transparency over every impression in the chain.

Lazy Loading & Smart Refresh

How Advlume lazily loads below-the-fold slots using an 800px IntersectionObserver margin, and refreshes ads every 30 seconds of viewability up to 10 times per session.

User ID Modules

The three Prebid user ID modules active on every Advlume impression — Shared ID, ID5 Universal ID, and a first-party UUID — and how they lift CPMs in cookieless environments.