Shopify Sessions Are Low, But Sales Are Real: Navigating the New Analytics Update

Hey everyone! I wanted to jump in and share some insights from a recent discussion in the Shopify community that’s been buzzing. It started with a store owner, FableAndFemme, noticing something really unsettling: their Shopify analytics were showing ridiculously low session counts – like 3 sessions yesterday, 1 today – even though they had actual sales coming in. Naturally, they were asking, "Is analytics within Shopify broken again?"

This kind of discrepancy is enough to make any store owner's heart race, right? You're seeing orders, but your traffic numbers look like a ghost town. It turns out, this isn't just a random glitch for a few stores. There's a big, important reason behind it, and it's something we all need to understand.

The Big Reveal: Shopify's Recent Analytics Update

As Francesco Guiducci from IFG eCommerce pointed out in the thread, there's an important piece of context here. Shopify rolled out a significant session measurement update between September 21st and 23rd. The key takeaway? Identified bot sessions are now being filtered out of your session-based reports by default.

Not only that, but Shopify also changed how session boundaries are calculated. This means that comparing your session numbers from before September 22nd to now isn't really an apples-to-apples comparison anymore. You're essentially looking at a new baseline.

FableAndFemme’s own experience confirmed this perfectly. They noticed that their own phone visit to their store, which wasn't showing up as a live visitor, did appear when they toggled the "add bots" filter in the sessions by locations report. This tells us the visit *was* collected; Shopify just classified it as bot traffic and excluded it from the default view.

Why Your Sessions Look Low (and Sales Are Still Real)

So, the good news first: if you're seeing sales, your sales are real! As Francesco and VikashJ both confirmed, your orders, sales, and customer counts aren't affected by this measurement update. These metrics are recorded server-side, separate from the session pixel, so they remain reliable indicators of your actual store performance.

The core of the problem, as many community members highlighted, is that Shopify's bot classifier has become a bit "overzealous." It's flagging genuine visits as bot traffic. This is particularly common with traffic coming from in-app browsers – think those links you tap in Instagram, Facebook, or TikTok that open your store within the social media app itself, rather than in Safari or Chrome. These in-app WebViews can send user agents that are close enough to automated traffic, causing Shopify's heuristics to misclassify them.

This has a ripple effect beyond just raw session counts. VikashJ from Apploy pointed out that all your session-based metrics derived from these counts are now skewed. We're talking conversion rate, sessions by landing page, sessions by traffic source, and anything in Marketing that attributes a sale back to a specific ad or post. If you're running paid social campaigns, this is a big deal! A chunk of real in-app-browser traffic getting bucketed as bots means your reported conversion rate and ROAS (Return on Ad Spend) from that channel will look worse than it actually is.

What About Google Analytics (GA4)?

You might be looking at your GA4 data and seeing much higher session counts, which only adds to the confusion. Several experts in the thread, including Francesco, Ad-attack, and alaattincagil, cautioned against treating GA4 as the absolute source of truth. GA4 and Shopify use different session definitions, different bot filtering rules, and different tracking pixels. So, GA4 will almost always read higher, and the gap itself isn't proof that one is right and the other is wrong. Use GA4 as a valuable cross-check for traffic volume, but don't expect the numbers to match exactly.

How to Confirm What's Happening and What to Trust

Alright, so what can you do to get a clearer picture? The community offered some excellent, actionable advice:

  1. Check the Conversion Summary on Your Orders: Ad-attack suggested a quick check. Go into your Shopify admin, open a recent order, and look at the "conversion summary" on the order page. This data is recorded directly on the order itself, separate from the session report. If it shows the visits that led to the order, then the sessions were collected, and Shopify's bot classifier is just hiding them from the default report.
  2. Trust Your Order-Level Data: For now, focus on actual order counts, sales figures, and payment attempt records. As Clovia from clovia.app emphasized, these live on the order itself, outside the bot filter, giving you a true picture of your store's performance.
  3. Don't Judge Campaigns by Shopify's Session Data: If you're running paid ads, VikashJ strongly advises pulling performance from the ad platform's own reporting (e.g., Facebook Ads Manager, Google Ads) or GA4. Reconcile against actual orders using UTM parameters rather than relying on Shopify's session-based attribution while this classifier is being tuned.

Actionable Steps to Investigate and Report

If you suspect genuine traffic is being misclassified, here’s how to dig deeper and potentially help Shopify improve their system:

  1. Run a Controlled Test: Francesco and alaattincagil recommended this. Open your store directly in a clean browser (like Safari or Chrome), ideally in a private/incognito window with no ad blockers. Browse a few pages and record the exact timestamp. Then, check whether that visit appears normally in Shopify Analytics or only when you include bot sessions.
  2. Isolate the In-App Browser Issue: If your own test visit in a regular browser shows up fine, but your phone visits from social media still get flagged, it strongly suggests the in-app browser is the culprit. This helps narrow down the problem.
  3. File a Detailed Support Ticket: If you can consistently reproduce a normal browser visit being classified as a bot, that's valuable information for Shopify. File a ticket with Shopify Support and provide exact details: the timestamp of your test visit, the device you used, the browser (e.g., Chrome, Safari, Instagram in-app browser), and the landing page. A screen recording showing the visit happening and then the sessions-by-location report in your admin (with a visible timestamp) would be even better. This gives them a reproducible classification issue, not just a vague report of "low sessions."
  4. Adjust Your Baseline: Remember to put a note on September 22nd. Data before and after that date isn't directly comparable for session-based metrics.

A Few Other Things to Rule Out

While the bot filtering update is the primary suspect, lumine brought up a couple of other things worth a quick check, just in case:

  • Consent Management: Did you install or update a cookie banner app recently? Or perhaps change a privacy setting to block tracking before consent? Shopify counts sessions via its storefront pixel, so stricter consent rules could also impact session counts while orders (recorded server-side) remain unaffected.
  • Theme Publish: A recent theme update or custom head edit could, in rare cases, accidentally drop the analytics pixel. If you've published a new theme, it's worth a quick check to ensure the pixel is still active.

Ultimately, it seems like Shopify is actively tuning its analytics, and changes are still rolling out. While it's frustrating to see your numbers look off, the community's collective experience confirms that your sales data is still accurate. Focus on your order-level metrics, use GA4 as a secondary check, and help Shopify fine-tune their bot classifier by reporting specific instances of misclassification. This isn't just about your store; it's about helping the entire Shopify ecosystem get more accurate data in the long run.

Share:

Use cases

Explore use cases

Agencies, store owners, enterprise — find the migration path that fits.

Explore use cases