A waterfall, frequently referred to as daisy chaining, is a sequential monetization strategy in programmatic advertising where a publisher offers a single ad impression to multiple demand partners one by one. If the first partner in the hierarchy declines the impression, the request is passed to the next until one fills the ad slot or the list is exhausted.
The Mechanics of Waterfall Monetization
In a waterfall configuration, publishers configure their ad server—often a Supply-Side Platform (SSP) or an ad server like Google Ad Manager—to rank demand partners based on historical performance. These partners are ordered from the highest expected yield to the lowest.
When a user visits a webpage, the ad server triggers a request to the first demand partner in the chain. This partner has a fixed amount of time to return a bid. If they choose to fill the impression, the transaction is completed. If they pass, or if their bid is below a set floor price, the request is "passed back" to the ad server, which then initiates a new request to the next partner in the sequence. This process continues until an impression is sold. Because this occurs in real-time, the latency introduced by each sequential "hop" is a critical technical constraint for publishers balancing monetization and User Experience.
Strategic Importance in the Adtech Ecosystem
Historically, the waterfall was the industry standard for managing Programmatic demand. It allowed publishers to prioritize their direct-sold campaigns—often sold at a premium—above programmatic inventory. By placing direct deals at the top of the chain, publishers ensured that their high-value, guaranteed impressions were fulfilled first.
However, as the ecosystem evolved, the limitations of this model became apparent. Because demand sources could not bid against one another simultaneously, the publisher had no way of knowing if a partner further down the chain would have paid more for the same impression than the partner at the top. This led to significant Yield degradation, as the "winning" partner was simply the first to bid above a threshold, rather than the partner willing to pay the highest price.
Challenges and Inefficiencies
The primary critique of the waterfall model is the "opportunity cost" associated with sequential processing. By restricting competition to a series of isolated auctions, publishers inadvertently suppress the true market value of their inventory.
Furthermore, the waterfall model is plagued by technical latency. Each server-to-server request takes time. If a chain is five or six partners long, the time it takes for an ad to render on a page increases, which can negatively affect Viewability metrics and site performance. Additionally, each pass-back event increases the risk of ad delivery errors, where the request drops entirely, leaving the publisher with an "unfilled" impression and zero revenue.
The Shift to Header Bidding
To solve the inefficiencies inherent in the waterfall, the industry shifted toward Header Bidding. Unlike the sequential waterfall, header bidding allows publishers to solicit bids from multiple demand sources simultaneously via a piece of JavaScript code placed in the header of a website.
By enabling all partners to compete in a single, unified auction before the ad server makes a decision, header bidding creates a "flat" auction environment. This transparency ensures that the highest bidder—not just the first bidder—secures the impression. While the waterfall still exists in some legacy setups or for specific Direct-Sold campaigns, the industry has largely transitioned to hybrid models where header bidding provides the bulk of programmatic demand, and the remaining waterfall serves as a secondary mechanism for backfill or specific Private Marketplace deals. Understanding the waterfall is essential for adtech professionals to appreciate the evolution toward open, transparent, and high-yielding auction dynamics.