AdTech field guide
Clear definitions for the protocols, commercial models and operating concepts used across the Nexus platform—written for product, commercial and technical teams.
Shared language
A platform evaluation becomes easier when every stakeholder understands what moves through the system, where decisions happen and which team controls the outcome. This guide connects common industry terms to practical Nexus workflows.
An open protocol used to exchange bid requests and bid responses between programmatic advertising systems in real time.
IN NEXUSNexus uses governed OpenRTB integration patterns to connect supply and demand while keeping routing and commercial policy visible.
The Video Ad Serving Template standard describes how a video player discovers, tracks and renders an advertisement.
IN NEXUSNexus supports VAST-oriented operations across web, app and connected TV delivery paths.
A structured stream of offers, advertisements or partner records exchanged between systems outside a real-time auction.
IN NEXUSNexus normalizes partner fields, delivery rules and feed workflows before traffic reaches a monetization destination.
Cost per action is a commercial model in which value is tied to a validated outcome such as a registration, lead or sale.
IN NEXUSNexus keeps campaign operations, conversion validation and partner configuration within the same control plane.
Queries per second expresses the request rate an advertising integration or endpoint is expected to process.
IN NEXUSCapacity limits and routing policy belong in governed platform configuration rather than scattered partner notes.
The operational layer used to configure, observe and govern systems without placing every decision inside the data path.
IN NEXUSNexus provides a shared control plane above independent revenue engines and tenant infrastructure.
A system that operates isolated customer or business environments through a shared product and operating model.
IN NEXUSNexus can keep tenant URLs, connections, modules and limits distinct while preserving centralized administration.
Model Context Protocol is an open protocol that lets AI clients discover and call approved tools and read structured resources.
IN NEXUSThe Nexus MCP server exposes product knowledge, capability discovery and deployment guidance to compatible AI clients.
From terminology to architecture