NEXUSAD PLATFORM
Sign inBook a demo
XML / JSON feeds

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.

Explore the features ↓Calculate your price ↗
Concept illustration of publisher feeds routed through a central hub to demand partners.
Publisher supply. Mapped demand.Concept illustration
explicit assignments
Publisher ↔ feed
operating boundaries
QPS + budgets
separate reporting views
Revenue + NET

Inside the module

Connect partners. Define the traffic policy.

Feed Mapping

Publisher-to-feed mapping

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.

Provider Setup

Provider configuration

Set provider and feed type, image and icon requirements, SubID handling, result count and timeout.

Traffic Targeting

Detailed targeting

Configure countries, operating systems, browsers, devices, domains, carriers, keywords and subscriber age.

Bids & Limits

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 Checks

Quality policy

Configure duplicate, fast-click, JavaScript, cookie, referrer, user-agent, iframe and headless-browser checks alongside network-risk categories.

Partner Reporting

Reports from both sides

Review requests, coverage, valid and invalid clicks, revenue, NET metrics and profit. Configure provider NET imports separately from traffic reporting.

Additional Fraud Filters are optional. See the plan details for add-ons; supported controls depend on the resource and agreed integration.

Inside the operation

Explore XML / JSON feeds in operation.

Choose a stage to see its controls. This is a workflow explanation; explore the actual platform in a demo.

XML / JSON feedsWorkflow
01 / Incoming requestAffiliatePublisher · SubID
02 / NexusMap & qualify
  • Feed mapping
  • Quality rules
  • Bids & limits
03 / Demand responseFeedResult count · timeout
Possible outcomes
Eligible responseorEmpty / error
04 / REVIEWRequests · Valid requests · Errors
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.

  • Minimum bid
  • QPS / click limits
  • Budget / expiry
A feed response is not a confirmed click or revenue. Quality filters do not detect every invalid interaction.Workflow illustration, not a live account. Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.

See it with your team.

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 ↗
Book a demo ↗

Reporting that fits the channel

Compare traffic, quality and commercial results.

Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.

Explore reporting & data freshness ↗

Performance indicators

  • Requests
  • Valid requests
  • Errors
  • Coverage
  • Clicks
  • Invalid clicks
  • NET clicks
  • CPC
  • NET CPC
  • Revenue
  • NET revenue
  • Profit

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 and supported Popunder JS placements. 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.

Explore MCP support ↗

Across the Nexus suite

Open standards. Your own platform.

Explore the integration foundation
IAB Tech Lab

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 specification
IAB Tech Lab

VAST

Video ad serving

Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.

VAST specification
AI connectivity

Full MCP

A structured interface for AI clients

Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.

Explore AI + MCP
Your operating model

White-label

Your brand. Your domains.

Build your partner-facing experience around your identity, enabled products and agreed deployment requirements.

Explore white-label

Protocols 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.

Discuss your requirements ↗