NEXUSAD PLATFORM
Sign inBook a demo
← All platform solutions

Connect supply and demand partners

OpenRTB exchange & traffic hub

Operate the connection between programmatic supply and demand. Manage exchanges, demand access, inventory rules and trading reports from the OpenRTB workspace.

Discuss this platform ↗See how it works ↓

Existing module workflow · For programmatic networks, exchanges and supply aggregators.

How it works

From your partners
to a working operation.

An operator connects a new supply partner, enables selected demand connections for that exchange and investigates request quality and trading performance in one workspace.

  1. 01Supply bid request
  2. 02Inventory & traffic checks
  3. 03Eligible demand / campaigns
  4. 04Response & event reporting

Build with

Your Nexus components

Inside the operation

What your team
can manage.

Trading relationships

Configure exchange and demand connections. Explicitly control which demand can receive traffic from each exchange.

Inventory and routing policy

Use supported inventory, geo, device, domain and app rules, QPS controls and partner-specific settings to qualify requests.

Operational reporting

Review requests, valid requests, impressions, clicks, revenue, spend and profit. Investigate traffic errors alongside trading results.

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
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.

Before launch

What you need
to connect.

  • Supply and demand endpoint access plus trading agreements
  • A tested OpenRTB contract for formats, events and partner requirements
  • Capacity, timeout, filtering and commercial settings

Formats & delivery

What can the
visitor actually see?

Explore relevant formats and traffic models. Delivery still depends on the selected module, publisher placement and partner integration.

Display banners

Learn how static, animated, HTML5 and responsive display banners occupy web and app placements, enter auctions and produce measurable impressions and clicks.

How it works ↗

Native ads

See how native ads use structured assets to match a publisher experience while preserving disclosure, placement control and measurable campaign outcomes.

How it works ↗

In-stream video

Understand pre-roll, mid-roll and post-roll video ads, VAST responses, player events, creative compatibility and completion-based measurement.

How it works ↗

Evaluate your platform

Plan your OpenRTB exchange

Map your supply and demand partners before choosing capacity. Use a demonstration to review exchange settings, eligible demand, inventory rules and the reports used to investigate trading results.

What to review in your demo

  1. Review a connection

    Confirm the adapter, OpenRTB version, inventory types and partner-specific request and event requirements.

  2. Control eligible demand

    Review partner grants, targeting, incoming QPS, timeout boundaries and auction settings.

  3. Inspect the result

    Separate requests, no-bids, errors, impressions and partner-reported revenue when reviewing a trading period.

Request this platform demo ↗

Inspect traffic and trading results together

Requests, valid requests, impressions, clicks, revenue, spend and profit in the RTB workspace. Values are shown as captured for the selected period, not a performance guarantee.

Inspect traffic and trading results together

Actual Nexus dashboard · original captured values. Requests, valid requests, impressions, clicks, revenue, spend and profit in the RTB workspace. Values are shown as captured for the selected period, not a performance guarantee.

Capacity, setup and running costs

OpenRTB costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations. Each 1,000 incoming QPS block has a maximum of 10,000,000 clicks per day for this module in this location; 2,000 incoming QPS allows a maximum of 20,000,000 clicks per day. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus.

One-time setup: $1,500 per platform, separately from monthly capacity and selected add-ons.

Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised.

Calculate capacity and first-month cost ↗

Before you choose a platform

Are supply and demand partners included?

You supply endpoint access and trading agreements. Nexus provides the exchange operating components; premium inventory, demand access and revenue are not bundled guarantees.

Is an exchange the same as a DSP?

An exchange connects supply and demand. A DSP adds advertiser buying workflows. Review campaign management, creatives, buying and measurement separately if your goal is a DSP deployment.

How do we validate a new partner?

Agree on request and response samples, inventory formats, event tracking, timeout behavior and reporting definitions. Run acceptance checks for the actual adapter and partner before moving production traffic.

Related deployments

Another way to build.

Compare all platform types ↗
01Existing module workflow

Connect traffic sources to advertiser feeds

XML ad network

XML / JSON feedsWorkflow
01 / Incoming requestAffiliate
02 / NexusMap & qualify
03 / Demand responseFeed
A feed response is not a confirmed click or revenue. Quality filters do not detect every invalid interaction.

Run an XML / JSON feed monetization platform. Connect advertiser feeds, assign them to publishers and control how traffic is filtered, routed and monetized.

See this platform ↗
02Existing module workflow

Monetize search intent

Search Syndication

Search SyndicationWorkflow
01 / Search queryPublisher
02 / NexusMatch & route
03 / Eligible feedProvider
A search does not guarantee a monetized result or click. Provider responses and NET imports depend on the integration.

Run a search syndication platform. Connect search providers to publisher links, apply keyword and traffic rules and compare searches, clicks and partner results.

See this platform ↗

Plan your deployment

See this workflow
with the Nexus team.

Pricing depends on modules, traffic, integrations and support. Tell us what you want to operate and we will prepare a relevant demonstration and proposal.

Request a tailored demo ↗