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.

01

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
02

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 configuration guide below explains Video channel policy, not iframe filtering or a universal policy for every module.

Video channel quality policyConfiguration guide
  1. 01 / CONTEXT

    Review duplicate-request and network-risk controls in the Video channel context.

  2. 02 / SUPPORTED CONTROLS
    • Duplicate requests
    • Datacenter / crawler
    • Tor / VPN / proxy
  3. 03 / REVIEW

    Inspect request and URI errors alongside delivery evidence. These controls are not proof of playback compatibility.

Illustrative configuration, not a live account. This is Video channel policy, not a universal filter set. No filter guarantees perfect detection; Additional Fraud Filters are optional.
03

Repetition controls

Duplicate-request policy, IP request ceilings and global maximum requests help protect delivery from repeated or excessive behavior.

Product accuracy

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.

Published by Nexus Soft.

Content revised

Sources and product scope

Product references describe available controls and their limits. Examples are illustrative.