Every number above is computed live from the filtered daily records — change the range, channel, or conversion definition and they all recompute. Attributed revenue uses a $94 blended average order value in this demo.
Budget pacing
This month, per channel: budget vs. spent so far, projected to month-end at the current pace.
Campaigns — all channels
Spend, leads and cost per lead for the selected range, using the conversion definition chosen above.
| Campaign | Channel | Spend | Leads | Cost / lead | Status |
|---|
Demo controls
Restore the original sample series and default filters.
How to read this
The discipline behind every number on the dashboard.
Platform-reported conversions and confirmed sales are kept separate, always. Ad platforms count conversions with their own attribution windows and modelled estimates; the sales system (CRM) counts orders that actually landed. The confirmed number is deliberately lower — that gap is normal, and it is information, not an error.
The “Count conversions as” toggle switches the whole dashboard — leads, cost per lead, attributed revenue and ROAS — between the two definitions. The two numbers are never averaged, summed, or blended into a single “true” figure, because there isn't one: there are two measurements answering two different questions.
Platform-reported answers “what did the channel claim it drove?” — useful for judging the channel's own optimisation. Confirmed sales answers “what can the business actually bank on?” — the number budgets should be set against.
Budget pacing is independent of the toggle: it tracks spend against the monthly budget and projects month-end at the current daily pace, flagging any channel projected to overspend before it happens.
All data on this page is fictional sample data generated deterministically in the browser for this demo.