Internal / Test User

An internal / test user refers to a team's own traffic — developers, QA, support and internal monitoring — that lands in the stats and, if not separated, pollutes the reports.

This concept is a data-hygiene problem, not a feature: your own team's visits are not real user behavior, yet they are recorded by the same script and can skew sensitive metrics. The effect is larger on a low-traffic site; a few developers refreshing a page a hundred times a day can render conversion rate or time-on-page meaningless. There are three ways to handle it: not loading the script on internal and staging environments at all, filtering team traffic by a stable signal, and excluding non-human traffic by default. The often-forgotten point is that an internal user is usually not detected automatically; you must deliberately decide how to separate them, or months of polluted data accumulate.