Header bidding revolutionized programmatic advertising by allowing publishers to offer their inventory to multiple demand sources simultaneously. Yet in our audits of hundreds of Indian publisher websites, we consistently find the same five mistakes, each one silently draining revenue.
1. Running an Outdated Prebid.js Version
This is the most common issue we see. Many Indian publishers are still running Prebid.js versions from 2023 or earlier, missing out on critical performance improvements, new adapter support, and security patches. In our April 2026 audit data, we found publishers running versions as old as v7.x when the current stable release is well past v10.x.
The fix: Update to the latest stable Prebid.js version. Each major version brings measurable CPM improvements (typically 5-15%) through better auction mechanics and adapter optimizations. Set a quarterly calendar reminder to check for updates.
2. Too Few Bidders Configured
Competition drives up CPMs. We regularly see publishers with only 2-3 bidders configured when the optimal range is 5-8 for Indian traffic. More bidders means more competition for every impression, which directly translates to higher revenue.
The fix: Add bidders that perform well for Indian traffic: AppNexus, Rubicon (Magnite), PubMatic, Index Exchange, and Criteo are strong performers. Don't go overboard though: beyond 8-10 bidders, the latency cost starts to outweigh the revenue gain.
3. Timeout Settings That Are Too Low (or Too High)
Prebid timeouts control how long the auction waits for bid responses. Set them too low (under 1000ms) and you miss bids from slower but potentially higher-paying partners. Set them too high (over 3000ms) and you delay ad rendering, hurting user experience and viewability.
The fix: Start with a 1500ms timeout for Indian audiences (accounting for higher average latency) and optimize from there. Use Prebid's built-in timeout analytics to find the sweet spot where you capture 95%+ of bids without excessive delay.
4. Not Using Prebid Server for Mobile
Client-side header bidding on mobile devices is particularly expensive. Each bidder adds JavaScript execution time on already-constrained mobile processors. This tanks your Core Web Vitals and can even cause timeouts.
The fix: Consider Prebid Server (server-side header bidding) for mobile traffic. It moves the auction to the server, reducing client-side JavaScript by 60-80% and dramatically improving mobile page speed. The trade-off is slightly lower cookie match rates, but for Indian mobile traffic where cookie rates are already lower, the speed benefit outweighs this.
5. No Floor Prices or Dynamic Floors
Without floor prices, you're letting demand partners bid whatever they want, and some will happily pay fractions of a cent for premium inventory. Many Indian publishers run without any floor pricing strategy.
The fix: Implement Prebid's price floors module with dynamic floors based on ad unit, device type, geography, and time of day. Start conservative and adjust based on fill rate impact. A 10% drop in fill rate with a 25% increase in CPM is a net win.
How to Check Your Setup
Want to see how your header bidding stacks up? Run a free RevenueRx audit. We detect your Prebid version, configured bidders, timeout settings, and more, then score your setup against industry best practices. The whole scan takes under 2 minutes and doesn't require any dashboard access.