Analytics / Improvement

Shopify Analytics session measurement improved
Session metrics move to a new baseline starting 2026-09-21

Default session views now focus on human visitors, and bot/system traffic is classified more consistently. Legitimate shopping activity without a standard page view still appears. Session counts and conversion rates may look different, but orders, sales, and customer counts are unchanged.

On this page
  1. What's changing? (30-second overview)
  2. How it works: 3 key improvements
  3. Metrics that will look different vs. metrics that won't
  4. Before vs. after
  5. Comparing reports across 9/21 (3 steps)
  6. 5 key points for developers
  7. 3 practical use cases
  8. One-line summary for proposals

1What's changing?

Starting September 21, 2026, Shopify Analytics session views will reflect actual shopper behavior more cleanly .
As a result, session-based metrics such as session count and conversion rate may look different .

Numbers may look different

Metrics that use sessions as a denominator or unit, such as sessions, conversion rate, add-to-cart rate, and bounce rate, may look different after the update.

Actual performance hasn't changed

The announcement states that this does not necessarily mean traffic, orders, or customer behavior has changed. Orders, sales, and customer counts are unaffected by this update.

2How it works: 3 key improvements

Store traffic Human visitors Bots / system Shopping activity without page views ① Default view focuses on human visitors Where the "Human or bot" filter is available, the default is set to human ② More consistent bot/system classification Reduces inconsistency in identifying bot/system traffic ③ Legitimate activity without page views is retained Valid shopping journeys still appear even without a standard page view Clean Session baseline = New baseline
① applies only where the "Human or bot" filter is available . Which reports support the filter, the specific bot-detection logic, and concrete examples of behavior that doesn't include "standard page views" arenot stated in the article.

3Metrics that may change vs. metrics that won't

May look different (9 session metrics)

Sessions
Conversion rate
Add-to-cart rate
Reached checkout rate
Checkout conversion rate
Bounce rate
Pageviews per session
Online store visitors
Searches

Unchanged by this update

No impact

Orders

Order counts aren't affected by the session measurement update.

No impact

Sales

Sales figures remain directly comparable.

No impact

Customer counts

Customer counts don't change either.

Whether each metric willgo up or down, and roughly by how much, isnot stated in the article. It only says they "may look different."

4Before vs. after the update

ItemBefore 2026-09-21From 2026-09-21
Default session view — Human-focused Focuses on human visitors where the Human or bot filter is available
Bot/system classification Inconsistent More consistent Classified more consistently
Purchase behavior without page views — Still shown Continues to be shown as valid journeys
Session metrics Old baseline New baseline Use caution with before/after comparisons
Orders, sales, and customer counts No change Directly comparable before and after

5How to compare reports that span 9/21 (3 steps)

1

Check whether the period spans 9/21

If the comparison period includes 2026-09-21, the baseline for session metrics has changed.

2

Split metrics into 2 groups

Read session metrics (new baseline) separately from orders, sales, and customer counts (unaffected).

3

Treat it as a new baseline

As the article instructs, treat session metrics from 9/21 onward as a new baseline when comparing periods.

No merchant setup required(The article lists no setup steps, so Shopify applies this automatically.) All you need to do is adjust how you read the numbers.

65 key points for developers

9/21

1. 9/21 is a measurement discontinuity

Session metric time series may show a step change. Adding a "measurement change" annotation to dashboards and weekly reports helps prevent false anomaly alerts and misguided decisions.

Orders Sessions

2. For rate metrics, only the denominator moves

Metrics like CVR use sessions as the denominator. Since order counts (the numerator) don't change, a shift in the rate may come from the denominator's definition change rather than actual traffic.

3. Behavior differs depending on the Human or bot filter

The focus on human visitors applies only where the filter is available. You'll need to check each report in the admin to confirm what it covers (no list of affected reports is provided).

4. Journeys without page views are still counted

The article states that valid purchase journeys without standard page views will continue to appear. This isn't simply a change where bot exclusion lowers the numbers (the direction of change isn't stated).

SHOP GA4

5. The gap with external analytics tools may change

Because figures in external tools such as GA4 are not affected by this update,the gap with Shopify Analytics may shift around 9/21. If you monitor this gap, it's safest to reset your comparison baseline to the period after 9/21. How this is handled in the API / ShopifyQL isnot mentioned in the article.

73 practical use cases

9/21
USE CASE 1

Get ahead of "why did the numbers change?" questions in monthly and weekly reports

Challenge
In regular client reports, CVR and session counts suddenly shift in late September, prompting questions like "Is this from our campaign? An outage?"
Action
Add a 2026-09-21 annotation line to time-series charts in reports, with a standard note: "Session metrics use a new baseline; orders, sales, and customer counts are unaffected."
Impact
Prevents misattributed root-cause analysis and unnecessary investigation, and keeps your reports trustworthy.
Technical note
For before/after comparisons, focus on orders, sales, and customer counts; compare session-based metrics only within the period from 9/21 onward.
Orders Sales CVR Sess
USE CASE 2

Reset KPI targets and alert thresholds

Challenge
You've set KPI targets and anomaly-detection thresholds for CVR and bounce rate, but if you keep running them on the old baseline, goal checks and alerts will misfire.
Action
Review the 9 metrics listed in the article → recalibrate targets and thresholds once enough data from 9/21 onward has accumulated. Until then, make decisions based on order- and sales-based KPIs.
Impact
Eliminates the risk of making wrong decisions based on "apparent improvements or declines" caused by the measurement change.
Technical note
The article doesn't specify how long an observation period is needed before recalibrating. Decide this internally, taking seasonality into account.
Before (A/B) After (A/B)
USE CASE 3

Adjusting impact analysis for initiatives that span 9/21

Challenge
You released a redesign or theme change in mid-September and plan to measure its impact by comparing CVR before and after.
Action
Don't use before/after comparisons of session-based metrics to judge impact; evaluate using order count, sales, and customer count instead. If you want to use CVR, redesign the comparison to stay within the period from 9/21 onward.
Impact
Avoids confusing the measurement change with the initiative's impact, keeping your proposals and reports on solid ground.
Technical note
If multiple changes overlap in the same period, annotate both the release date and 9/21 on your dashboards.

8One-line summary for proposals

"Starting 2026-09-21, Shopify Analytics session measurement was refined to focus on human visitors.
The 9 session-based metrics, including CVR, now have a new baseline; orders, sales, and customer counts are unaffected.
Don't read comparisons that span 9/21 as 'a change in the numbers = a change in reality.'"