XML feed operations
Connect publisher accounts with demand feeds. Configure targeting, minimum bids, QPS and click limits, then compare publisher-side and feed-side results.
Inside the product
Choose demand feeds for each affiliate account. XML direct links are supported for publisher traffic and configured demand destinations. Popunder JS is available with script, frequency and delay settings. Keep source controls in place; browser restrictions still determine window behavior.
Set provider and feed type, image and icon requirements, SubID handling, result count and timeout.
Configure countries, operating systems, browsers, devices, domains, carriers, keywords and subscriber age.
Set minimum bid, maximum requests and QPS, daily budget, click limits, clicks per IP or IP + user-agent, and result expiry.
Configure duplicate, fast-click, JavaScript, cookie, referrer, user-agent, iframe and headless-browser checks alongside network-risk categories.
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
A practical workflow for your XML feeds operation, with the relevant controls at each step.
Define the publisher account, integration and traffic-handling settings.
Add provider settings, commercial limits, targeting and quality rules.
Map selected feeds to the affiliate account.
Review affiliate and feed reports by SubID, country, browser and domain.
Reporting that fits the channel
Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.
Explore reporting & data freshness ↗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.
A closer look
Configure the resource that owns the decision. Features and integrations are scoped to your enabled modules.
Define minimum bid, daily budget and revenue-share configuration at feed level.
Bound requests and QPS independently from pricing-plan allowances.
Configure limits per IP and IP + user-agent, duplicate policy and result expiry.
Use subscriber-age and carrier targeting where the feed provides those signals.
Configure backfill, postback and invalid-traffic handling in the affiliate editor.
Select the provider API adapter, update days, SubID import behavior and timeout.
Inside the operation
Choose a stage to see its controls. This is a workflow explanation; explore the actual platform in a demo.
Set minimum bid, maximum requests and QPS, daily budget, click limits, clicks per IP or IP + user-agent, and result expiry.
Bring your operating requirements. We will walk through the current interface and the relevant configuration, integrations and reporting controls.
Explore targeting and operating controls in Resources ↗What the audience sees
Contextual and domain advertising derive intent from a page, site or domain rather than a conventional user search. The operating challenge is to preserve the source, extracted context and selected demand route so relevance and quality remain explainable.
Explore this ad format ↗Illustrative placement, not a live advertisement. Format and integration scope are confirmed for your deployment.
Part of your Nexus
Your brand, domains and partner experience, with deployment scope agreed up front.
Connect supported AI clients through an identity-aware setup and inspect the available tools.
Server management, integrations and custom development around your platform.
Across the Nexus suite
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 specificationVideo ad serving
Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.
VAST specificationA structured interface for AI clients
Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.
Explore AI + MCPYour 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.
Make it concrete
Bring your use case, partner integrations and expected volume. We will map the relevant controls.