Publisher-to-feed mapping
Choose demand feeds for each affiliate account. Keep publisher integration details and feed eligibility understandable.
XML / JSON feeds
Core features.
Connect publisher accounts with demand feeds. Configure targeting, minimum bids, QPS and click limits, then compare publisher-side and feed-side results.
Compare price plans ↗Provider configuration
Set provider and feed type, image and icon requirements, SubID handling, result count and timeout.
Detailed targeting
Configure countries, operating systems, browsers, devices, domains, carriers, keywords and subscriber age.
Bids, limits and expiry
Set minimum bid, maximum requests and QPS, daily budget, click limits, clicks per IP or IP + user-agent, and result expiry.
Quality policy
Configure duplicate, fast-click, JavaScript, cookie, referrer, user-agent, iframe and headless-browser checks alongside network-risk categories.
Reports from both sides
Review requests, coverage, valid and invalid clicks, revenue, NET metrics and profit. Configure provider NET imports separately from traffic reporting.
A day in the platform
From setup to a decision.
A practical workflow for your XML feeds operation, with the relevant controls at each step.
- 01
Set up the affiliate
Define the publisher account, integration and traffic-handling settings.
- 02
Configure demand
Add provider settings, commercial limits, targeting and quality rules.
- 03
Assign the relationship
Map selected feeds to the affiliate account.
- 04
Compare both sides
Review affiliate and feed reports by SubID, country, browser and domain.
Reporting that fits the channel
Know what to review.
Know where to look.
Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.
Explore reporting & data freshness ↗Performance indicators
Ways to break it down
Affiliate · Feed · SubID · Country · OS · Browser · Domain
Deployment scope. Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.
Keep the operating context
Controls that connect to a decision.
Connect affiliates with advertiser feeds, define allowed mappings and apply request-quality checks, minimum bids, QPS, click limits and daily budgets.
- Affiliate-to-feed mappings
- Duplicate protection & IP limits
- Feed QPS, click caps & budgets
Compare affiliate and feed requests, errors, clicks, revenue and provider NET figures to identify the partner or source that needs attention.
Explore targeting & filters ↗Extend the workflow with AI + MCP.
Connect supported AI clients to domain-scoped tools. Access, audit history and allowed operations stay within the boundaries configured for your deployment.
Across the Nexus suite
Open standards. Your own platform.
OpenRTB
2.4 / 2.5 / 2.6 configuration
Connect exchange and demand partners with version selection, auction settings, bid floors and timeouts in the RTB module.
OpenRTB specificationVAST
Video ad serving
Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.
VAST specificationFull MCP
A structured interface for AI clients
Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.
Explore AI + MCPWhite-label
Your brand. Your domains.
Build your partner-facing experience around your identity, enabled products and agreed deployment requirements.
Explore white-labelProtocols apply to the relevant Nexus modules. Supported versions, player compatibility and partner interoperability are confirmed for your integration. References to IAB Tech Lab standards do not imply certification or endorsement.
See these capabilities in your workflow.
Share the channel, expected volume and integrations. No credentials or production data required.