A filter should have an owner, an input signal and an explainable result. An unexplained rejection rule makes partner support and commercial reconciliation unnecessarily difficult.
Available request context
Nexus models referrer, language, user-agent and sub-ID participation in XML request workflows. The connected engine determines how enabled signals are enforced.
- Referrer
- Language
- User agent
- Sub-ID
Environment controls
The Video channel editor groups network-risk controls for datacenters, crawlers, Tor, VPN and proxy traffic. Other modules expose their own environment checks; the Video screenshot below does not demonstrate iframe filtering or a universal policy for every module.
Inside Nexus / configuration example
The Video channel editor includes duplicate-request and network-risk controls. This is a channel configuration example—not a guarantee of detection or playback compatibility.
Inspect the traffic policy
Review the treatment of duplicate requests and network-risk categories such as datacenters, crawlers, Tor, VPN and proxy traffic.
Captured from an existing channel with its identifier hidden. Visible settings illustrate the editor, not a recommended policy or a claim of universal player compatibility.
Repetition controls
Duplicate-request policy, IP request ceilings and global maximum requests help protect delivery from repeated or excessive behavior.
This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.