Bot AI - Spam Traffic

Short description of issue

Our Shopify store is experiencing a high volume of spam traffic originating from China, which is negatively impacting our analytics and making it difficult to track real user behavior accurately. We are looking for a way to block this traffic at an early stage (DNS/CDN level) before it reaches the storefront.

Link to Shopify Store

Reproduction steps

Reproduction steps
Visit the store and review analytics data (e.g., Shopify Analytics or Google Analytics).
Observe a significant amount of traffic coming from China.
This traffic does not behave like real users (high bounce rate, low engagement).
The abnormal traffic volume continues consistently over time.

Additional info

Additional info

We are also experiencing the same issue on another Shopify Plus store, which suggests this may not be an isolated case. This traffic pattern appears consistent across both stores, indicating potential bot activity rather than legitimate users.

What type of topic is this

Troubleshooting

Hey @Lsci_Team :waving_hand: - right now we don’t offer a means to block bot traffic at the DNS/CDN level through Shopify directly, but there are ways to limit access to your site for specific IPs using apps (more info here), and we do also offer a way to filter analytics reports so that bot traffic isn’t as impactful:

https://help.shopify.com/en/manual/intro-to-shopify/bots/bot-filtering

We do also leverage Cloudflare on our side to mitigate the effects of bots as a general rule, and there’s some decent info on this hereif you wanted to check that out too.

I definitely understand it’s not super ideal though if you’re having to handle a lot of bot traffic and making bots more identifiable/less impactful on real analytics is something we are looking at improving. Hope this helps a bit, let me know if I can clarify anything more on our side here.

change DNS to cloudflare and then set a security rule to have managed challenge for china.

Hi Shopify team, we’re also seeing massive bot traffic from Singapore and China. It’s severely distorting our analytics because these are normal organic automated visits and Shopify treats them in analytics as human users. It’s as if someone were using Puppeteer or something similar for this.

We recorded sessions in Clarity and every bot follows practically the same path, just on different products. At a certain point they always zoom out the page view as if to take a screenshot. It looks like they’re crawling the store and copying products.

This is a pretty serious problem.

Could you tell me more about it? Are these the correct steps?

  • Create cloudflare account
  • Set DNS records — both @ and www as CNAMEshops.myshopify.com, proxied (orange cloud)
  • Update nameservers at your domain registrar to Cloudflare’s
  • SSL/TLS → set to Full (not Full Strict, not Always HTTPS)

Hey @lynthius - good question,.

Cloudflare does have an O2O / Orange-to-Orange setup for Shopify, where traffic goes through your own Cloudflare zone first and then Shopify’s Cloudflare zone. That said, our current domain troubleshooting guidance treats Cloudflare proxy setups, including O2O, as unsupported from our side. So I wouldn’t want to present this as a Shopify-recommended workaround for bot traffic or analytics issues, but it is an option for sure.

If you do want to test O2O, the Cloudflare-side docs are the right source for setup and support. The main thing I’d call out is that this can affect how request signals reach Shopify, which can make Shopify-side bot detection less accurate, and any issues caused by the proxy layer would generally need to be handled with Cloudflare support.

For the bot/analytics issue itself, we are aware of reports where automated-looking traffic from regions like Singapore/China can distort analytics, and work is ongoing on our end to improve things, though I can’t guarantee a turnaround time on that or what the solution will look like. If you’re open to sharing the affected store URL and rough date/time range for the spike, I can pass that context along on our end for sure

Let me know if I can clarify anything here.

Thanks for the detailed explanation, @Alan_G. That’s exactly the kind of clarity we needed before deciding how to proceed. Cheers!

No worries @lynthius - I’ll mark this thread as solved, but let me know if we can help out further for sure :slight_smile: