A partner portal is not only a registration screen. It is the boundary where identity, traffic permissions, feed access, commercial terms and operational support meet.
Approve access deliberately
Applications can be reviewed before activation, assigned an account level and connected only to the traffic types and feed profiles appropriate to the agreement. Signup date, source IP and account context provide useful review evidence.
- Approval and rejection
- Account levels
- Traffic-type permissions
- Feed profiles
Respond without destroying history
Suspension should stop or restrict traffic while preserving the account, configuration and evidence required to resolve a problem. Search by identity, level or active feed helps operators find the relevant relationship quickly.
Separate payout workflow from delivery
Balances, payout requests, processing periods, minimum thresholds and fees belong to a controlled financial workflow. Exact payment methods and legal requirements depend on the deployment and commercial agreement.
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.