Browse apps

Guides

Shopify Bot Traffic in Analytics & GA4: Ashburn & Singapore Spikes

TL;DR

Sudden direct traffic spikes from Ashburn (Virginia), Council Bluffs (Iowa), or Singapore usually come from cloud data centers (AWS us-east-1, Google Cloud us-central1, and APAC hosting hubs) running headless scrapers, AI crawlers, or carding scripts. Blocking datacenter ASNs and headless browsers on your storefront stops bots from firing browser pixels while Checkout Protection blocks automated orders.

If you have ever opened your reporting dashboard to investigate Shopify bot traffic in Analytics and GA4, you have likely seen the same puzzling pattern: overnight, your store records a sudden spike in direct traffic from Singapore, Ashburn, or Council Bluffs. Every session arrives as Direct / None, lands on a handful of product or collection URLs, registers zero seconds of engagement, adds nothing to the cart, and drags your storewide conversion rate down.

For merchants who do not run ads in Iowa, Northern Virginia, or Southeast Asia, these spikes look like a broken tracking pixel or a targeted attack. In reality, those three cities are the physical capitals of the global cloud computing infrastructure. What your reports are capturing is automated compute—headless browsers, competitor price scrapers, AI training crawlers, and checkout probing scripts—spinning up virtual machines inside commercial data centers.

In this guide, we explain why cloud bot traffic clusters in specific cities, why both Shopify Analytics and Google Analytics 4 (GA4) struggle to filter out modern headless browsers, what storefront blocking can and cannot remove from your analytics reports, and how to configure LabX Fraud Filter to stop automated bots without locking out real buyers or search engines. For a complete overview of visitor filtering, see our Shopify traffic and bot blocking guide.

Why is your Shopify store getting sudden traffic spikes from Ashburn, Council Bluffs, or Singapore?

When an analytics tool resolves a visitor’s location, it looks up the visitor’s IP address in a geolocation database and maps it to the physical city where that IP subnet is registered. While human shoppers are spread across thousands of residential suburbs and mobile carrier towers, automated scripts run inside massive server farms concentrated in a few specific towns:

  1. Ashburn, Virginia (us-east-1): Located in Loudoun County’s “Data Center Alley,” Ashburn is the physical home of Amazon Web Services’ flagship US East (N. Virginia) region (us-east-1), along with major colocation hubs for Microsoft Azure (eastus), DigitalOcean, and Oracle Cloud. Because us-east-1 is the default region in most AWS SDKs, serverless templates, and scraping containers, any developer or bot operator who launches a cloud script without changing the region setting appears as a visitor from Ashburn, Virginia.
  2. Council Bluffs, Iowa (us-central1): Council Bluffs is home to Google Cloud’s primary North American compute region (us-central1). Automated workloads running on Google Compute Engine, Cloud Run, or headless Chromium containers—as well as some unverified Google-hosted fetchers—geolocate to Council Bluffs, Iowa (or nearby Omaha).
  3. Singapore (ap-southeast-1 / asia-southeast1): Singapore is the primary fiber and cloud interconnect hub for the entire Asia-Pacific region. AWS, Google Cloud, DigitalOcean, Alibaba Cloud, Tencent Cloud, and OVHcloud all operate major data centers in Singapore. Automated catalog scrapers, dropshipping spy tools, and credential-stuffing bots frequently rotate through Singapore datacenter IP pools.
  4. Other recurring datacenter hubs: You may see identical spikes from Boardman or The Dalles, Oregon (AWS us-west-2 and Google Cloud us-west1), Dublin, Ireland (AWS eu-west-1), Frankfurt, Falkenstein, or Nuremberg, Germany (Hetzner Online and AWS eu-central-1), and North Bergen / Clifton, New Jersey (DigitalOcean NYC regions).
