NEXUSAD PLATFORM
Sign inBook a demo
← All platform solutions

Connect traffic sources to advertiser feeds

XML ad network

Run an XML / JSON feed monetization platform. Connect advertiser feeds, assign them to publishers and control how traffic is filtered, routed and monetized.

Discuss this platform ↗See how it works ↓

Existing module workflow · For feed operators, traffic networks and monetization teams.

How it works

From your partners
to a working operation.

A traffic network connects several publisher sources to selected advertiser feeds, caps each source and compares partner-reported revenue with its own recorded clicks.

  1. 01Publisher request
  2. 02Filters & limits
  3. 03Eligible advertiser feeds
  4. 04Click & revenue reports

Build with

Your Nexus components

Inside the operation

What your team
can manage.

Partner connections

Manage advertiser feeds and publisher mappings. Connect each source to the demand and commercial terms you choose.

Traffic decisions

Configure bids, QPS, click limits, budgets and supported geo, device, domain and sub-ID rules. Inspect rejected traffic instead of treating every request as sellable.

Revenue visibility

Review feed and affiliate statistics. Compare local results with imported partner NET figures and use the XML dashboard to investigate differences.

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

Before launch

What you need
to connect.

  • Publisher traffic and advertiser feed agreements
  • Request parameters, response formats and tracking contracts for each partner
  • Traffic volumes, quality policy and reporting responsibilities

Formats & delivery

What can the
visitor actually see?

Explore relevant formats and traffic models. Delivery still depends on the selected module, publisher placement and partner integration.

Contextual & domain

See how page content, site approval, keywords, categories and parked-domain templates create structured intent for relevant advertising delivery.

How it works ↗

Popunder / CPV

Learn how popunder traffic opens a destination behind the active browser window, how CPV delivery is counted and why browser, frequency and quality policy matter.

How it works ↗

In-page Push

See how notification-style ads appear inside a webpage and how selected Nexus feed adapters connect them to compatible publisher placements.

How it works ↗

Direct Link

Route publisher traffic through Nexus XML / JSON demand and configured destinations, with source controls and click reporting.

How it works ↗

Evaluate your platform

Plan your XML / JSON ad network

Bring one publisher source and one advertiser feed to your demo. We will review the mapping, traffic limits and reporting you need, then identify adapter work and capacity requirements for your XML / JSON network.

What to review in your demo

  1. Connect a provider

    Review the feed adapter, request parameters, response format and SubID mapping for your advertiser partner.

  2. Set traffic policy

    Walk through publisher assignments, targeting, minimum bids, QPS limits, daily budgets and click caps.

  3. Reconcile reporting

    Compare local clicks and XML revenue with imported partner NET figures for the same reporting period.

  4. Prepare a deployment brief

    Bring a short brief with five items: traffic sources and placements; approximate peak QPS and daily clicks; target countries and devices; CPC, CPA or other commercial model; and required provider integrations. Name existing feed agreements and the reports or controls you need. Redacted request and response samples help assess compatibility; keep credentials and personal data out of the enquiry form.

Request this platform demo ↗

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.

Compare revenue and partner NET figures

Actual Nexus dashboard · original captured values. XML revenue and partner NET trends with referral and audience breakdowns. Values are shown as captured for the selected period, not a performance guarantee.

Capacity, setup and running costs

XML / JSON feeds costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations. Each 1,000 incoming QPS block has a maximum of 10,000,000 clicks per day for this module in this location; 2,000 incoming QPS allows a maximum of 20,000,000 clicks per day. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus.

One-time setup: $1,500 per platform, separately from monthly capacity and selected add-ons.

Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised.

Calculate capacity and first-month cost ↗

Before you choose a platform

What if our offers pay on CPA but we buy traffic on CPC?

State both models in your demo brief and explain how conversions are reported back. We need to review the conversion identifier, source or SubID mapping, attribution window and reconciliation process. Keyword-level bidding, source-level controls, automatic optimization and bid API access must be confirmed for the proposed integration; do not assume they are included.

What should I include in an XML platform enquiry?

Tell us whether you are launching or migrating, which traffic types and provider feeds you already have, and your approximate peak QPS and daily clicks. Name the controls or reporting gaps you want to solve. These details help scope a relevant demo; never include API keys, passwords or raw user data.

Does the platform include advertiser demand?

You bring publisher traffic and advertiser feed agreements. Nexus supplies the software to configure those relationships; partner approval, traffic acceptance and commercial terms are agreed with each provider.

Can we migrate an existing XML network?

Begin with an inventory of feeds, publisher mappings, tracking parameters and reporting definitions. Validate a representative partner connection, reconcile the results and agree on a staged cutover and rollback plan.

What determines the launch date?

Feed access, adapter compatibility, branding, capacity and acceptance testing determine the schedule. Share your current setup so we can agree on the work and timeline before launch.

Related deployments

Another way to build.

Compare all platform types ↗
01Existing module workflow

Monetize search intent

Search Syndication

Search SyndicationWorkflow
01 / Search queryPublisher
02 / NexusMatch & route
03 / Eligible feedProvider
A search does not guarantee a monetized result or click. Provider responses and NET imports depend on the integration.

Run a search syndication platform. Connect search providers to publisher links, apply keyword and traffic rules and compare searches, clicks and partner results.

See this platform ↗
02Existing module workflow

Connect supply and demand partners

OpenRTB exchange & traffic hub

OpenRTBWorkflow
01 / Bid requestSupply
02 / NexusQualify & route
03 / Eligible partnersDemand
A bid response is not an impression or confirmed revenue. No eligible bid is also a possible outcome.

Operate the connection between programmatic supply and demand. Manage exchanges, demand access, inventory rules and trading reports from the OpenRTB workspace.

See this platform ↗

Plan your deployment

See this workflow
with the Nexus team.

Pricing depends on modules, traffic, integrations and support. Tell us what you want to operate and we will prepare a relevant demonstration and proposal.

Request a tailored demo ↗