Partner connections
Manage advertiser feeds and publisher mappings. Connect each source to the demand and commercial terms you choose.
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.
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.
- 01Publisher request
- 02Filters & limits
- 03Eligible advertiser feeds
- 04Click & revenue reports
Build with
Your Nexus components
Inside the operation
What your team
can manage.
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 revenue & partner NET reporting
XML revenue and partner NET trends with referral and audience breakdowns. Values are shown as captured for the selected period, not a performance guarantee.
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 ↗Related deployments
Another way to build.
01Existing module workflow
Monetize search intent
Search syndication platform
Search activity & partner filters
Searches, NET searches and clicks, with publisher, link, advertiser and feed filters. Values are shown as captured for the selected period, not a performance guarantee.
Build a PPC search advertising network. 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
RTB traffic & trading results
Requests, valid requests, impressions, clicks, revenue, spend and profit in the RTB workspace. Values are shown as captured for the selected period, not a performance guarantee.
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.