In-app header bidding

What is In-app header bidding?

In-app header bidding is a programmatic advertising technique that allows multiple demand sources to simultaneously bid on a single ad impression within a mobile app, in real time. Unlike sequential waterfall auctions, every participating buyer receives equal access to each impression and the highest bid wins. In-app header bidding maximizes publisher revenue by increasing competition and ensuring no bid is bypassed in favor of a lower one submitted earlier.

How it works

When a user loads a page inside an app that contains an ad slot, in-app header bidding triggers a simultaneous auction across all connected demand sources. This process completes within milliseconds, before the page finishes rendering, so the winning ad creative appears seamlessly to the user.

The Auction Process

The app SDK or mediation layer sends a bid request to all integrated supply-side platforms (SSPs) at the same moment. Each SSP then notifies its connected demand-side platforms (DSPs) and ad networks, which respond with bids. All bids are collected and evaluated together, and the highest bid wins the impression. The winning ad creative is then served into the ad slot.

In-App Header Bidding vs. Waterfall Auctions

The waterfall method passes an impression to ad networks one at a time, in a predefined priority order, until one meets the publisher's price floor. This means a lower-priority network offering a higher bid is never even consulted if an earlier network accepts. In-app header bidding eliminates this inefficiency entirely. All demand sources compete simultaneously regardless of rank, so the highest-value bid always wins. Publishers are no longer constrained by static price floors or fixed network hierarchies, and advertisers previously locked out of premium inventory gain the opportunity to compete on equal footing.

Technical Implementation

In-app header bidding is typically implemented through a mediation SDK integrated into the app. The SDK coordinates communication between the app, the publisher's ad server, and the various SSPs and DSPs participating in the auction. Some implementations use a server-side architecture where the auction logic runs on an external server rather than the device, reducing latency and battery consumption on the user's device.

Why it matters

In-app header bidding meaningfully improves outcomes for both publishers and advertisers. Publishers gain access to a broader pool of demand, which drives up competition for each impression and increases effective CPMs compared to waterfall setups where many high-value bids are never reached. Advertisers and ad networks that were previously assigned low priority in waterfall hierarchies gain fair access to premium inventory they could not reach before, improving campaign reach and targeting efficiency.

For app publishers specifically, replacing or supplementing waterfall auctions with header bidding can significantly raise fill rates and revenue per impression. The unified auction model also simplifies yield management, since publishers no longer need to manually tune the priority order of ad networks. As programmatic advertising matures in mobile, in-app header bidding has become a standard expectation for publishers running high-volume ad monetization strategies.

How to implement in-app header bidding

1. Choose a mediation platform that supports header bidding. Select an ad mediation platform or SDK that natively supports simultaneous auctions. Confirm it integrates with the SSPs and DSPs relevant to your audience and geography.

2. Integrate the mediation SDK into your app. Follow the platform's integration documentation to embed the SDK. Ensure the SDK is initialized early in the app lifecycle so it is ready when the first ad slot loads.

3. Connect demand sources. Add the SSPs and ad networks you want to compete in your auctions. Each demand source typically requires its own adapter or SDK module alongside the mediation layer.

4. Configure price floors. Set minimum bid thresholds to ensure impressions are not filled below acceptable revenue levels. Price floors protect inventory value while still allowing competition above the minimum.

5. Test auction behavior. Use test modes provided by the mediation platform to verify that all demand sources are receiving bid requests simultaneously and that the highest bid is winning each auction correctly.

6. Monitor eCPM and fill rate. After launch, track effective CPM and fill rate by demand source. Use this data to identify underperforming partners, adjust price floors, or add new demand sources to increase competition.

7. Consider server-side bidding for performance-sensitive apps. If device-side auction processing introduces latency or affects user experience, evaluate a server-side header bidding setup where auction logic runs off-device. Airbridge attribution integrations can help connect in-app ad revenue data to downstream campaign performance reporting.

Related concepts