Understanding the Oxxion RTD Module: Smarter Bidder Filtering for Prebid.js

Managing a successful header bidding setup requires more than just connecting bidders. Publishers continuously struggle with signal overload, ad stack inefficiencies, and the trade-off between maximizing demand and minimizing latency. Prebid.js offers many ways to optimize, but real-time data modules are often underused—especially when it comes to hands-on bidder filtering.

The Oxxion RTD module introduces a practical, data-driven approach to filtering bidders and improving auction quality. By understanding and applying this module in your Prebid.js stack, you can shrink wasted request volume, uncover poor-performing partners, and make faster, evidence-based revenue decisions.

What Is the Oxxion RTD Module?

The Oxxion Real-Time Data (RTD) module is an add-on for Prebid.js that allows publishers to make smarter, data-driven decisions about which bidders participate in each auction. Instead of sending every bid request to every SSP or exchange, Oxxion’s approach lets you conditionally filter those bidders in real time based on historical performance or custom rules.

For publishers, this translates into greater control over auction traffic. By routing bid requests only to high-performing partners, you can cut down on tech fees, reduce unnecessary load on both users and ad servers, and improve overall page speed. Oxxion’s functionality is especially useful for larger publishers with a bloated bidder list, or for those experimenting with new partners and needing to track performance granularly.

Real-World Example: Header Bidding Optimization

Consider a site running five bidder adapters in Prebid.js. After tracking fill rates and effective CPMs, you discover that one bidder replies only 0.5% of the time and never significantly beats your winners. Oxxion makes it straightforward to set a threshold (say, 1% bid response) and automatically exclude that bidder from future auctions unless performance improves—without custom code or manual data analysis.

Configuring Oxxion in Prebid.js

Integrating Oxxion into your Prebid.js stack requires a two-step process: building your bundle with the right modules and updating your Prebid configuration. This process is low-friction for most ad ops teams familiar with Prebid’s modular structure.

Prebid Build Setup

During your Prebid build, include both the core ‘rtdModule’ and ‘oxxionRtdProvider’. For example:

gulp build –modules=schain,priceFloors,currency,consentManagement,appnexusBidAdapter,rubiconBidAdapter,rtdModule,oxxionRtdProvider

This ensures that real-time data hooks are available and that Oxxion can interact with bidder selection just before the auction.

Key Configuration Parameters

In your ad stack configuration, set up the ‘realTimeData’ object inside pbjs.setConfig. The most important parameters are:

– domain: Identifies your property within Oxxion’s systems (obtained from Oxxion)
– threshold: The minimum expected bid rate or ‘false’ to skip filtering
– samplingRate: Allows a percentage of otherwise filtered requests through for testing (e.g., 10 for 10%)
– bidders: Optionally restrict filtering to specific SSPs

A typical configuration gives you precise, granular control. For example, setting ‘threshold’ to 1.0 and ‘samplingRate’ to 10 means only bidders with a bid rate above 1% will be called unless they enter the random 10% testing pool. This approach balances revenue optimization with ongoing partner evaluation.

Tuning Bidder Filtering: Practical Use Cases and Pitfalls

Oxxion’s real strength is in its flexible logic for controlling each bidder’s participation. However, it’s important to understand both the typical use cases and common mistakes publishers should avoid.

Example Use Case: Dynamic Exclusions Based on Bid Rate

Suppose a publisher notices that two bidders—BidderX and BidderY—have dropped their response rates after a major traffic spike. By setting Oxxion filtering to only call bidders with more than a 2% response rate, the publisher can dynamically sideline non-responsive SSPs. This cleanup reduces auction latency, improves buyer competition, and keeps code reviews minimal.

Pitfall: Over-Aggressive Filtering

There’s a risk in tuning thresholds too tight—excluding bidders that underperform for a brief period could miss out on valuable demand when markets rebound. Oxxion partially mitigates this with the ‘samplingRate’ parameter, but ad ops teams should still regularly audit logs and adjust filters. Always validate that key demand partners are not mistakenly excluded during high-value traffic spikes or events.

Best Practices for Strategic Implementation

Thoughtful use of the Oxxion RTD module can yield both short-term and long-term gains, but requires ongoing management. Here are actionable best practices for publishers looking to get the most from Oxxion filtering:

– Regularly analyze bidder logs and performance metrics before setting thresholds
– Leverage the sampling feature to detect emerging changes in bidder behavior
– Start with conservative thresholds, adjust upward only after consistent underperformance is proven
– Test exclusions on a segment of traffic before applying globally
– Document configuration changes in your ad ops playbook for transparency and troubleshooting

These practices help prevent accidental revenue loss and ensure your auction logic remains adaptable to changing market conditions.

What this means for publishers

For publishers, Oxxion’s RTD filtering offers a practical toolkit for streamlining auction workflows, improving auction density, and eliminating unnecessary tech costs from non-contributing bidders. This module empowers ad ops teams to shift from blanket bidder participation to informed, performance-driven filtering—leading to more agile, data-responsive monetization strategies.

Practical takeaway

Oxxion’s RTD module adds a layer of flexible, data-backed bidder selection to any Prebid.js setup. Publishers no longer need to manage complex custom scripts or manual bidder reviews. Instead, configure Oxxion to automate the inclusion/exclusion of SSPs based on proven criteria like bid rate and auction participation.

Start with a period of thorough analysis of your bidder response data, then gradually introduce Oxxion thresholds—leveraging the sampling option for ongoing health checks. Iterate, monitor, and maintain transparency with your team to maximize the upside and stay agile with market shifts. Ultimately, Oxxion is best used as part of a dynamic, feedback-driven optimization process—not a “set and forget” tool.