Publisher channels
Configure publisher, price type, CPM, floor, required fields and the web, app or CTV environment.
Video monetization
Manage publisher channels and demand tags in a dedicated VAST workspace. Configure environments, pricing and delivery limits, then follow video events from Started to Completed.
Inside the product
Configure publisher, price type, CPM, floor, required fields and the web, app or CTV environment.
Keep advertiser, source, tag type, timeout and delivery settings together. Tag configuration offers VAST, Audio and RTB options.
Configure countries, operating systems, ad sizes, languages, bundle IDs and application names.
Set applicable hourly and daily revenue, request and impression limits. Demand tags add maximum QPS and scheduled-delivery controls.
Assign allowed tags to a channel and allowed channels to a tag. Keep publisher integration and host configuration separate from demand.
Inspect VAST URI validity, errors, fill, impressions and revenue. Review Started, First Quartile, Midpoint, Third Quartile and Completed.
A day in the platform
A practical workflow for your Video operation, with the relevant controls at each step.
Define publisher, pricing, environment and integration fields.
Set demand source, timeout, targeting and delivery limits.
Grant access between channels and tags.
Review request and URI errors alongside fill, revenue and completion.
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 ↗Channel / tag · Country · OS · App bundle · Application · Environment · Device / size
Deployment scope. VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.
A closer look
Configure the resource that owns the decision. Features and integrations are scoped to your enabled modules.
Select web, app or CTV and configure the required request fields.
Set publisher price type, CPM and floor, with demand-tag CPM configured independently.
Configure network-risk and applicable referrer, IP and user-agent matching checks.
Control impression expiry, QPS and hourly or daily limits.
Configure tracking pixels and scheduled delivery on demand tags.
Review URI validity, invalid impressions, fill and completion events.
Inside the operation
Choose a stage to see its controls. This is a workflow explanation; explore the actual platform in a demo.
Assign allowed tags to a channel and allowed channels to a tag. Keep publisher integration and host configuration separate from demand.
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 ↗What the audience sees
In-stream video advertising plays inside a video player before, during or after the requested content. The viewer experience depends on more than the media file: VAST metadata, wrapper depth, player capability, duration and tracking must work as one delivery chain.
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.