Analytics overview
Open the right store report, choose a period, and check the evidence behind traffic and sales changes.
Analytics helps you connect recorded visits, shopping activity, and sales for the selected store.
Entry path
Open a store project → Measure → Analytics.
English callouts highlight the controls. Select the image to enlarge it.
The single-page Analytics layout in a tutorial store with no recorded activity. The Alpha diagnostics illustration is not evidence of a store issue.
Before you start
- Your plan must include the reporting surface. A plan preview does not show your measured store results.
- A published store and recorded shopper activity are needed for meaningful traffic and sales reports.
- Select the same store, period, and filters when comparing reports.
Choose the layout you see
If your screen shows Net Sales, GMV, Sessions, and Conversion Rate above a single scrolling page, follow the earlier dashboard instructions below. If it shows grouped report navigation, use the workbench instructions that follow. The two layouts have different controls.
Choose a report
Conditional: If your screen shows Storefront analytics, use the grouped workbench below. Some workspaces still show the earlier single-page dashboard described later.
| Control | What it opens |
|---|---|
| Overview | A summary of the selected store’s activity. Use an available See details link to inspect the underlying report. |
| Commerce | Commerce, funnel, product, acquisition, and goal reports. |
| Behavior | Page, event, journey, and other supported browsing reports. |
| Audience | Visitor, user, segment, and trait reports. |
| Live page | The available live activity view. |
| Configure | Tracking and other analytics configuration tools. Opening it does not create events. |
| Date selector | Refreshes the selected report for the chosen period. |
| Compare, when shown | Adds the supported comparison period. |
Review your first report
- Open Overview and confirm the selected store.
- Choose a period that contains known store activity, such as 7d or 30d.
- Read the visible summary, then open Commerce to inspect sales and funnel data.
- Open the relevant subreport for the question you need to answer. For example, compare funnel stages before inspecting a suspected checkout problem.
- Open Behavior to inspect an affected page or journey when those reports have data.
- Return to Overview to compare the detail with the summary.
Checkpoint: You can identify the report, active period, and events behind a result. An empty report confirms neither working event collection nor a broken store.
If you see the earlier dashboard
Use its time-range selector, then read Net Sales, GMV, Sessions, and Conversion Rate together. Scroll to product, source, funnel, abandonment, and refund sections. The earlier Site Diagnostics Alpha card is a preview without supporting store-specific issue details; use report or storefront evidence before changing a page.
Troubleshooting
| State | Next step |
|---|---|
| Dash, zero, or empty chart | Clear optional filters, try a longer period, and confirm actual visits or orders exist. |
| Upgrade notice or plan preview | Review access in Plan & Billing before diagnosing collection. |
| Report is loading | Wait for its request to finish before changing filters again. |
| One report has data and another does not | Check the event each report needs. Visits can exist before orders. |
| Report cannot load | Reload once and preserve the report name, period, and error if it fails again. |
| Navigation entry missing | Expand Measure and confirm the selected workspace. See Feature availability. |