Exchange configuration
Configure adapter, OpenRTB version, revenue share, auction type, no-bid code and billing event for the supply connection.
Programmatic operations
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.
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.
Inside the product
Configure adapter, OpenRTB version, revenue share, auction type, no-bid code and billing event for the supply connection.
Configure DSP type, timeout, traffic types, Gzip and demand-side QPS. Keep NET import settings with the demand resource.
Use country, OS, browser, device, ad size, application and bundle controls, with inventory and video-type settings on demand.
Set Allowed Demands for an exchange and Allowed Exchanges for demand. Define trading relationships explicitly.
Configure bid floors, exchange maximum bid, network-risk rules and SSP, site, publisher, domain or creative lists.
Configure UID macros and image or iframe sync URLs. Review synced requests, win rate, impressions, revenue, spend and NET metrics.
Review requests, errors, cookie-sync activity, win rate, impressions and local versus NET spend to investigate the auction path.
A day in the platform
A practical workflow for your OpenRTB operation, with the relevant controls at each step.
Configure the exchange adapter, OpenRTB version and commercial rules.
Set demand targeting, bid floors, QPS and timeout.
Define which exchange and demand resources may work together.
Inspect requests, errors, win rate, impressions and NET financial indicators.
Reporting that fits the channel
Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.
Explore reporting & data freshness ↗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.
A closer look
Configure the resource that owns the decision. Features and integrations are scoped to your enabled modules.
Select OpenRTB version and auction settings for the partner connection.
Configure floors and exchange maximum bid separately from demand QPS and timeout.
Use SSP, Site/App ID, Publisher ID, domains and app bundles.
Manage supported domain, inventory and creative-ID lists.
Configure notifications, supply-chain settings and third-party pixel limits.
Review revenue, NET revenue, spend, NET spend and profit alongside delivery.
Inside Nexus / OpenRTB settings
Inspect the actual exchange editor: connection and bidding settings sit alongside inventory types, targeting, filters and partner grants. Each area has its own reviewable configuration.
Choose the adapter and OpenRTB version, then review revenue share and adapter-specific auction settings.
The Types & Endpoints tab exposes separate controls for popup, HTML banner, banner, native and video inventory.
Captured from Nexus. Identifying details are hidden. These are new, unsaved exchange settings. The displayed version and numeric defaults are not recommendations, performance claims or proof of protocol certification.
What the audience sees
Display banners are visual ad units placed inside a page or application layout. They are familiar and scalable, but effective delivery still depends on creative dimensions, placement context, viewability, frequency and transparent supply paths.
Explore this ad format ↗Illustrative placement, not a live advertisement. Format and integration scope are confirmed for your deployment.
Part of your Nexus
Your brand, domains and partner experience, with deployment scope agreed up front.
Connect supported AI clients through an identity-aware setup and inspect the available tools.
Server management, integrations and custom development around your platform.
Across the Nexus suite
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 specificationVideo ad serving
Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.
VAST specificationA structured interface for AI clients
Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.
Explore AI + MCPYour brand. Your domains.
Build your partner-facing experience around your identity, enabled products and agreed deployment requirements.
Explore white-labelProtocols 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.
Make it concrete
Bring your use case, partner integrations and expected volume. We will map the relevant controls.