The identity behind the label
The browser SDK creates a random anonymous ID and keeps it in a first-party cookie, with localStorage or memory as fallbacks. A person returning tomorrow in the same browser keeps the same anonymous ID and counts as a returning visitor. Cleared cookies, a private window, or another device create additional IDs.
The date range matters
Across multiple days, distinct anonymous IDs count each browser once. They still do not equal distinct people, because one person can use several browsers or devices. State the identity unit whenever you share a count. An explicit user ID sent by your app can associate identified activity across devices.
Do not mix populations
The Users tab represents explicitly identified accounts. Anonymous represents anonymous IDs without a known user. Adding these totals does not necessarily count distinct people, because one person can appear in both observed populations.
Frequently asked questions
Is a visitor the same as a person?
No. The anonymous ID identifies a browser, not a verified person. One person can use several browsers or devices, and cleared cookies or a private window create additional IDs. When you share a visitor count, state the identity unit. An explicit user ID sent by your app can associate identified activity across devices.
Does a returning visitor count as new the next day?
No, not in the same browser. The browser SDK creates a random anonymous ID and keeps it in a first-party cookie, with localStorage or memory as fallbacks. A person who returns tomorrow in the same browser keeps the same anonymous ID and counts as a returning visitor.
Can I add the Users and Anonymous totals?
Not to count distinct people. The Users tab shows explicitly identified accounts. Anonymous shows anonymous IDs without a known user. One person can appear in both populations, so the sum of the two totals does not necessarily equal the number of distinct people who used your site.