Unique visitor vs. the other numbers on your dashboard
A dashboard usually shows three related but different counts for the same traffic:
- Page views -- every single page load, including repeats. One visitor reading five articles is five page views.
- Sessions (visits) -- a burst of activity from one visitor, ended by a period of inactivity (commonly 30 minutes) or a new day. One visitor can rack up several sessions in a week.
- Unique visitors -- the distinct people behind all of that. One visitor having three sessions and reading five pages is still one unique visitor.
Unique visitors answer "how many different people" rather than "how much activity." It is the number to watch when you want reach; sessions and page views are better for engagement and volume.
How a tool tells one visitor from another
No analytics tool can check ID cards at the door, so each one approximates identity. Cookie-based tools drop an identifier in the visitor's browser and recognise it on return; cookieless tools like TrackTrendy instead combine signals available on each request (such as IP range and browser details) into a daily rotating, one-way hash, so no persistent identifier is stored and nothing can be traced back to a person. Both approaches are estimates, not a perfect headcount: a person switching from phone to laptop looks like two visitors to any tool, cookie-based or not.
Why "unique" resets with the time window
Uniqueness is only ever unique inside the period you have selected. Someone who visits on Monday and again on Friday counts as one unique visitor for the week, but as one unique visitor on Monday's daily report and a separate one on Friday's daily report. Widen the date range and the same people get folded back together, which is why daily totals added up across a month will usually overshoot the month's real unique-visitor count.
How Google Analytics 4 counts this today
GA4 does not display a metric literally labelled "unique visitors" -- it reports Active users instead, and the definition is specific. According to Google Analytics Help, a user becomes "active" when Analytics records an engaged session: one that lasted 10 seconds or longer, included a conversion event, or had 2 or more page or screen views. A visit that bounces in 4 seconds with a single page view does not count toward Active users at all, even though it reached the server.
That threshold is also why month-over-month comparisons can look odd: GA4's default data retention keeps user-level data for only 2 months before it ages out, per Google Analytics Help, so a 90-day lookback will quietly lose some of the identifiers behind older unique counts even if the aggregated report still shows a number. For the full mechanics of GA4's counting, including why it can disagree with the unique-visitor numbers you remember from Universal Analytics, see our complete guide to unique visitors in Google Analytics.
What the number is good for
Unique visitors (or Active users, in GA4's language) tell you reach: is a new campaign, a guest post, or a social share actually bringing new people, or just more clicks from the same crowd? Use it alongside conversions and revenue, not instead of them -- a large, unique audience that never buys is a marketing problem, not a measurement one.