NEXUSAD PLATFORM

Performance traffic

Direct links for XML traffic

A publisher link routed through XML demand to a configured destination. Route publisher traffic through the XML / JSON module and inspect click results.

IN PRACTICE

A simple example.

A visitor follows an approved publisher link. The configured XML demand route selects a destination, while the platform records the traffic and click reporting context.

Where it appears
Approved links and calls to action
What to measure
Requests · clicks · revenue

Tracking path / Nexus fit

How Nexus
supports this workflow.

XML ad network ↗

What Nexus provides

Direct link support is available in the XML / JSON module, with publisher traffic routing, configured demand destinations, source controls and click reporting.

What you need to connect

Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path.

DEPLOYMENT FITDirect link support is available in the XML / JSON module

Exact format support, enforcement and reporting depend on the connected revenue engine and agreed deployment configuration.

XML routingA publisher link enters the configured XML demand workflow.
Format independentA permitted publisher placement can link to the destination.
Click reportingInspect source activity and the results recorded by XML reports.

Plain-language definition

What is direct link advertising?

A direct link routes publisher traffic through the XML / JSON module to a configured demand destination. It defines a traffic path rather than a visual creative. Source rules, destination configuration and click reporting remain part of the XML workflow.

WHERE IT APPEARS

Placements

  • Approved publisher links and calls to action
  • Configured XML demand destinations using agreed traffic sources
HOW IT IS BOUGHT

Buying models

  • Partner-agreed XML traffic commercial terms
  • Platform capacity is billed separately under the XML plan
HOW ELIGIBILITY CHANGES

Targeting signals

  • Supported XML country and device rules
  • Publisher approval and feed eligibility
  • Request and click controls

Delivery path

From opportunity to measurable outcome.

The exact services differ by format, but every useful implementation keeps eligibility, delivery and evidence connected.

01Publisher link→
02XML routing→
03Eligible demand→
04Configured destination→
05Click & source reporting

Measurement

Metrics that explain more than volume.

Use these metrics to evaluate the format. They are not a promise that every Nexus integration supplies every metric: player, publisher, analytics or conversion reporting may be needed.

Requests

Inspect traffic entering the configured XML route.

Clicks

Review clicks associated with the publisher and demand source.

Revenue

Compare recorded XML results and configured partner reporting.

Operator guide

What clients should understand before launch.

01

What the visitor sees

The original publisher link or creative, followed by the configured demand destination. The link does not define the visual design of either page.

02

How Nexus tracks the result

The XML route keeps the publisher, demand and destination context with the recorded traffic. Use the XML reports to review clicks and commercial results.

03

What must be agreed

Allowed publisher sources, XML demand configuration, destination behavior and partner commercial terms.

04

Direct link is not popunder

A direct link does not itself open a background browser window. Popunder behavior requires a separate permitted placement and browser-compatible implementation.

Frequently asked

Questions about direct link.

Strictly, it is a delivery and tracking path. It is included in this guide because operators commonly evaluate direct-link traffic as a channel.

Build the right delivery path

Connect format, targeting, traffic policy and commercial evidence.

Talk to an AdTech expert ↗