Playbook
Shopify Analytics Dashboard: Turn Metrics Into Decisions
A Shopify analytics dashboard shows sales and traffic. Learn which metrics matter, how to diagnose product health, and what decision each signal supports.
Time to read
14 minutes
Requires
Shopify orders, catalog, traffic, inventory, and cost data where available
Outcome
A short list of product decisions, data gaps, and next checks
What is a Shopify analytics dashboard?
A Shopify analytics dashboard is a customizable set of metric cards for monitoring a store's sales, sessions, customers, products, inventory, and fulfillment. Each card answers a narrow question, such as how much net sales changed or whether conversion rate moved, and opens into a report for deeper analysis. The dashboard is the monitoring layer. A useful review turns those measurements into a decision: protect stock, fix a product page, support a hidden seller, change an offer, or investigate a data gap.
Start with a business question, choose a matching date range and comparison period, then read the metrics in sequence. Revenue tells you the size of the change. Orders and average order value separate purchase volume from basket value. Sessions and conversion rate separate traffic from store efficiency. Product, margin, inventory, and return data locate where the change came from and whether acting on it would improve profit rather than only sales.
Which Shopify metrics should be on the dashboard?
For a weekly operating view, keep net sales, orders, average order value, sessions, online-store conversion rate, sales by product, inventory risk, and returning-customer behavior close at hand. Add a metric only when someone can name the decision it supports. A card that never changes a decision is decoration.
Dashboard, report, diagnosis, and automation are different layers
A dashboard monitors a small set of indicators. A report lets you filter and group the underlying data. A diagnosis connects changes across metrics and locates a likely cause. Automation watches for a defined condition and prepares or executes the next step. Confusing the layers creates two common failures: expecting a chart to explain itself, or letting a rule act before the cause is known.
Shopify's native Analytics overview is the right starting point for store-wide monitoring. Its metric cards can be rearranged, compared across periods, and opened into detailed reports. A separate analytics or automation layer earns its place only when it reduces the work between seeing the number and making a sound decision.
| Layer | Question it answers | Typical output | Main risk |
|---|---|---|---|
| Dashboard | What changed? | Metric cards and trends | Too many cards hide the signal |
| Report | Where did it change? | Filtered table and visualization | Averages can hide product or channel outliers |
| Diagnosis | Why might it have changed? | Ranked causes, confidence, and missing data | Correlation can be presented as causation |
| Automation | What should happen next? | Alert, draft, approval, or action | A bad rule can repeat a bad decision |
Keep all four layers, but give each one a separate job. The dashboard should surface the change. The diagnosis should explain the evidence. The action should state its assumptions and approval boundary.
How to review a Shopify analytics dashboard
Use the same sequence every time so a dramatic card does not pull the review off course. First, lock the date range and comparison. A seven-day period should be compared with an equal seven-day period unless seasonality makes the same period last year more useful. Second, locate the commercial change in net sales, orders, or contribution. Third, split the change into traffic, conversion, and basket value. Fourth, drill into products, inventory, and customers. Last, check whether discounts, sales reversals, channel mix, or incomplete cost data change the interpretation.
Shopify's native overview can update quickly, but freshness does not make a short window reliable. A one-day conversion spike on twelve sessions carries less evidence than a smaller move across hundreds of sessions. Write the sample beside the rate. If the denominator is small, keep the conclusion directional and wait for more data before changing the store.
| Review step | Read | Question | Possible next drill-down |
|---|---|---|---|
| 1. Frame | Date range and comparison | Are these periods genuinely comparable? | Day, week, month, or same period last year |
| 2. Size | Net sales and orders | Did value change because of order count or order value? | Sales by product, channel, discount, or market |
| 3. Funnel | Sessions and conversion rate | Is the issue traffic volume, traffic quality, or store conversion? | Device, landing page, product page, cart, and checkout |
| 4. Basket | Average order value and units per order | Are customers buying less per order? | Product pairs, discounts, and merchandising |
| 5. Product | Revenue, PDP CVR, inventory, and cost | Which products created the movement, and are they healthy? | Hero, hidden gem, traffic leak, margin trap, or stock risk |
| 6. Quality | Returns, reversals, attribution, and missing fields | Would the conclusion survive a data-quality check? | Source report, connector status, or longer window |
A weekly review should end with no more than three decisions. Keep the rest as observations or questions. A long action list usually means the review has not ranked impact yet.
A product health model for Shopify analytics
Store averages are useful for orientation and weak for merchandising. A stable store conversion rate can hide one popular product page that leaks demand and one lightly visited product that converts unusually well. Product health needs sales, product-page behavior, margin evidence, and inventory in the same view.
One workable model separates mature products into five operating groups. Heroes combine strong revenue with healthy available margin and product-page conversion. Mid-tier products sell but have not reached the top group. Long-tail products contribute less and should not automatically receive paid support. Problem products carry a negative margin or materially weak product-page conversion. Dead products hold inventory without sales. Products younger than 30 days stay outside the classification because a launch needs time to collect evidence.
| Group | Evidence | Decision to consider | Do not assume |
|---|---|---|---|
| Hero | Top revenue with healthy available margin and PDP CVR | Protect stock and test more qualified visibility | High sales alone make scaling profitable |
| Mid-tier | Between median and top-quartile seller revenue | Support selectively or pair with a hero | Every mid-tier SKU needs paid spend |
| Long tail | Below-median seller revenue or catalog depth | Leave, bundle, feature in a roundup, or investigate a hidden gem | Low sales prove the product is bad |
| Problem | Negative available margin or weak PDP CVR with enough sessions | Fix the named issue before scaling or retiring | More traffic will solve a conversion leak |
| Dead | No sales in the analysis window with stock on hand | Review clearance, bundle, archive, or positioning options | A young launch belongs in this group |
The groups are decision aids, not permanent labels. Recalculate them as sales, traffic, costs, and inventory change, and keep the evidence behind each assignment visible.
Three worked Shopify analytics dashboard diagnoses
A diagnosis should name the category, the rate, the denominator, and the commercial decision in complete sentences. These examples use simple numbers to show the reasoning pattern. They are not universal benchmarks.
| Store signal | Diagnosis | Decision |
|---|---|---|
| Skincare: 1,800 serum PDP sessions, 0.4% CVR, catalog median 2.1%, $42 AOV | The page produces about 7 orders. Reaching the catalog median at the same traffic would produce about 38, a gap of roughly 31 orders and $1,302 in order value before returns, costs, and discounts. | Inspect product evidence, price, images, reviews, delivery promise, and checkout before buying more traffic. |
| Fashion: 4.8% PDP CVR, 220 sessions, 52 orders in 180 days, 18 units left | Conversion is strong while visibility and stock are both constrained. At 0.29 units per day across the full window, simple cover is about 62 days, but a recent acceleration could make that estimate stale. | Check a recent velocity window and unit cost before increasing exposure or promising a restock date. |
| Homeware: $96 AOV, 28% gross price-cost margin, 35% discount, 120 orders | The product may lead revenue while contributing less cash than the dashboard implies. A price-cost margin of 28% cannot absorb a 35% discount before payment, fulfillment, returns, and ad costs. | Stop calling it a hero on revenue alone. Rebuild the promotion or margin model before scaling. |
Lost-order opportunity = product sessions × (comparison CVR − product CVR)
Simple days of cover = units on hand ÷ average units sold per day
Price-cost margin % = (selling price − unit cost) ÷ selling price × 100
These formulas size an investigation. They do not forecast guaranteed revenue, demand, or profit. State every omitted input beside the estimate.
Where ecommerce automation software belongs after the dashboard
Ecommerce automation software is most useful after a metric has been translated into a bounded condition. A stock-risk rule can watch days of cover. A product-page rule can look for high traffic paired with weak conversion. A catalog rule can surface products that convert well but receive little traffic. The rule should produce a diagnosis card with the affected product, the calculation, the missing evidence, and the proposed next step.
Keep diagnosis separate from execution. A low conversion rate can justify opening a product-page review. It does not justify rewriting a live page without seeing the current content and approving the diff. A strong seller can justify a scale candidate. It does not justify higher ad spend until cost and inventory are known. Automation earns trust by narrowing the next decision and preserving the approval boundary.
| Signal | Safe automated output | Approval-gated follow-through |
|---|---|---|
| High PDP traffic, weak CVR | Ranked leak with lost-order estimate | Product copy, image, price, or storefront change |
| High CVR, low traffic | Hidden-gem alert with evidence | Collection placement, organic feature, or paid campaign |
| Low stock on a strong seller | Days-of-cover and revenue-risk warning | Reorder, backorder policy, or ad pause |
| Inventory with no sales | Dead-stock list and capital exposure where cost exists | Clearance, bundle, archive, or merchandising change |
The safe progression is monitor, diagnose, propose, approve, execute, then measure again. Removing a step saves time only when the evidence and downside are both understood.
Where Shopify competitor analysis fits
Shopify competitor analysis adds context that first-party analytics cannot supply: assortment depth, visible prices, promotions, merchandising, public bestsellers, and storefront changes. It can explain why a category deserves investigation or reveal an offer pattern worth testing. It cannot reveal a competitor's conversion rate, margin, customer acquisition cost, inventory position, or internal demand.
Keep first-party and competitor evidence in separate columns. Your Shopify data can show that a product page converts poorly. Public competitor data can show that competing pages lead with different proof, pricing, or bundles. The combination supports a hypothesis for a controlled change. It does not prove that copying the competitor will improve the store.
Use competitor evidence to widen the option set, then validate the decision against your own margin, customers, stock, and conversion data.
What metrics should a Shopify analytics dashboard track?
Each metric below answers one part of the operating model. Read them as a chain and keep the denominator visible for every rate.
Net sales
Net sales is gross sales minus discounts and sales reversals. It is a better revenue starting point than gross sales when adjustments are material.
Use it to size the commercial change, then split it by product, channel, market, or discount to locate the driver.
Orders
Orders counts completed order records in the selected scope and period.
Use it with net sales to tell whether revenue changed because more people ordered or because each order was worth more.
Average order value
Average order value is order revenue divided by distinct orders.
Use it to evaluate basket size, bundling, discount thresholds, and product-pair opportunities. Deduplicate order totals before calculating it from line-item data.
Online-store conversion rate
Online-store conversion rate is sessions that completed checkout divided by sessions.
Use it for the store funnel. Segment by device, landing page, and source before assigning the change to the storefront.
Product-page conversion rate
Product-page conversion rate measures purchases or completed conversions against sessions associated with a product page, depending on the source report's definition.
Use it with page sessions and bounce or cart-add behavior to find hidden gems and traffic-heavy leaks. Confirm the source definition before comparing it with store-wide CVR.
Price-cost margin
Price-cost margin is selling price minus known unit cost, divided by selling price.
Use it as a screening check before recommending scale or a discount. It is not full contribution margin because payment, fulfillment, returns, and acquisition costs may be missing.
Sell-through and days of cover
Sell-through compares units sold with units sold plus remaining inventory. Simple days of cover divides inventory by average daily unit sales.
Use them to separate demand problems from stock risk. Recalculate with a recent window when sales velocity is changing quickly.
Returning-customer behavior
Returning-customer metrics compare customers or orders with prior purchase history against the total in the selected period.
Use them to evaluate retention and customer mix. Do not treat a lifetime customer count stored on an order as a complete cohort analysis.
Revenue, traffic, conversion, basket, product, margin, inventory, and customer behavior form a useful minimum set. Returns and channel attribution deserve their own checks whenever they materially change the commercial answer.
Should a Shopify dashboard recommend actions automatically?
It should recommend an investigation automatically when the trigger is specific and the evidence is visible. It should not silently change a live store because one rate crossed a threshold. A low product-page conversion rate could come from the page, price, traffic source, stock, delivery promise, or a thin sample. The dashboard knows the symptom before it knows the cause.
A stronger system prepares the next piece of work. It can name the affected product, show the rate and denominator, estimate the size of the gap, list the missing inputs, and draft the change. A person can then inspect the current state, review a current-to-proposed diff, and approve the write. This keeps the analytical loop fast without pretending uncertainty has disappeared.
The Shopify analytics dashboard decision framework
Use this six-step check before turning any dashboard movement into work.
- 1
Write the business question before opening the dashboard.
A question such as 'Which mature products deserve more qualified traffic?' determines the metrics, scope, and comparison you need.
- 2
Lock a date range, comparison, currency, and denominator.
Do not compare a promotion week with an ordinary week or quote a rate without its sessions, orders, customers, or units.
- 3
Trace the store-level movement into products and funnel stages.
Separate traffic, conversion, and basket effects, then identify the products responsible for the change.
Read Shopify Conversion Rate Optimization - 4
Check margin, inventory, returns, and data coverage.
A revenue winner can lose money, a conversion winner can be close to stockout, and missing cost or return data can reverse the decision.
- 5
Choose one action and state what would disprove it.
Fix, feature, bundle, restock, discount, pause, or investigate further. Do not attach several interventions to one signal.
- 6
Record the baseline and review window before executing.
Save the current metric, denominator, assumptions, and expected decision date so the follow-up can distinguish progress from noise.
How Kluck analyzes Shopify product performance
Kluck adds a diagnostic layer to connected Shopify data. It produces saved analysis artifacts and ranked decisions rather than replacing Shopify's native Analytics dashboard.
A synced 180-day operating snapshot
Kluck can query the last 180 days of Shopify order line items, the full product catalog, product inventory and pricing, product-page sessions and conversion signals, and on-site search demand. A custom order window can be calculated from the stored order history within that range.
Five product-health groups
Products at least 30 days old are assigned to hero, mid-tier, long-tail, problem, or dead groups from revenue, units, available cost, PDP conversion, sessions, and inventory. The stored assignment is used consistently instead of being improvised for each question.
Coverage-aware analysis
Margin signals affect catalog classification only when price and cost coverage reaches at least half of active products. PDP signals are treated as catalog-wide evidence only when more than 30 percent of eligible products have traffic. Fewer than 50 distinct orders makes the analysis directional.
Named anomalies instead of a stats dump
The current analysis looks for hidden gems, traffic black holes, margin traps, and inventory risk. It leads with three to five actionable findings, then keeps the wider catalog available for drill-down.
Saved chart, table, and written diagnosis
A catalog review can save a product-group bar chart, a table of hero and problem products, and a written summary with recommendations. These are reviewable artifacts, not a permanently updating BI dashboard.
Question-led drill-down
The Brand Manager can query groups, individual products, custom order windows, customer and basket patterns, inventory, geography, and storefront search demand. It narrows the result before presenting it rather than returning the raw catalog.
Honest missing-data behavior
If costs, PDP analytics, returns, or order volume are missing, Kluck drops the unsupported conclusion and names the gap. Products newer than 30 days remain unclassified rather than being called dead or problematic.
Approved follow-through
A diagnosis can hand off to product, inventory, merchandising, pricing, organic content, or Meta campaign work. Live Shopify changes are staged as a draft or current-to-proposed diff and require approval before they are written.
Before you start
- A connected Shopify store with a completed Pulse sync.
- Enough order history for the chosen window; fewer than 50 distinct orders produces a directional catalog-health read.
- Product costs entered for any margin or scale decision. Missing cost does not stop sales analysis, but it blocks a profitability claim.
- Shopify product-page analytics available for traffic, CVR, bounce, and cart-add diagnosis.
- A specific scope: full catalog, a category, selected products, or recent launches.
Keep in mind
- Kluck does not replace Shopify's native Analytics dashboard, Live View, reports, custom data explorations, targets, or ShopifyQL editor.
- The saved catalog charts and tables are point-in-time analysis artifacts. They do not update continuously on screen.
- The product-health window is capped at the synced 180-day snapshot. It cannot answer a longer historical question from Pulse alone.
- Products created within the last 30 days are deliberately left unclassified. They are new launches, not dead or problem products.
- Price minus unit cost is a margin proxy, not complete contribution profit. Payment fees, fulfillment, returns, duties, discounts, and acquisition costs can change the result.
- Returns are not currently included in Kluck's product-health classification. If return details are unavailable, the analysis states the gap instead of estimating them.
- A product-page conversion rate and the store-wide online conversion rate can use different scopes and denominators. Confirm the source definition before comparing them.
- A high conversion rate on a small number of sessions is weak evidence. The rate must travel with its denominator.
- Revenue does not make a product safe to scale. Confirm positive economics and enough inventory first.
- Public competitor data cannot reveal a competitor's conversion rate, margin, customer acquisition cost, or inventory. Treat competitor observations as hypothesis inputs only.
- Shopify deprecated report benchmarks in May 2026. Use the store's own targets and comparable periods instead of building decisions around a retired benchmark view.
- Live product, pricing, inventory, collection, discount, and campaign changes require their own review and approval. A diagnosis does not execute them silently.
Related playbooks
Did the dashboard surface a conversion leak?
The Shopify Conversion Rate Optimization playbook separates product-page, cart, checkout, device, and traffic-source friction before choosing a fix.
Read Shopify Conversion Rate OptimizationNeed public market context for the product decision?
Competitor Price Tracking shows how to monitor public prices, promotions, assortment, ads, and positioning without pretending to know a competitor's internal performance.
Read Competitor Price TrackingDid product performance point back to the ads?
Dynamic Creative Optimization explains how to isolate one creative variable, run a controlled Meta test, detect fatigue, and keep the learning attached to the next version.
Read Dynamic Creative OptimizationSources and methodology
Platform terminology changes over time. These primary references support the category definitions; Kluck-specific thresholds and behavior come from the current product implementation.
Frequently asked questions
What is a Shopify analytics dashboard?
A Shopify analytics dashboard is a customizable set of metric cards for monitoring sales, sessions, customers, products, inventory, and fulfillment. Each card summarizes one indicator and links to a deeper report. Its job is to show what changed; diagnosis is the separate step that explains where the change came from and what decision it supports.
What metrics should I track on Shopify?
Start with net sales, orders, average order value, sessions, online-store conversion rate, sales by product, inventory risk, and returning-customer behavior. Add product-page CVR, margin, discounts, and returns when they support the current decision. Keep the denominator beside every rate and remove cards that never lead to action.
How do I analyze Shopify sales?
Choose a date range and a comparable period, then split the sales change into order count and average order value. Drill into product, channel, market, and discount data, then check traffic, conversion, cost, inventory, and sales reversals before choosing an action. This prevents a revenue movement from being mistaken for a profit movement.
What is a good Shopify conversion rate?
There is no single rate that makes every store healthy. Product mix, price, device, market, traffic source, customer mix, and the denominator all change the result. Compare the store with its own comparable periods and targets, then use product and funnel segments to find the largest actionable gap.
How do I find my best-selling products on Shopify?
Rank products by revenue or units sold for the chosen period, then add known unit cost, product-page conversion, and inventory. The sales leader is commercially healthy only when its economics are positive and enough stock remains to support more demand.
How can I find products that get traffic but do not convert?
Compare product-page sessions with product-page conversion rate across mature products. Prioritize pages with high sessions and low CVR, then inspect images, description, price, reviews, stock, delivery promise, traffic source, and checkout behavior. More traffic is usually the wrong first move for a confirmed leak.
What is the difference between Shopify Analytics and Google Analytics?
Shopify Analytics is the first-party operating view for store sales, orders, products, customers, inventory, and storefront sessions. Google Analytics is useful for broader acquisition and behavioral analysis across traffic sources and sites. Definitions and attribution can differ, so reconcile scope before comparing the numbers directly.
Can Kluck build a live Shopify analytics dashboard?
Kluck currently adds a diagnostic layer to synced Shopify data rather than replacing Shopify's live dashboard. It can save a product-group chart, a product table, and a written catalog-health analysis, then answer follow-up questions and prepare approved actions. Those saved artifacts are point-in-time reports, not continuously updating BI screens.
Does Kluck include returns in Shopify product analysis?
Not in the current product-health classification. The analysis uses orders, product revenue and units, available price and unit cost, product-page behavior, and inventory. When returns are unavailable, Kluck names the gap and avoids making a return-adjusted profitability claim.
Does Kluck automatically change products when a metric drops?
No. It can surface the affected product, calculation, likely causes, and recommended next step. A live Shopify change is staged as a draft or current-to-proposed diff and requires approval before the write occurs.
Turn the dashboard into a decision.
Ask one commercial question about your Shopify catalog.
Open Kluck, connect Shopify, and ask your Brand Manager which products are healthy, which are leaking demand, and which data gap must be fixed before acting.
Open Kluck