Revenue Dashboards
A practical guide to revenue dashboards — what to track, how often to refresh, and how to tell a decision-driving dashboard from a decorative one.
Revenue Dashboards
Curated views of revenue KPIs that operators check daily or weekly to spot anomalies and trigger action.
Revenue dashboards are the working surface where merchandisers, finance, and growth leads watch the money move — net revenue, AOV, conversion rate, refund rate, channel mix, and the funnel stages that produce them. The good ones are built around decisions: each chart has an expected range, an owner, and a response if the number breaches the range.
The bad ones are wallpaper. They look impressive in a board deck, no one opens them on a Monday, and a 30% drop in checkout conversion sits there for a week before anyone notices. The difference isn't the tool — it's whether the dashboard is wired to how the team actually runs the store.
A revenue dashboard is part of a broader revenue intelligence stack — it surfaces the headline numbers, while the underlying analytics platform explains why those numbers moved. Without that pairing, dashboards become a guessing game: you see the dip, but you can't get to the cause without opening five other tools.
The job of a daily dashboard is narrow. It should answer one question in under ten seconds: is the store on plan today, and if not, where? Anything that doesn't help answer that belongs on a weekly or monthly view — not on the screen the team checks before standup.
z = (today_value - rolling_mean_28d) / rolling_stddev_28d
today_value
Today's metric value
The KPI reading for the current day (e.g. checkout conversion rate).
rolling_mean_28d
28-day rolling mean
Average of the same metric over the trailing 28 days.
rolling_stddev_28d
28-day rolling standard deviation
Standard deviation of the same metric over the trailing 28 days.
A Shopify apparel store watches checkout conversion rate. The 28-day mean is 3.20% with a standard deviation of 0.25 percentage points. Today the rate reads 2.55%.
today_value: 2.55%
rolling_mean_28d: 3.20%
rolling_stddev_28d: 0.25pp
→ z = -2.6
A z-score below -2 is the threshold most teams use to fire an alert. -2.6 is well past it — the dashboard should flag this row red and ping the owner before more sessions are wasted.
Pick the cadence that matches the decision. Daily views catch tracking outages and checkout regressions; weekly views catch channel-mix shifts; monthly views catch cohort and LTV drift. Mixing them on one screen is how dashboards get ignored.
Typical refresh cadence and chart count by dashboard tier
| Tier | Refresh cadence | Chart count | Primary audience | Example KPIs |
|---|---|---|---|---|
| Daily ops | Hourly to 1×/day | 5–8 | Merchandising, growth ops | Sessions, CVR, AOV, checkout funnel, refund rate |
| Weekly trading | 1×/day | 10–15 | Head of e-commerce | Channel revenue, new vs returning, paid ROAS, gross margin |
| Monthly board | 1×/week | 6–10 | Founder, CFO | Net revenue, contribution margin, LTV:CAC, cohort retention |
| Campaign-specific | Hourly during flight | 4–6 | Performance manager | Spend pacing, ROAS, CPA, attributed revenue |
Most stores have too many dashboards and not enough alerts. Three well-built views — daily ops, weekly trading, monthly board — covers 90% of real decisions. Every additional dashboard splits attention and raises the chance the important one stops getting opened.
Frequently asked questions
A revenue dashboard shows what's happening — the numbers, the trends, the alerts. Revenue intelligence is the layer underneath that explains why: cohort behaviour, funnel drop-offs, channel attribution. The dashboard is the windscreen; revenue intelligence is the diagnostics.
Five to eight metrics, no more: sessions, conversion rate, AOV, net revenue, checkout completion rate, refund rate, and one or two channel-specific numbers (paid ROAS, organic sessions). If a chart hasn't triggered a decision in the last 60 days, it doesn't belong on the daily view.
Daily ops dashboards should refresh at least once an hour during trading hours, more often if you run flash sales. Weekly trading dashboards can refresh once a day. Monthly board views weekly is plenty — refreshing them hourly invites noise.
Three signs: no owner per chart, no expected range or alert threshold, and no documented response when a number breaches it. If the team can't tell you what they'd do if conversion dropped 20% on this dashboard, it's wallpaper, not a tool.
GA4 is fine for traffic and channel views but limited for revenue-level analysis — sampling, four-hour data latency on the free tier, and weak handling of refunds and discounts. Most stores past €1M move revenue dashboards into a BI tool or analytics platform that imports GA4 history plus order data from Shopify.
Start with a z-score threshold of ±2 against a 28-day rolling baseline, then tune by metric. High-variance metrics like daily ROAS need a wider band (±2.5 or even ±3). Low-variance metrics like checkout completion rate can use ±1.5. Review false-positive rate after two weeks and adjust.
Both, but on different views. The daily dashboard should split by device (mobile is usually where checkout regressions surface first). The weekly trading view should split by channel (paid, organic, email, direct) because that's where budget decisions get made.
Annotate the dashboard with a 'last updated' timestamp per data source. Shopify order data is near-real-time; GA4 has a 4–24h lag; ad platforms reconcile attributed revenue for up to 72h. Build your daily view to tolerate this — don't compare today's GA4 sessions against today's fully-attributed ad spend.
One named person per dashboard, not a team. The owner sets thresholds, triages alerts, and decides what gets added or removed. Without single-person ownership, dashboards drift — charts pile up, no one prunes, and the signal gets buried.
If you can't list every dashboard from memory, you have too many. For most stores under €15M revenue, three core dashboards (daily ops, weekly trading, monthly board) plus a campaign-specific view during major promotions is enough. Past that, you're building reports nobody reads.
See Metricuno on your data
Bring your stack — Google Analytics, Stripe, a CRM, anything — and we'll walk through the metric tree that turns your funnel into one number.