Overview
An ecommerce performance dashboard gives an ecommerce marketing lead one place to review trading KPIs, target variance, product notes, and the actions that need owner follow-up.
This playbook replaces the usual weekly shuffle between an ecommerce KPI spreadsheet, a separate dashboard view, and trading-meeting recap notes that drift out of sync. Juno starts with the latest metrics you provide in the workspace, then keeps the dashboard and Metric history table together.
It does not pretend to pull every order, analytics, ad, or Shopify number automatically. The default workflow is useful with pasted metrics, uploaded exports, existing workspace tables, storefront context, or manual owner updates, and it labels stale or missing inputs directly.
Why you should keep ecommerce trading reports in one place
Ecommerce trading reviews move fast because the same revenue movement can mean different things. Revenue might be up because traffic rose, conversion improved, average order value changed, or one product category had an unusual week.
Shopify's marketing performance docs show how common this KPI mix is: store teams review sales, sessions, average order value, conversion rate, and channel results in the same reporting area (Shopify Help Center). The hard part is not naming the metrics. It is keeping definitions, targets, freshness, evidence, and actions attached to the same review.
GA4 has a similar lesson for ecommerce reporting: Google recommends ecommerce events for online sales and notes that these events need extra context, so they are not sent automatically (Google Analytics Help). That makes source caveats part of the operating workflow, not a footnote.
Juno gives the recurring trading review a clean home. The Metric history table preserves period-by-period context, the dashboard makes the current state scannable, and the notes turn metric movement into a practical conversation for the next review.
Step-by-step
- 1Confirm the store or brand, store URL if available, reporting period, currency, KPI definitions, starter values, targets, and whether the workspace should run once, weekly, or monthly.
- 2Set up the installed ecommerce workspace with a Metric history table and responsive ecommerce performance dashboard.
- 3Load the latest user-supplied metrics from pasted updates, uploaded exports, existing workspace tables, storefront observations, or other supplied files, then record the source and freshness for each period.
- 4Compare revenue, orders, conversion rate, AOV, traffic, acquisition, retention, and product or category notes against targets or prior context where available.
- 5Refresh the dashboard so the ecommerce marketing lead can scan what is on track, what is at risk, what is missing, and which owner needs to act next.
- 6Update the dashboard with the main changes, risks, open data questions, and recommended next actions for the next ecommerce review.
Frequently asked questions
Does this connect to Shopify or analytics automatically?
No. This playbook uses default Juno capabilities and the latest metrics supplied in the workspace. Source-specific automation can be added later, but the default replacement is a durable trading-report workflow, not a connector bundle.
What metrics should I include?
Start with the KPIs your ecommerce team already discusses: revenue, orders, conversion rate, AOV, traffic, acquisition, retention, product or category notes, targets, variance, evidence, and owner actions.
How does the dashboard handle stale data?
Each period carries a freshness status and evidence note. Missing, delayed, manual, partial, or low-confidence values stay visible in the dashboard.
When should this run?
Use it weekly for trading meetings and monthly for a broader ecommerce performance review. Leave cadence as run-once while the team is still agreeing on KPI definitions and targets.