XML feed operations

Manage feed partners, traffic limits and revenue together.

Connect publisher accounts with demand feeds. Configure targeting, minimum bids, QPS and click limits, then compare publisher-side and feed-side results.

Book a demo ↗Explore price plans

Nexus XML dashboard showing revenue and partner NET trends with referral and audience breakdowns. — Compare revenue and partner NET figures
XML revenue and partner NET trends with referral and audience breakdowns. Values are shown as captured for the selected period, not a performance guarantee.

Publisher ↔ feedexplicit assignments

QPS + budgetsoperating boundaries

Revenue + NETseparate reporting views

Built forAffiliate networksPublishersDemand aggregators

Inside the product

Connect partners. Set rules. Track results.

All core features ↗

Publisher-to-feed mapping

Choose demand feeds for each affiliate account. Keep publisher integration details and feed eligibility understandable.

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.

Inside the workflowIllustrative

INCOMINGPartner requestAffiliate · sub-ID · referrer

Mapping + request limitsNEXUS

DELIVERYConfigured demand feed

VISIBILITYDelivery + error context

Compare affiliate and feed requests, errors, clicks, revenue and provider NET figures to identify the partner or source that needs attention.

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

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.

A closer look

Targeting, limits and partner controls.

Configure the resource that owns the decision. Features and integrations are scoped to your enabled modules.

Commercial limits

Define minimum bid, daily budget and revenue-share configuration at feed level.

Request capacity

Bound requests and QPS independently from pricing-plan allowances.

Repeated clicks

Configure limits per IP and IP + user-agent, duplicate policy and result expiry.

Subscriber context

Use subscriber-age and carrier targeting where the feed provides those signals.

Publisher handling

Configure backfill, postback and invalid-traffic handling in the affiliate editor.

NET imports

Select the provider API adapter, update days, SubID import behavior and timeout.

Compare targeting across all products ↗

Inside Nexus / XML / JSON feeds settings

Set up each provider feed.

Start with the provider connection and delivery settings. Import a provider URL for detection, then review feed type, SubID handling and response controls before configuring traffic rules.

Nexus XML feed Settings with provider URL import, feed type, SubID handling, revenue share, result count and timeout. — Review feed delivery settings
The Settings tab brings URL import, feed type and SubID handling together with revenue share, result count and timeout.

About these screenshots

Captured from Nexus. Identifying context is outside the frame. This is a new, unsaved XML feed. The provider URL is a placeholder and the numbers are editor defaults. Detection and format support depend on the configured provider integration.

Explore targeting and operating controls in Resources ↗

What the audience sees

Contextual advertising and domain monetization

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.

Illustrative placement · no customer data

Part of your Nexus

One product. A wider operating platform.

Your white-label platform ↗

Your brand, domains and partner experience, with deployment scope agreed up front.

Connected AI + MCP ↗

Connect supported AI clients through an identity-aware setup and inspect the available tools.

Engineering and support ↗

Server management, integrations and custom development around your platform.

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.

Make it concrete

See XML feeds in your workflow.

Bring your use case, partner integrations and expected volume. We will map the relevant controls.

Book a walkthrough ↗