Platform  Microsoft Power BI

Spend on the traffic that converted, not the traffic that looked busy

Allocate cost per source and per affiliate, compare it against conversion results, and see which channels are actually paying for themselves — delivered as Power BI dashboards built on your own warehouse.

Five machined metal cylinders of differing heights on a milled plate, one of them shorter and matte black — the source that is not paying its way.

A decision-support tool, not an autopilot

This shows your traffic team where money is going and what it’s returning, and alerts them when a slice starts underperforming. It does not stop or reallocate spend on its own — that call stays with the people accountable for it.

It does

  • Allocate traffic cost down to source and affiliate
  • Match conversion results against that cost
  • Alert when a slice improves or deteriorates

It does not

  • Stop, pause or reallocate traffic spend
  • Change bids or budgets automatically
  • Make the call your team is accountable for

Every source looks busy. The question is which ones pay back.

Traffic cost arrives in one shape — invoices from agencies, platform spend, payout obligations. Conversion results arrive in another, from different systems on a different clock. Between the two sits the only question that matters at scale: per source, per affiliate, did this traffic return more than it cost?

The tool holds both sides in one model — cost allocated down to source and affiliate, conversions matched against it — so the answer is a dashboard, not a quarterly project.

Cost vs return by source cost return indexed · cost = 100 = break-even · illustrative 0 50 150 100 +38% +61% −22% +42% +18% src A100 → 138 src B100 → 161 src C100 → 78 src D100 → 142 src E100 → 118 src C returning less than it costs — flagged for review

Grey is cost, colour is return, per source. A stylised illustration of the comparison the tool makes — not a product screenshot, not client data.

Cost arrives as

  • Agency invoices
  • Platform spend
  • Payout obligations

Conversions arrive as

  • Results from different systems
  • On a different clock

Held in one model

Both sides on the same row, per source and per affiliate.

What lands on your desk

Delivered to the traffic team, on your own warehouse

Cost per source, per affiliate

Traffic spend allocated to the level where decisions actually happen.

Movement alerts

Notifications when a specific slice improves or deteriorates — before the month-end review would have caught it.

Analytics-grade allocation

Cost distributed for project and product analytics, from data processed and enriched across your sources.

Report templates included

Built-in Power BI templates for marketing-effectiveness analysis — a starting point your analysts extend, not a black box they fight.

Questions

Does it change bids or budgets automatically?

No. It analyses and alerts. Spending decisions stay with your team.

Do we need our own Power BI?

It’s built on Microsoft Power BI connected to a warehouse on Miraxtech templates — the same Microsoft stack the other Miraxtech products are built on.

Where does the data come from?

From a SQL Server warehouse built on Miraxtech templates, fed through Integration Gateway or your own data feeds — cost and conversion sides held in one model.

See what your traffic data would show

Analysis and alerts. Budget decisions stay with your team.