Direct advertiser demand gives an operator more commercial control, but it also adds responsibility for campaign eligibility, creative or listing review, balance policy and transparent performance reporting.
Create a governed advertiser workspace
Only authorized advertiser roles should access campaign creation, bids, funding context and performance. Campaigns can be reviewed, suspended or removed when they violate platform or publisher policy.
- Advertiser role
- Campaign moderation
- Minimum bid policy
- Account and balance boundary
Target with supported request evidence
Country, region, operating system, browser, device class and supported device-brand signals can narrow eligibility. The platform should state which service enforces each target and how missing context is handled.
Inside Nexus / configuration example
The campaign editor distinguishes operating-system and browser families from version-specific targeting. The captured selections illustrate configuration, not campaign results.
Review campaign eligibility
Set country and device criteria, and distinguish OS and browser families from version-specific targeting.
Captured from an existing campaign with its identifier hidden. Visible selections illustrate configuration, not campaign results or recommended targeting.
Connect bids to observable outcomes
Detailed campaign statistics should relate eligible traffic, delivered results, clicks and downstream outcomes to the commercial rules in effect at the time. Catch-all or fallback campaigns require the same visibility as precisely targeted demand.
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.