Can it prove there's no internal traffic?

No. An export without an identifying dimension can't show internal traffic either way, and the result says so.

Which markers are checked?

internal, employee, staff, office, test and localhost by default.

What share is a problem?

More than 5% is flagged as a warning. Any amount of test revenue is worth excluding.

How do I set up GA4 internal traffic filtering?

Define internal traffic rules in the data stream settings, then create and activate a data filter that excludes them.

No. It's parsed to produce the result, and the findings expire after 7 days.

Free tool by Clarvivo · no login

Find internal traffic contaminating your analytics export

Upload a GA4 traffic export to identify clear staff, QA, staging and test markers before they distort acquisition decisions.

GA4 traffic export

Upload a GA4 source, hostname, traffic type, or user-type export. We look for clear staff, test, QA, staging, and internal markers.

This tool answers: How much of this analytics export looks like employee, QA, staging, or internal traffic?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

Internal traffic inflates the numbers you make decisions from. Staff checking the site, QA testing checkout, developers on staging hostnames, agencies reviewing landing pages: all of it lands in analytics as sessions, events and sometimes conversions.

For a small site the effect can be large. A few people loading the site every day can make up a noticeable share of sessions, flatten conversion rates and add test purchases to revenue. GA4's internal traffic filter helps, but only if it's defined, activated and covers every way your team accesses the site.

This checker scans a GA4 export for clear internal markers and tells you what share of traffic they represent.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

Upload a GA4 export
A source, hostname, traffic type or user-type export from GA4, with sessions if available.
We look for internal markers
By default we match internal, employee, staff, office, test and localhost in the chosen dimension. Rows that match are listed.
We measure the share
Matching sessions (or rows) are compared with the total. A share above 5% is flagged as a warning.

Common causes and fixes

Internal traffic filter not active: GA4 filters are created in testing mode. Activate the filter once you've verified it.
Office IP list out of date: Remote work means staff traffic comes from many IPs. Consider a cookie- or user-property-based internal flag instead.
Staging hostnames sending data: Staging and preview environments using the production measurement ID pollute reports. Use a separate property or block non-production hostnames.
Test orders not excluded: QA purchases appear as revenue. Use test modes or a test flag that's excluded from reporting.

Frequently asked questions

Can it prove there's no internal traffic?: No. An export without an identifying dimension can't show internal traffic either way, and the result says so.
Which markers are checked?: internal, employee, staff, office, test and localhost by default.
What share is a problem?: More than 5% is flagged as a warning. Any amount of test revenue is worth excluding.
How do I set up GA4 internal traffic filtering?: Define internal traffic rules in the data stream settings, then create and activate a data filter that excludes them.
Is the file stored?: No. It's parsed to produce the result, and the findings expire after 7 days.

Keep acquisition reporting about customers.

Clarvivo gives channel decisions a cleaner revenue baseline.

See cleaner acquisition performance

What this tool reads, and what it keeps

Your export is parsed to produce the diagnostic and is not stored as a file.
Only aggregate columns and redacted row references are used in the result.
Findings expire after 7 days and are never used to train models.