Put Vireo and GA4 side by side and check a single day: the numbers come close. Stretch the range to a month and the gap opens up.

Say 1,000 readers each visit your site on three separate days in a month. GA4 would report about 1,000 users, because it recognizes each reader across days. Vireo would report about 3,000 visitors, because it counts each reader again every day. Both tools are doing what they say they do.

Vireo’s Visitors card counts daily-unique browsers, rebuilt from scratch every day. GA4 counts users it recognizes across days, by a cookie, and sessions that end after 30 minutes of inactivity.

How Vireo decides two views are the same visitor

Every visitor gets a code. When a pageview arrives, Vireo joins the IP address and the browser’s user-agent string as “IP address|user-agent”. It runs that through HMAC-SHA256, keyed with a secret salt, and keeps the first 32 hex characters.

The salt is a random value, one per day, created a day ahead so it’s ready at midnight. The day follows your site’s WordPress timezone, so the salt, and with it every visitor code, changes at your site’s local midnight.

Vireo keeps yesterday’s and today’s salts, plus the next one created ahead, and deletes older ones. Vireo deletes the records that tell visitors apart within a day after two days. Once that day’s salt is gone, nobody can work out which address a code came from. The collect endpoint hashes with the current day’s salt only, so a reader who returns tomorrow gets a different code.

Vireo stores nothing on the visitor’s device. It sets no cookies and uses no local storage for tracking. The privacy docs have the retention details, and the post on analytics without cookies covers what that changes in practice.

What that means for your numbers

Within a day, Vireo counts each visitor once, on their first counted pageview. Everything else that day from the same code isn’t a new visitor. However many pages a browser reads today, it’s one visitor today.

Tomorrow the count starts again. Vireo counts a reader who comes back the next day as a new visitor.

On a longer range, the Visitors card adds up each day’s visitors. That’s why it’s labeled “daily uniques, summed”. That’s where the hypothetical’s 3,000 comes from.

Where a code can merge or split people

The code comes from IP address plus browser, so it can be off in two directions. Two people on the same network with the same browser string can share a code and count as one. One person who moves from phone data to Wi-Fi, or whose IP address changes, gets two codes in a day.

The free “Shorten IP addresses” setting (added in 0.23.0, off by default) zeroes the last part of the IPv4 address. With it on, Vireo counts visitors on the same network as one more often. Switching it on or off mid-day starts a new code for everyone from that point.

What a visit is in Vireo

Vireo’s Overview reports pageviews and visitors.

Bounce rate follows the same daily logic. It’s the share of a day’s visitors who viewed exactly one page, counted per daily visitor. Someone who reads one page on Monday and one on Tuesday bounces on both days. The bounce rate and time on page post goes through how those numbers behave.

Pro adds a session view. The Live screen’s Active sessions card shows each current visitor’s trail of pages, and Pro keeps those live hits for 30 minutes. Before it deletes them, Pro records each trail’s first and last page, which is where its entry and exit pages come from.

How GA4 defines users and sessions

Google splits its user metrics three ways. “Total users” is “the number of unique users who triggered any event in the specified date range.” “New users” counts the new unique users who logged the first_open or first_visit event in the date range. “Active users” counts the unique users who engaged with your site or app in the date range.

Google’s page on Analytics sessions defines a session as “a period of time during which a user interacts with your website or app.” By default a session times out after 30 minutes of inactivity. The same page says session and user metrics are calculated through an estimation.

Recognizing the same user across days takes something that stays on the device. Google’s cookie documentation says the _ga cookie is “used to distinguish users,” with a default expiry of 2 years. A second cookie, ga followed by the container ID, is “used to persist session state.” GA4 tags use first-party cookies to distinguish unique users, and unique sessions from a single user.

So GA4 can say “this is the same person as last Tuesday” because a cookie told it so. The cookie also lets it group a person’s activity into sessions. It does mean the tool stores something on your visitors’ devices, and whether that needs consent on your site is a question for your own adviser.

Reading both without fooling yourself

Compare single days when you check one tool against the other. A day’s Vireo visitors and that day’s GA4 users should land in the same neighborhood. They won’t match to the digit, because bots, exclusions and timezones differ between tools. The post on why analytics tools show different numbers covers those, along with Search Console.

Vireo also leaves some traffic out entirely. It doesn’t count logged-in roles ticked under Settings, General, “Do not count” (administrators by default), bots, or visitors sending Do Not Track or Global Privacy Control, among others. Views per visitor are capped at 5 per page and 50 in total per day, and the extras go into the bot report. The what counts page has the full list.

For a week or a month, skip lining Vireo’s summed visitors up against GA4’s users. If you need one figure to compare across tools, use pageviews. They don’t depend on how a tool recognizes a person.

Compare Vireo to Vireo over time. A week-over-week change in daily visitors means the same thing every week, because the counting rule stays the same. Keep the definition in mind, though: a loyal audience that visits often lifts the number just as new readers do. The same goes for GA4 against GA4.

If you import your GA4 history, expect the same kind of difference. Imported history arrives as daily users, so a month of imported data reads higher than GA4’s own monthly user count.

What Vireo tells you

Vireo tells you how many distinct browsers showed up each day, which pages they viewed, and how that moves from day to day. Because the visitor code resets at midnight, nothing Vireo keeps can be traced back to a person once two days have passed.

When the Visitors number and GA4 users disagree, check the date range first. On a one-day range the tools should broadly agree. If the gap only opens on longer ranges, you’re looking at two definitions of “visitor”.