Why Your Analytics Show Traffic from China and Singapore (and What to Do About It)
Because much of that traffic is not from real people at all it often comes from bots, crawlers, AI training systems and cloud infrastructure based in or routing through China and Singapore, which can skew your metrics. You can exclude these visits in Google Analytics (GA4) using Google Tag Manager so your reports reflect real audience behaviour.
Over the past 12 to 24 months, many businesses across industries have noticed a consistent pattern in their website analytics: unexpected traffic from China and Singapore, often accompanied by low engagement, no conversions, and no commercial value.
This issue is not unique to your website. It is a global trend increasingly flagged by analytics teams, SEO specialists, hosting providers, and cloud infrastructure vendors.
In this guide, we explain:
- Why this traffic occurs
- How it affects analytics accuracy and reporting
- When traffic should be blocked entirely
- When it should be excluded from analytics only
- How to manage this safely using Google Tag Manager
- How to document changes to maintain reporting integrity
What Is Causing the Increase in China and Singapore Traffic?
In most cases, this traffic does not originate from human users.
China and Singapore are global hubs for:
- Cloud infrastructure and data centres
- AI training and crawling systems
- Automation and scraping tools
- Security scanners and monitoring software
As AI adoption accelerates, automated systems increasingly:
- Crawl websites to analyse content
- Test forms, APIs, and endpoints
- Scrape structured data
- Trigger basic page views and events
As a result, this traffic often:
- Appears as sessions and page views
- Rarely converts
- Skews engagement metrics
- Inflates geographic and channel reports
Singapore, in particular, is a major cloud routing hub. Many automated tools route traffic through Singapore even when originating elsewhere.
How This Traffic Affects Your Analytics and Reports
If unmanaged, automated traffic can distort key metrics such as:
- Sessions and users by country
- Engagement rate and average session duration
- Conversion rates
- Funnel and attribution analysis
- SEO performance benchmarks
This can lead to:
- Incorrect assumptions about audience behaviour
- Misguided marketing decisions
- Confusion when comparing month-on-month performance
- Time wasted investigating non-existent leads
Importantly, this traffic does not consume paid advertising budgets unless you are actively targeting these regions.
Two Ways to Handle the Problem
There are two valid approaches, depending on business impact.
Option A: Block the Traffic at Server Level
When to Choose This Option
- High volumes of spam form submissions
- Fake or low-quality leads affecting sales teams
- Server resources or site performance are impacted
- You want to actively prevent access from certain regions
How Server-Level Blocking Works
Traffic is blocked before it reaches your website using:
- Cloudflare
- A Content Delivery Network (CDN)
- Firewall or Web Application Firewall (WAF) rules
These tools can:
- Block traffic by country
- Apply CAPTCHA challenges
- Filter known bot patterns
- Rate-limit suspicious behaviour
Key Considerations
- This is a technical, infrastructure-level change
- Requires configuration and testing
- Best used when there is a clear operational issue
Option B: Exclude the Traffic From Analytics (Recommended First Step)
When to Choose This Option
- No spam leads or operational impact
- Site performance is unaffected
- The primary issue is reporting accuracy
This is the most common and recommended approach.
How Analytics Exclusion Works
Instead of blocking access, you:
- Allow the site to load normally
- Prevent analytics tools from recording visits from selected countries
- Keep reports accurate and decision-ready
This is implemented using Google Tag Manager before data reaches Google Analytics 4.
How to Exclude China and Singapore Traffic Using Google Tag Manager
This approach ensures GA4 and Looker Studio remain aligned without server-level changes.
Step 1: Detect the Visitor's Country (GeoIP Tag)
A lightweight script runs on page load to identify the visitor's country code (for example, CN or SG).
Steps
- Open Google Tag Manager
- Select the correct GTM container
- Create a new tag
- Choose Custom HTML
- Name the tag: GeoIP – Country Detection
- Paste the script below
- Set the trigger to All Pages
- Save the tag
Script (paste exactly as shown)
fetch('https://ipapi.co/country/')
.then(function(response) {
return response.text();
})
.then(function(country) {
window.geoipCountry = country.trim();
})
.catch(function() {
window.geoipCountry = 'unknown';
});
Step 2: Store the Country as a Variable
Create a reusable variable inside Google Tag Manager.
Steps
- Go to Variables
- Create a new variable
- Select Custom JavaScript
- Name it: Visitor Country
- Paste the code below
- Save the variable
Variable Code
function()
Step 3: Create the Block Trigger
This trigger identifies traffic from China or Singapore.
Steps
- Go to Triggers
- Create a new trigger
- Name it: Block GA4 – China & Singapore
- Choose Page View
- Select Some Page Views
- Add the condition below
- Save the trigger
Trigger Condition
- Variable: }
- Operator: matches RegEx
- Value: ^(CN|SG)$
Step 4: Apply the Trigger as an Exception on GA4
- Open your GA4 Configuration tag
- Confirm it fires on All Pages
- Under Exceptions, add Block GA4 – China & Singapore
- Save the tag
From this point forward:
- GA4 will not record data from China or Singapore
- Historical data remains unchanged
- SEO and paid ads are unaffected
Step 5: Preview and Publish
- Use GTM Preview mode to confirm tags fire correctly
- Publish with the version name:
GA4 geo exclusion – CN & SG
Recommended Post-Implementation Checks
GA4 Annotation
Document the following in GA4:
- Date of change
- Countries excluded
- Exclusion method (GTM level)
Looker Studio Dashboard Note
Explain:
- When exclusions were applied
- Why historical data may still show China and Singapore
GA4 Exploration Verification
Create a simple exploration filtered to China and Singapore to confirm no new data is recorded.
Frequently Asked Questions (FAQs)
No. Excluding traffic in Google Tag Manager prevents the data from entering GA4 in the first place.
Historical data remains unchanged. New exclusions may take several hours to reflect fully.
No. Only analytics collection is affected.
Traffic defaults to “unknown” and GA4 continues to fire to avoid losing valid user data.
Invest in the skills that the world is demanding. Future-proof your career with BlueMagnet. Explore our certified AI SEO and GEO courses and make your skills your most exportable asset.
Final Recommendation
For most businesses, excluding China and Singapore traffic from analytics is sufficient and should be the first step. Server-level blocking should only be implemented when there is clear operational impact.
Need Help Cleaning Up Your Analytics?
At BlueMagnet, we help businesses:
- Audit GA4 and Google Tag Manager setups
- Resolve data quality and bot traffic issues
- Implement clean geo-exclusions
- Build accurate GA4 and Looker Studio dashboards





