Shopify Analytics: sessions and conversion rate from Sep 21

Laptop con dashboard di analytics e visualizzazione separata del traffico umano e bot in un ambiente di lavoro e-commerce

Between September 21 and 23, 2026, Shopify is updating how Analytics measures sessions. As a result, sessions, conversion rate and other session-based metrics can change even when traffic, orders or customer behavior have not materially changed.

If you use Shopify Analytics to compare periods, campaigns or optimization work, September 21 should be treated as a measurement break. A direct before-and-after comparison can attribute a change to the business when part of it actually comes from the new measurement method.

What changes in session measurement

Shopify introduced three main changes. First, continuous customer activity no longer ends automatically at midnight UTC. A session ends after 30 minutes of inactivity.

Second, some valid journeys without a standard pageview can now be counted, for example when a customer goes directly to checkout from a cart link.

Third, identified bot sessions are filtered out by default in session-related reports. Where the Human or bot session filter is supported, you can change the filter. Some surfaces, including Home and Live View, apply bot filtering without exposing an adjustable filter.

These changes can move session counts in different directions. Counting valid no-pageview journeys can increase sessions, while filtering automated traffic or avoiding a midnight UTC split can reduce them.

Why conversion rate can change too

Conversion rate depends on the number of sessions. If the denominator changes, the percentage can move even with the same number of orders.

That is why a sudden improvement or decline around the rollout should not be interpreted on its own. Shopify states that orders, sales and customer counts are not changed by this session measurement update.

Metrics that may look different include sessions, conversion rate, add-to-cart rate, reached-checkout rate, checkout conversion rate, bounce rate, pageviews per session, online store visitors and searches.

This does not mean every metric will move in the same direction or by the same amount for every store. The impact depends on traffic composition and the journeys Shopify is classifying under the updated method.

Treat comparisons across September 21 with caution

Shopify is not deleting or fully reprocessing historical data. Historical session data can, however, display differently when bot filtering is applied.

For data after the update, session-based metrics use the new measurement method. Shopify therefore recommends using post-update data as a new baseline for session-based metrics.

There is another date to know: bot classification applies only to sessions from October 7, 2025 onward. A comparison that includes earlier periods cannot apply the same bot classification across the entire range.

Year-over-year comparisons can still be useful, but they are not perfectly homogeneous across these boundaries. Orders, sales and customer counts should be reviewed alongside sessions.

What I would check on a Shopify store

Separate measurement from business performance: compare sessions and conversion rate with orders, sales and customers.
Check the date range: identify whether the comparison crosses the September 21-23 rollout.
Verify bot filtering: where available, compare periods using the same Human/Bot filter setting.
Avoid conclusions from one or two days: build a sufficient post-update sample before resetting operational benchmarks.
Document the break: if you export data or maintain external dashboards, mark September 21, 2026 as a methodology change.

This matters especially if you built a Shopify KPI dashboard with CSV, Google Sheets or Looker Studio. A chart can look continuous while the definition of the underlying session metric has changed.

Shopify Analytics and GA4 do not need to match

This update does not make Shopify Analytics equivalent to Google Analytics 4 or other measurement systems. Each platform uses its own rules for sessionization, identity, consent, bots and attribution.

A difference between two tools is therefore not automatic proof that one is wrong. First compare definitions, filters and date ranges. Reliable analytics is not about forcing two numbers to match; it is about knowing what each number measures and keeping comparisons coherent over time.

The same principle applies to more complex measurement stacks. In the guide to Shopify tracking with Customer Events, pixels and server-side architecture, the first step is defining the decision the data needs to support, then verifying how the data is collected and what its limits are.

Bot filtering is useful, but not an absolute truth

Shopify classifies sessions as human or bot to make traffic easier to interpret. This is particularly useful when automated activity distorts session-based metrics.

Not every automated visit is necessarily useless or harmful. Crawlers, testing systems and other automated traffic can serve different purposes. Where supported, Shopify therefore lets you include or exclude bot sessions from a report.

How I would set the new baseline

Keep benchmarks through September 20, 2026 as historical reference for the previous method.
Mark September 21-23 as a transition window.
Build new session-based benchmarks from a post-rollout period.
Continue using orders, sales and customers as control metrics.
Document the Human/Bot filter used in shared or automated reports.

For CRO analysis this avoids a common mistake: attributing a movement to a theme change, campaign or promotion when it coincides with a change in the measurement system.

What to do now

There is no migration to perform and no theme change is required. Shopify is applying the update between September 21 and 23, 2026.

The useful action is to document the change, review the reports you actually use and reset session-based benchmarks carefully. If you use external dashboards or automated reporting, add a methodology note instead of treating the time series as perfectly comparable across the rollout.