Reporting & reconciliation

Find the signal behind the total.

A request, a reported impression and a partner-confirmed result are different things. Nexus gives each channel its own reporting vocabulary, with breakdowns that help you investigate traffic, delivery and commercial performance.

  1. 01Choose a channel
  2. 02Select a date range
  3. 03Break down the result
  4. 04Compare partner NET

Inside the workflow

Practical controls.
A clearer working day.

Explore the settings and reports behind the headline, then review the configuration your deployment needs.

01

Channel-specific measures

Search coverage, XML valid requests, RTB win rate, video completion and CPA conversions answer different questions. Work with the measures relevant to the product you operate.

02

Dimensions with a purpose

Investigate results by the source and request attributes available in each report. The breakdown may be a search keyword, an RTB bundle or a video application environment.

03

Partner NET reporting

Search, XML and RTB administration expose partner NET reporting fields. Configure the supported provider adapter and its update settings before comparing local and partner-reported results.

04

Your working report

Report templates and a column chooser let operators arrange the available fields for their routine analysis. CSV export is available in the reporting interface.

05

A separate financial overview

The financial dashboard provides background snapshots on a five-minute cycle. It is an overview, not a promise that every partner feed or channel metric refreshes at that interval.

06

From exceptions to investigation

Requests with errors, invalid traffic and differences between local and NET figures give the team a starting point. Review the relevant partner and configuration before changing delivery rules.

Inside Nexus reportingCapability guide · no account data
Choose columns · save report templates · export CSV. Report availability follows enabled modules and account access.

A day in the platform

From setup to a decision.

A practical workflow for your reporting operation, with the relevant controls at each step.

  1. 01

    Start with the question

    Choose the channel and report: publisher, affiliate, feed, exchange, demand, video or offer performance.

  2. 02

    Set the context

    Select the period, relevant account or source and the available report dimensions.

  3. 03

    Inspect the difference

    Compare volume, delivery and commercial fields. Keep local counts and partner NET figures distinct.

  4. 04

    Keep a useful view

    Arrange columns, use a report template or export the available report for further analysis.

Reporting that fits the channel

Know what to review.
Know where to look.

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

Explore reporting & data freshness ↗

Performance indicators

  • Requests
  • Valid / invalid traffic
  • Clicks
  • Revenue
  • Cost / spend
  • Profit
  • Partner NET

Ways to break it down

Channel-specific reports · Date range · Account / partner · Source identifiers · Traffic attributes

Deployment scope. Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.

Know before you launch

Useful distinctions.
Clear expectations.

Good operations start with a shared understanding of what is configured, what is measured and what needs validation.

Local versus NET
Local figures describe the platform’s recorded activity. NET fields are the corresponding measures obtained through a configured partner reporting integration. Do not treat the two as interchangeable.
Coverage versus conversion
Coverage describes a delivery-related measure in a channel report. A conversion represents an outcome in the performance workflow. Read them in their own product context.
Useful comparisons
Compare like-for-like periods, partners, currencies and report dimensions. Confirm the provider update window before investigating a discrepancy.

The connected operation

Keep the rest of the workflow in view.

See it with your team

Bring the report you wish you had.

We will map your questions to the available channel reports, provider integrations and any additional development required.

Plan your demo ↗