City Seen in Shopify / GA4Underlying Cloud Region & Major ASNsCommon Automated Traffic SourcesBest Storefront Control in LabX Fraud Filter
Ashburn, Virginia (US)AWS us-east-1 (AS16509, AS14618), Azure (AS8075)Headless Puppeteer/Playwright scrapers, SEO/AI crawlers, serverless monitors, and card testing botsEnable Block datacenter traffic + Auto-block suspicious crawlers (preserves real Virginia shoppers)
Council Bluffs, Iowa (US)Google Cloud us-central1 (AS15169, AS396982)Cloud Run headless browsers, custom Python/Node scrapers, and ad/merchant quality fetchersEnable Block datacenter traffic while keeping Allow verified good bots on for Googlebot / AdsBot-Google
Singapore (SG)AWS ap-southeast-1, DigitalOcean (AS14061), Alibaba (AS45102), Tencent (AS132203)Competitor price trackers, catalog copycats, and automated checkout probingEnable Block datacenter traffic (or block/redirect Singapore in Blocking Rules > Location if you do not sell there)
Frankfurt / Falkenstein (DE)Hetzner Online (AS24940), OVHcloud (AS16276), AWS eu-central-1Low-cost VPS scraper farms and rotating proxy poolsEnable Block datacenter traffic or quick-add + Hetzner Online (AS24940) in Blocking Rules > ISP

Why do headless browser bots show up in GA4 and Shopify Analytics despite built-in bot filters?

Merchants often assume that Google Analytics 4 and Shopify Analytics already strip out all automated traffic. Both platforms do filter known crawlers, but they evaluate traffic at different layers and miss different types of modern bots:

  • How GA4 filters bots (and what it misses): According to Google Analytics documentation on known bot-traffic exclusion, GA4 automatically excludes traffic from known bots and spiders using Google’s internal research and the International Spiders and Bots List maintained by the Interactive Advertising Bureau (IAB). You cannot disable this filter or view a report of how much traffic it excluded. However, the IAB list relies on recognized crawler signatures and known spider IPs. When a scraper spins up a fresh virtual machine in Ashburn or Singapore using headless Chrome (via Puppeteer, Playwright, or Selenium) and passes a normal desktop Mozilla/5.0 ... Chrome/... user-agent string, it is not on the known spider list. Because a headless browser executes JavaScript, it runs gtag.js and Google Tag Manager, sending a page_view and session_start event straight into GA4.
  • Why bot sessions always appear as Direct / None: A real shopper usually clicks a search result, social post, email link, or paid ad, which populates document.referrer or attaches utm_ query parameters. A bot script simply loads a list of target URLs from a database and opens them directly in a fresh browser context with no referrer and no cookies—causing GA4 and Shopify to classify every hit as a brand-new Direct session from a “New Visitor.”
  • Why Shopify Analytics and GA4 counts rarely match: Shopify records traffic at the server/CDN request layer when a storefront page is requested, whereas GA4 only records visitors whose browsers execute JavaScript and allow analytics tags to fire (unless blocked by ad blockers or cookie consent banners). Raw HTTP bots (curl, python-requests) that never execute JavaScript will never trigger GA4 tags, whereas headless browser bots that execute JavaScript inflate both dashboards.

How can you tell if a traffic spike is automated bots or real shoppers?

Before you add blocking rules, take two minutes to verify that a regional spike is automated datacenter traffic rather than a viral post or press mention:

  1. Check the city-to-region concentration: Real human traffic in a country or state follows population density (for example, spreading across Los Angeles, New York, Chicago, Houston, and Miami). If 90% of your Virginia sessions come from Ashburn or 95% of your Iowa sessions come from Council Bluffs, you are looking at cloud servers, not consumers.
  2. Inspect engagement time and page depth in GA4: In GA4, open Reports > Engagement > Pages and screens or Tech > Tech details and add a secondary dimension for City and Operating system. Headless cloud bots typically show 0s average engagement time, a near-100% bounce rate (zero engaged sessions), and a disproportionate share of Linux desktop operating systems or outdated Chrome versions.
  3. Cross-check ASN and block reasons in LabX Fraud Filter: Once LabX Fraud Filter is active on your theme, open Analytics and Visitor in the app navigation (detailed in our Analytics and Visitor log guide). The Block reasons table breaks down whether incoming hits matched Datacenter IP (datacenter), Headless browser (suspicious:headless), Known bot pattern (bot), Unrecognized browser (suspicious:unknown-ua), or Tor exit node (tor).

