NEXUSAD PLATFORM

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.

Concept illustration of supply and demand partners connected through an exchange hub.
Supply and demand. Explicit relationships.Concept illustration
OpenRTB configuration
2.4 / 2.5 / 2.6
explicit partner grants
Exchange ↔ demand
reporting context
Win + NET spend

Inside the module

A trading relationship you can configure.

Exchange Setup

Exchange configuration

Configure adapter, OpenRTB version, revenue share, auction type, no-bid code and billing event for the supply connection. Prebid.js and Prebid Server integrations are available now; configure compatible adapters, endpoints and inventory for your deployment.

Demand Controls

Demand delivery controls

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

Inventory Targeting

Inventory targeting

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

Partner Access

Partner grants

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

Floors & Filters

Floors and quality filters

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

Sync & Reporting

Cookie sync and reporting

Cookie sync is available now. Configure UID macros and image or iframe sync URLs. Review synced requests, win rate, impressions, revenue, spend and NET metrics. Cookie sync has its own partner and browser requirements, separate from the Prebid integration setup.

Additional Fraud Filters are optional. See the plan details for add-ons; supported controls depend on the resource and agreed integration.

Inside the operation

Explore OpenRTB in operation.

Choose a stage to see its controls. This is a workflow explanation; explore the actual platform in a demo.

OpenRTBWorkflow
01 / Bid requestSupplySite · app · format
02 / NexusQualify & route
  • Targeting
  • Bid floors
  • Partner grants
03 / Eligible partnersDemandQPS · timeout
Possible outcomes
Bid responseorNo bid
04 / REVIEWRequests · Delivery signals · NET results
Choose who can trade with whom.

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

  • Partner grants
  • Inventory targeting
  • Bid floors
A bid response is not an impression or confirmed revenue. No eligible bid is also a possible outcome.Workflow illustration, not a live account. Connected partners, supported formats and operating settings depend on your deployment.

See it with your team.

Bring your operating requirements. We will walk through the current interface and the relevant configuration, integrations and reporting controls.

Explore targeting and operating controls in Resources ↗
Book a demo ↗

Reporting that fits the channel

Compare traffic, quality and commercial results.

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 ↗