OpenRTB

Core features.

Manage exchange and demand connections with OpenRTB version selection, bid floors, targeting and partner grants. Keep auction and financial signals in the same operating view.

Compare price plans ↗
01

Exchange configuration

Configure adapter, OpenRTB version, revenue share, auction type, no-bid code and billing event for the supply connection.

02

Demand delivery controls

Configure DSP type, timeout, traffic types, Gzip and demand-side QPS. Keep NET import settings with the demand resource.

03

Inventory targeting

Use country, OS, browser, device, ad size, application and bundle controls, with inventory and video-type settings on demand.

04

Partner grants

Set Allowed Demands for an exchange and Allowed Exchanges for demand. Define trading relationships explicitly.

05

Floors and quality filters

Configure bid floors, exchange maximum bid, network-risk rules and SSP, site, publisher, domain or creative lists.

06

Cookie sync and reporting

Configure UID macros and image or iframe sync URLs. Review synced requests, win rate, impressions, revenue, spend and NET metrics.

A day in the platform

From setup to a decision.

A practical workflow for your OpenRTB operation, with the relevant controls at each step.

  1. 01

    Register supply

    Configure the exchange adapter, OpenRTB version and commercial rules.

  2. 02

    Connect demand

    Set demand targeting, bid floors, QPS and timeout.

  3. 03

    Grant partner access

    Define which exchange and demand resources may work together.

  4. 04

    Review the auction path

    Inspect requests, errors, win rate, impressions and NET financial indicators.

Reporting that fits the channel

Know what to review.
Know where to look.

Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.

Explore reporting & data freshness ↗

Performance indicators

  • Requests
  • Errors
  • Synced requests
  • NURL / BURL / LURL
  • Impressions
  • Win %
  • Conversions
  • Revenue
  • NET revenue
  • Spend
  • NET spend
  • Profit

Ways to break it down

Exchange · Site ID · Publisher ID · Size · Country · OS / browser · Device · Connection / carrier · Domain · Bundle

Deployment scope. Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.

Keep the operating context

Controls that connect to a decision.

Connect supply and demand through an OpenRTB workflow with explicit endpoint routing, capacity boundaries and auction policy.

  • Supply & demand endpoints
  • QPS and timeout boundaries
  • Inventory and floor policy

Review requests, errors, cookie-sync activity, win rate, impressions and local versus NET spend to investigate the auction path.

Explore targeting & filters ↗

Extend the workflow with AI + MCP.

Connect supported AI clients to domain-scoped tools. Access, audit history and allowed operations stay within the boundaries configured for your deployment.

Explore MCP support ↗

Across the Nexus suite

Open standards. Your own platform.

Explore the integration foundation
IAB Tech Lab

OpenRTB

2.4 / 2.5 / 2.6 configuration

Connect exchange and demand partners with version selection, auction settings, bid floors and timeouts in the RTB module.

OpenRTB specification
IAB Tech Lab

VAST

Video ad serving

Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.

VAST specification
AI connectivity

Full MCP

A structured interface for AI clients

Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.

Explore AI + MCP
Your operating model

White-label

Your brand. Your domains.

Build your partner-facing experience around your identity, enabled products and agreed deployment requirements.

Explore white-label

Protocols apply to the relevant Nexus modules. Supported versions, player compatibility and partner interoperability are confirmed for your integration. References to IAB Tech Lab standards do not imply certification or endorsement.

See these capabilities in your workflow.

Share the channel, expected volume and integrations. No credentials or production data required.

Discuss your requirements ↗