Which traffic is relevant?
Countries, devices, browsers, sources and channel-specific attributes define eligibility.
Targeting, filters & operating limits
The right rules.
At the right resource.
A Search feed, an RTB exchange and a CPA offer do not need the same settings. Nexus exposes channel-specific controls so your team can define relevance, quality and commercial boundaries deliberately.
Which requests need scrutiny?
Request consistency, network signals and explicit lists express your traffic policy.
What are the operating boundaries?
Bids, revenue share, caps, budgets, QPS and timeouts serve different purposes in each channel.
Compare the actual control surfaces
One suite.
Five different toolsets.
This is a map of configuration fields, not a claim that every product enforces identical policy. Partner and integration requirements remain part of the rollout.
On smaller screens, scroll horizontally to compare all five channels.
| Control area | Search ↗ | XML feeds ↗ | OpenRTB ↗ | Video ↗ | CPA ↗ |
|---|---|---|---|---|---|
| Countries, OS, devices | Feed settings | Feed targets | Exchange + demand | Channel + tag | Offer targets |
| Browser / version | Browser + version | Browser selection | Browser selection | Integration-specific | Browser + OS versions |
| Domains / source IDs | Link + feed rules | Domains + SubID | Site / publisher / domain | Channel / app context | SubID / domain / IP lists |
| Applications | Integration-specific | Integration-specific | Bundle + app name | Bundle + app name | App ID + offer context |
| Specialized targeting | Keywords + replacement | Carrier + subscriber age | Ad size + inventory type | Language + environment | Connection + carrier |
| Operating limits | Search caps + RevShare | QPS + bid + clicks + budget | Floors + QPS + timeout | CPM + QPS + hourly/daily caps | Payout + daily/monthly caps |
Traffic-quality policy
Make the checks explicit.
Keep the interpretation human.
Choose the relevant checks, understand their effects and inspect the resulting traffic. A rejected request needs context, and a filter is not a guarantee of perfect detection.
Connect policy with reporting ↗- Network signals
- Datacenter, crawler, attack-source, fake-crawler, Tor, scraper, VPN and proxy categories are available in the relevant resource editors.
- Request consistency
- XML controls include duplicate/fast clicks, JavaScript, cookies, referrer, user-agent, iframe and headless-browser checks.
- Explicit exceptions
- Use supported source, domain, publisher, creative and IP lists to express policy at the correct resource level.
- Evidence after configuration
- Review invalid traffic and error dimensions alongside delivery and financial indicators. No filter guarantees perfect detection.
Open the relevant playbook
Go from a category
to the setting that matters.
Explore Targets, Filters and Limits in the relevant Resources guides. Use a guided demo to confirm the fields and integrations required by your workflow.
Search Syndication
Search caps · Revenue share · Backfill · Source context · NET imports · Reusable reports
Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.
Explore Search controls ↗XML feed operations
Commercial limits · Request capacity · Repeated clicks · Subscriber context · Publisher handling · NET imports
Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.
Explore XML feeds controls ↗Programmatic operations
Version and auction · Bid boundaries · Supply context · Demand exclusions · Delivery settings · Financial visibility
Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.
Explore OpenRTB controls ↗Video monetization
Environment · Commercial setup · Traffic policy · Expiry and limits · Delivery context · Playback evidence
VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.
Explore Video controls ↗Performance offer management
Commercial models · Conversion window · Volume limits · Private access · Source rules · Click diagnostics
Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.
Explore CPA controls ↗Start with your traffic policy
Bring your rules.
We will map the controls.
Define your traffic sources, partner requirements, limits and acceptance criteria before launch.