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
Hosting and iframe filters provide configuration surfaces for deployments that distinguish data-center or embedded traffic patterns.
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.