Ghost in the machine: how to fix phantom traffic in Google Analytics 4
In the world of e-commerce, a sudden traffic spike usually calls for a celebration. But what happens when thousands of visitors suddenly land on your site from a region where you don't even ship? If you are seeing massive hits from a remote location while your sales stay flat, you aren't trending; you are likely being targeted by a device farm.

These sophisticated robots mimic real human behavior by clicking through multiple pages, making them much harder to spot than a standard "one-hit" bot. This article will help you identify this phantom traffic and show you how to scrub it from your GA4 data for good.
In the example above Country dimension is used as a Column - to learn more about that check out our Columns in GA4 help article.
The domino effect on your marketing metrics
The primary danger of non-human traffic is that bots never buy anything. When they inflate your session counts without ever reaching the checkout, they effectively break your reporting.
-
Conversion rates plummet: both your Session and User Key Event rates will drop, making it look like your marketing is failing.
-
Skewed Landing page data: bots often target specific pages, making them appear more popular or important than they actually are to real customers.
-
Wasted ad spend: if you optimize your budget based on raw traffic volume rather than a specific intent, this data will confuse learning processes of advertising platforms.
GA4 vs. Universal Analytics: a new way to filter
In the old days of Universal Analytics, we used "View filters" to block traffic before it hit the database. GA4 handles things differently. While it lacks the old permanent view filters, it offers a more flexible way to exclude data directly within the reporting interface. Adding a filter in GA4 refers to a temporary quick solution - that lasts only during your current analytics session:

The new logic for customizing reports is more advanced compared to how Universal dealt with this because you can filter various reports based on different dimensions and conditions. It allows an analyst to decide exactly what data should be visible in a specific context.
The best part? Applying these exclusions takes less than sixty seconds.
Step-by-step: how to exclude traffic that doesn’t belong
Follow these steps to clean up any standard report in your GA4 property:
-
Start by navigating to the report you want to clean (e.g., the "Traffic Acquisition" report).
-
Click the “Customize report” button (pencil icon) located in the top right corner.

-
A slider will open on the right, just like when adding a temporary filter.
-
Select a dimension by which you’ll identify the bot traffic (Country in our case)
-
Choose the match type "does not exactly match" and select the country you want to hide.
-
Once applied, GA4 will ask if you want to save the changes.
-
Save to current report: This keeps your interface clean and updates the standard view.
-
Save as a new report: This creates a separate, "clean" version while leaving your raw data untouched for comparison.
-
Making Your Clean Data Visible to the Team
If you choose to save your filtered view as a new report, you need to ensure your team can actually find it.
Navigate to the Library link at the bottom of the left-hand sidebar. From here, find the Collection your team uses (such as "Life Cycle") and click Edit.

You can then search for your new, filtered report by name and drag it into the belonging Topic such as "Acquisition" or "Engagement."
Remember that any changes made in the Library are visible to everyone with access to the property. By taking this extra step, you ensure the entire organization is making decisions based on accurate, human-driven data.
Summary of Key Takeaways
Phantom traffic from device farms can destroy the integrity of your marketing reports by inflating sessions and tanking conversion rates. By moving away from the old "all or nothing" filtering of the past, GA4 allows you to identify specific bot patterns using dimensions like country (or any other that makes sense in your case) and build custom, filtered reports that exclude these anomalies in seconds.