Executive summary
- What: Shopify revised session measurement in Analytics starting September 21, 2026, which moves sessions, conversion rate, and every metric derived from them.
- Why: Sessions now follow continued shopper activity instead of resetting at midnight UTC, identified bot traffic is filtered by default, and some journeys without a pageview are finally counted.
- Who: Anyone who reports on conversion rate, channel performance, or CRO test results, including marketing leads, analysts, and agency partners.
What changed
Three mechanical changes ship together. First, a session used to end at midnight UTC whether or not the shopper was still browsing, so one late evening journey could be split into two sessions. Sessions now end only after 30 minutes of inactivity. Second, sessions that never included a pageview are now counted, so a shopper who goes straight to checkout from a saved cart link is no longer invisible. Third, identified bot sessions are filtered out of session related reports by default, with a Human or bot session filter available in the reports that support it.
Orders, sales, and customer counts are not affected. The rollout runs from September 21 to September 23, 2026, so your store may cross over on any of those three days rather than all at once.
Why it matters
The direction of the change is not predictable in advance. Bot filtering removes sessions from the denominator, which pushes conversion rate up. Counting pageview free sessions adds to the denominator, which pushes conversion rate down. The net effect depends entirely on your traffic mix. A store carrying heavy scraper or uptime monitor traffic can see sessions fall by a visible margin while conversion rate rises in step. That is a measurement artifact, not performance.
The practical risk for Shopify Plus merchants is misattribution. If a CRO test, a paid campaign, or a merchandising change landed in the same week, the step change will be read as a result. Board decks and recurring reports built on September comparisons will mislead unless the date is annotated. If you are running experiments on a continuous cycle, align the rollout date with your test calendar before the next readout: our conversion rate optimization team treats a platform level break like this as a hard stop on cross period comparisons. Headless storefronts deserve extra scrutiny, because filter availability and session behaviour vary with how storefront analytics were implemented.
Role specific impact
- Marketers: annotate every dashboard at September 21, 2026. Do not compare pre and post periods for conversion rate, bounce rate, or add to cart rate without flagging the break in method.
- Developers: on headless builds, confirm which session related reports expose the Human or bot session filter, and verify that your storefront analytics implementation still emits the events your reporting depends on.
- Store admins: review alerting and scheduled report thresholds tied to session volume, and pause automated anomaly flags for the rollout window so the team is not chasing a false alarm.
Use-case example
Real-world scenario
A Plus apparel merchant running roughly 900,000 monthly sessions at a 2.1 percent conversion rate watches sessions fall to about 820,000 in the rollout week while orders hold flat. Conversion rate now reads 2.3 percent. Nothing improved: close to 80,000 bot sessions simply left the denominator. The same team had shipped a new product page layout that week and was one meeting away from declaring a 9 percent conversion lift. Annotating the rollout date and checking orders and sales, which had not moved, prevented a false positive and preserved the test.
Implementation checklist
- Confirm the exact date your store received the update, somewhere between September 21 and September 23, 2026.
- Export sessions, conversion rate, bounce rate, and add to cart rate for the 30 days before the rollout, and keep that file as a frozen reference.
- Annotate the rollout date in every dashboard, BI tool, and recurring report that consumes Shopify session data.
- Pause or restart any in flight CRO test whose measurement window spans the rollout.
- Review the Human or bot session filter in affected reports and agree one house default.
- Rebaseline targets and alert thresholds once you have two clean weeks of post update data.
- Brief stakeholders before the next reporting cycle rather than explaining the variance afterwards.
FAQ
Q: Was our historical data restated?
A: No. Figures already recorded stay as they were measured. The new method applies going forward, which is precisely why comparisons across the rollout date are unreliable and need an annotation.
Q: Will this make our Shopify numbers agree with Google Analytics?
A: Not necessarily. GA4 and Shopify still use different session definitions and different bot heuristics. The gap may narrow, but continue to treat the two systems as separate sources rather than expecting reconciliation.
Resources
Changes to sessions and conversion rate in Shopify Analytics
Need guidance? Talk to Makro.