Executive summary
- What: Shopify Analytics is now better at spotting automated traffic inside cart and checkout events, so sessions that once counted as human are reclassified as bots.
- Why: Reports built on the human session filter may step down slightly in volume, while the conversion rates on those same reports read a little higher.
- Who: Anyone who reports on sessions, funnel drop-off or conversion rate, including growth leads, finance partners and agency analysts.
What changed
Shopify labels every storefront event as probably human or probably bot, then classifies the whole session from the pattern of those events. The detection logic covering cart and checkout activity has been sharpened. It now catches more of the automated tooling that simulates shopping behaviour to read data: price monitors, inventory watchers, competitive scrapers and the long tail of scripts that add to cart to reach a price or a stock number.
Only the labelling moved. Orders, sales and customer records are outside the scope of this change, and nothing was deleted or restated. The visible effect is confined to reports that use the Human or bot session dimension or filter. Shopify's classifier stays deliberately conservative: a session with mixed signals is still counted as human rather than risk discarding a real customer, which is why this reads as a small step rather than a cliff.
Why it matters
For a Shopify Plus merchant the value is denominator hygiene. Bot sessions almost never convert, so leaving them in the session count depresses measured conversion rate and makes genuinely good traffic look mediocre. Cleaner inputs sharpen three decisions that cost real money: which acquisition channels get budget, which funnel steps get development time, and whether a merchandising test actually moved anything.
The risk runs the other way too. An unexplained dip in sessions during peak season gets escalated as lost demand, and teams spend a week chasing a problem that is really a measurement improvement. Worth noting if your conversion rate programme reports week over week against a fixed target, because the baseline just shifted under it.
Role-specific impact
- Marketers: expect campaign and landing page reports to show fewer sessions with steadier order counts. Re-baseline any conversion rate target set before mid-November, and flag the shift in your next readout so nobody reads it as a traffic loss.
- Developers: if dashboards or warehouse jobs pull session data out of Shopify, confirm whether they apply the human filter. Mixed filtering across sources is the usual reason two dashboards disagree by a few percent.
- Store admins: check saved and scheduled reports that use the Human or bot session filter, and annotate the date in whatever runbook your team uses for reporting anomalies.
Use-case example
Real-world scenario
A Plus apparel merchant runs roughly 900,000 online store sessions a month and reports human-filtered conversion rate to its board weekly. The Monday after the change, human sessions for the prior week came in 2.1 percent below the trailing four-week average, while orders were flat and revenue was up slightly. Conversion rate moved from 1.74 percent to 1.78 percent. Nothing in the business changed. The team confirmed it by holding the same report with the filter removed, where total sessions were unchanged, then added a note to the board deck. Without that check, a 2.1 percent dip in the first week of peak trading would plausibly have triggered a paid media review.
Implementation checklist
- List the reports and dashboards that apply the Human or bot session filter, including scheduled exports and anything feeding a BI tool.
- Pull each one with the filter on and off for the same period, so you can separate a classification shift from an actual traffic change.
- Re-baseline session and conversion rate targets that were set before mid-November 2026.
- Annotate the date in your analytics documentation and in any board or stakeholder reporting that trends sessions.
- Check that external platforms you reconcile against, such as your ad platforms or GA4, are being compared on a like-for-like filter basis.
- Leave orders, sales and customer reporting alone. It is unaffected, and changing it now only adds noise.
FAQ
Q: Did we lose traffic, or did the numbers just change?
A: The numbers changed. Total sessions are untouched. Only the split between human and bot moved, so a dip appears exclusively in human-filtered views.
Q: Does this affect revenue, orders or customer records?
A: No. Shopify has scoped the change to session classification in cart and checkout activity. Financial and customer data is not part of it, so your reconciliation against finance stands.
Resources
Bot filtering in Shopify analytics and reports
Need guidance? Talk to Makro.