The ad stack is the most sophisticated distributed system most people have never heard of. It processes more transactions per second than most stock exchanges, makes decisions in under 100 milliseconds, and operates across every digital surface. Having worked at every layer — from Google ad server to exchange infrastructure at InMobi — I can give you the architectural overview most explanations miss.
The Publisher Layer
Everything starts with the publisher. The key technology is the ad server — Google Ad Manager dominates for web and app, FreeWheel for CTV and broadcast. The ad server manages inventory, traffics direct campaigns, and coordinates with programmatic demand. At Google, I spent years understanding DFP priority systems determining how demand sources are evaluated. On top sits the header bidding layer — Prebid.js for client-side or Prebid Server for server-side — soliciting parallel bids from multiple SSPs.
The Exchange Layer
SSPs and exchanges sit between publishers and buyers. InMobi Exchange, Magnite, PubMatic, Index Exchange, OpenX, TripleLift, 33Across, Sovrn, and Google AdX each receive bid requests from publishers, translate to OpenRTB, send to DSPs, run auctions, and return winners. Exchanges are not interchangeable pipes — each makes different product decisions materially affecting outcomes. The same impression through two exchanges can yield 30% CPM difference based on demand routing, floor optimization, and signal quality.
The Demand Layer
DSPs enable programmatic buying: The Trade Desk, DV360, Amazon DSP, Xandr, Criteo, MediaMath, StackAdapt. They evaluate bid requests, apply campaign targeting and budget logic, run bid optimization including shading, and submit bids. Supporting infrastructure includes DMPs/CDPs for audience management, verification vendors (IAS, DoubleVerify, MOAT), identity solutions (UID 2.0, LiveRamp, Privacy Sandbox), and measurement platforms (Nielsen, Comscore).
The CTV Stack
CTV has notably different architecture. Ad server is often FreeWheel rather than GAM. Ad insertion can be server-side (SSAI). Format is VAST-based video, not display. Identity relies on device-level IDs rather than cookies. At InMobi, building exchange products for both Web and CTV means maintaining parallel architectures sharing auction logic but differing in delivery, creative management, and measurement.
Why Architecture Matters
Every component is a product decision. Choice of ad server, header bidding config, exchange selection, floor strategy, demand partner mix — each affects revenue, user experience, and monetization health. I have built stacks generating $200M+ revenue. Every dollar started with an architectural choice. Understanding architecture is the foundation of every product decision in digital advertising.
Practical Implications for Builders
Understanding the ad stack at this architectural level is not academic — it is the foundation of every product decision in digital advertising. When I evaluate a new monetization opportunity at InMobi, I trace the full path: how does the ad request originate, what signals does it carry, which exchanges process it, which DSPs evaluate it, and how does the creative render? Each node in this chain is an optimization opportunity. At Glance, I optimized each layer independently and then as a system, compounding improvements that drove the monetization stack to $200M+ in annual revenue. The publishers and exchanges that understand their stack architecturally — rather than treating it as a collection of vendor integrations — consistently outperform those that do not.
For anyone building in adtech, my advice is straightforward: learn every layer. Spend time with the ad server configuration, understand the header bidding wrapper mechanics, study the exchange auction logic, analyze DSP bidding patterns, and trace creative delivery end-to-end. This cross-layer understanding is rare and extraordinarily valuable. It is what I bring from my journey across Google, Automatad, Glance, and InMobi — and it is what I am building into the tools at adsgupta.com.