How do you block datacenter and headless browser bots in LabX Fraud Filter?

The smartest way to stop Ashburn, Council Bluffs, or Singapore bot spikes on your storefront is to target how the bot connects (cloud datacenter ASNs and headless browser signals) rather than blocking the entire United States or every visitor in Virginia. That way, real customers browsing from home Wi-Fi or mobile carriers in Virginia, Iowa, or Singapore can shop normally.

Follow these steps in LabX Fraud Filter (see annotated screenshots in our bot and content protection guide):

Before enabling bot or network switches, open Settings > General settings and copy your Admin access link (https://your-store.myshopify.com/?fg_bypass=...). Open that link once in your browser so our server verifies your token and stores it in your browser—allowing you to browse and test your store without ever being blocked by your own rules. You can rotate the link anytime by clicking Generate new link.

Step 2: Turn on Datacenter and Headless Bot detection in Settings > Mitigator

Open Settings in the app navigation and select the Mitigator tab:

  1. Enable Block datacenter traffic: This is the single most effective control against Ashburn (us-east-1), Council Bluffs (us-central1), and Singapore cloud spikes. Our server checks each session’s Autonomous System Number (ASN) against a curated list of cloud compute and VPS hosting providers—including Amazon AWS (AS16509, AS14618, AS8987, AS7224), Google Cloud (AS15169, AS396982, AS19527), Microsoft Azure (AS8075, AS8068, AS8069, AS12076), DigitalOcean (AS14061), Hetzner (AS24940), OVH (AS16276), Alibaba Cloud (AS45102, AS37963), Tencent Cloud (AS132203, AS45090), Vultr (AS20473), Linode/Akamai (AS63949), Contabo (AS51167), M247 (AS9009), and Leaseweb (AS30633). As we explain in our guide on blocking datacenter IPs vs VPNs on Shopify, datacenter blocking is not consumer VPN blocking: shoppers using a consumer privacy VPN on a residential network are not locked out.
  2. Enable Auto-block unknown bots: Blocks visitors whose user-agent contains known scraper and HTTP client tokens (bot, crawl, spider, scrap, curl/, wget, python-requests, python-urllib, go-http-client, java/, okhttp, headlesschrome, phantomjs, puppeteer, playwright, and selenium) or whose browser reports navigator.webdriver === true.
  3. Enable Auto-block suspicious crawlers: Check both sub-options:
    • Unknown user agent (not a known browser): Blocks clients that do not match a recognized desktop or mobile browser family (Chrome, Firefox, Safari, Edge, Opera, SamsungBrowser, UCBrowser, YaBrowser, or DuckDuckGo).
    • Headless hints (webdriver, no plugins, no touch, no languages): Catches disguised headless Chromium/Firefox instances that spoof a standard user-agent string. It triggers when the W3C WebDriver navigator.webdriver flag is true, or when three weak automation tells (navigator.plugins.length === 0, navigator.maxTouchPoints === 0, and navigator.languages.length === 0) all agree at once.
  4. Enable Block Tor traffic: Blocks connections from the weekly refreshed Tor exit-node list.

Step 3: Keep Allow verified good bots on (and uncheck unwanted AI crawlers)

Because Googlebot and AdsBot-Google crawl from US data centers—including Google Cloud infrastructure—you must keep Allow verified good bots enabled in Settings > Mitigator.

LabX Fraud Filter evaluates its Allowed bot list of 25 crawlers at the very top of the storefront precedence order, before Block datacenter traffic or Auto-block unknown bots. If your traffic spike is caused by AI training crawlers or competitor SEO bots rather than search engines, click Manage next to Allowed bot list, uncheck Allow all, keep Search Engines (10) and Social Media (4) checked, and uncheck specific AI Crawlers (GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider, Google-Extended) or SEO Analytics bots (AhrefsBot, SemrushBot). See our guide on how to whitelist Googlebot, ad crawlers, and webhooks on Shopify for the full token list.

Step 4: Add custom ASN or Country rules when needed

  • Block additional hosting networks (Blocking Rules > ISP): Click any quick-add sample chip (+ Amazon Web Services (AWS) (AS16509), + Google Cloud (AS15169), + DigitalOcean (AS14061), + Hetzner Online (AS24940), + Linode / Akamai (AS63949), + OVHcloud (AS16276)) or enter any custom AS#### code or ISP substring you spot in your logs.
  • Block or redirect unsupported countries (Blocking Rules > Location): If your store never ships to Singapore or specific international markets, you can block or redirect those countries outright—or use Block all except mode for a domestic-only store.

Can storefront bot blocking completely remove bot sessions from Shopify Analytics?

We believe in stating the technical architecture of Shopify plainly so you know exactly what to expect in your reports: blocked visitors still appear in Shopify Analytics and abandoned checkouts.

Understanding why comes down to how Shopify serves pages (which we compare in detail in storefront blocking vs checkout blocking on Shopify):

  1. Shopify logs the request at the CDN edge first: When a bot in Ashburn or Singapore requests https://your-store.com/products/shirt, Shopify’s CDN delivers the initial HTML document and logs the visit on Shopify’s servers before any third-party app JavaScript executes in the visitor’s browser. No Shopify app can sit in front of Shopify’s CDN to drop the HTTP connection before Shopify counts it.
  2. Storefront rules run in the visitor’s browser (Fraud Guard app embed): As soon as the page loads in the browser, LabX Fraud Filter evaluates your inline metaobject ruleset (zero extra network calls for user-agent, IP, or headless checks, and one 30-minute cached /apps/fraud/geo lookup for datacenter, Tor, ISP, or country rules). When a visitor is blocked, renderBlockPage immediately calls window.stop()—canceling pending theme scripts, images, and pixels that have not finished loading—and replaces the page body with your block screen (preserving <head> when the client looks like a bot so SEO metadata stays intact).
  3. Browser scripts can be bypassed if JavaScript is off: Because storefront blocking runs in the browser, a script that disables JavaScript or fetches raw HTML with curl bypasses browser blocking. Similarly, storefront Content protection (disabling right-click, text selection, and copy shortcuts to deter casual copying, as covered in stopping competitor price scraping on Shopify) is a browser deterrent that cannot stop OS screenshots or non-JS scrapers.
  4. Use LabX Fraud Filter’s built-in Analytics for a clean Allowed vs. Blocked view: Because Shopify Analytics includes requests that were subsequently blocked in the browser, open Analytics inside LabX Fraud Filter to see your true Total allowed, Total blocked, and Block rate over the last 7 days, 30 days, or 90 days, alongside the Visitor log of the 50 most recent blocked or redirected visits.

How do you clean up GA4 reports and stop bots that bypass the browser?

To keep your reporting clean and prevent automated scripts from submitting fake newsletter signups or fraudulent orders, pair your storefront rules with analytics filters and server-side checkout validation:

LayerWhat Happens Without ProtectionAction to Take
GA4 Reporting (Reports & Explorations)Headless browsers from Ashburn, Council Bluffs, or Singapore that fire gtag.js before a geo check completes skew conversion rateEnable Auto-block unknown bots and Headless hints (which evaluate synchronously from the inline metaobject before any network call), and apply a comparison or Exploration exclusion filter in GA4 for unengaged sessions from known datacenter cities
Shopify Analytics ReportsServer-side edge requests from bots still register in overall session totalsApply Shopify’s built-in Human or bot session dimension filter in custom reports, and compare against Total allowed vs. Total blocked in LabX Fraud Filter > Analytics
Storefront Newsletter FormsAutomated bots submit throwaway email addresses to harvest welcome discount codesToggle on Block disposable emails in Settings > Mitigator to block throwaway email domains on storefront newsletter signup forms
Shopify Checkout (Cart & Checkout APIs)Carding or inventory-hoarding bots skip the browser entirely and post directly to Cart/Checkout endpointsConfigure Checkout Protection in LabX Fraud Filter, which runs server-side on Shopify’s infrastructure as a Shopify Cart and Checkout Validation Function and cannot be bypassed

While storefront scripts cannot stop a bot that disables JavaScript or calls /cart/add.js directly, our server-side Shopify fraud prevention layer (Checkout Protection) executes on Shopify’s own servers during cart and checkout progression. By adding Checkout Protection rules that block disposable email domains (Email Contains @mailinator.com, @tempmail.com, @10minutemail.com, @yopmail.com), restricted shipping countries (Country), freight-forwarder street substrings (Address), or burner numbers (Phone), you ensure that automated cloud traffic can never complete a fraudulent checkout—even if it skips your storefront altogether.

Frequently asked questions

Why am I getting hundreds of visits from Ashburn, Council Bluffs, or Singapore with zero sales?

Ashburn (Virginia), Council Bluffs (Iowa), and Singapore are the physical locations of the world’s largest cloud computing regions—AWS us-east-1, Google Cloud us-central1, and APAC cloud hubs. Price scrapers, AI crawlers, ad verification tools, and headless browser bots rented on those cloud servers appear in analytics as direct visits from those cities.

Does Google Analytics 4 (GA4) automatically filter out all Shopify bot traffic?

No. GA4 automatically excludes known bots and spiders listed on the IAB/ABC International Spiders and Bots List, and that filter cannot be turned off. However, custom headless browsers (such as Puppeteer, Playwright, or Selenium scripts) running on cloud servers often spoof a standard desktop Chrome user-agent and execute JavaScript, allowing them to fire GA4 tags as if they were human visitors.

Will blocking bots in a Shopify app remove them from Shopify Analytics?

No. Because Shopify serves storefront HTML from its CDN before any browser script runs—and logs sessions at the platform level—blocked visitors still appear in Shopify Analytics and abandoned checkouts. However, storefront blocking in LabX Fraud Filter stops browser execution immediately via window.stop(), protects your catalog in the browser, and gives you a clean Allowed vs. Blocked breakdown in the app’s own Analytics dashboard.

Will blocking traffic from Ashburn or Council Bluffs hurt my Google SEO or block local shoppers?

If you block entire cities or US states by location, you risk blocking real shoppers in Virginia or Iowa. Instead, enable "Block datacenter traffic" and keep "Allow verified good bots" turned on in LabX Fraud Filter. Datacenter blocking only stops cloud hosting ASNs (not residential ISPs or consumer VPNs), and the 25-crawler allowlist ensures Googlebot and AdsBot-Google always pass first.

Sources

  1. Google Analytics Help — Known Bot-Traffic Exclusion in GA4
  2. AWS Global Infrastructure — Regions and Availability Zones (US East N. Virginia)
  3. Google Cloud — Global Locations and Regions (us-central1 Council Bluffs, Iowa)
  4. W3C WebDriver Specification — Navigator Automation Information (navigator.webdriver)
  5. Google Search Central — Verifying Googlebot and Other Google Crawlers
  6. Shopify Dev Docs — About Cart and Checkout Validation Functions

Part of our guide: Traffic & bot blocking →

Put your first blocking rule live in minutes

Install LabX Fraud Filter free on Shopify, turn on the Fraud Guard embed and add your rules.

Install free on Shopify

Free plan available