A single affiliate or member may aggregate many traffic sources. Without a sub-ID contract, poor and strong sources collapse into the same reporting row.
Preserve source context
Nexus can require or preserve sub-ID context in XML request configuration. Naming and allowed values should be agreed with the partner before launch.
- Source
- Placement
- Campaign reference
- Partner-defined segment
Apply policy at the correct level
Member limits protect the account boundary while sub-ID reporting helps operators investigate quality and performance beneath it.
Avoid identity ambiguity
Sub-IDs should not be treated as authenticated identity. They are request context and must be validated and interpreted within the partner contract.
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.