---
title: "Comment by StackShortlist on \"Our analytics counted US visitors twice every evening\" | Hashnode"
description: "The table of what midnight UTC means locally makes the bug obvious in a way prose would not: for Los Angeles the daily_key rotates at 4 to 5 pm, right in the mi"
url: "https://hashnode.com/posts/our-analytics-counted-us-visitors-twice-every-evening/6ad2483064d43830064d19da/comment/6ad2b86786a25f986438aaa9"
---

[Discussion](https://hashnode.com/posts/our-analytics-counted-us-visitors-twice-every-evening/6ad2483064d43830064d19da)

Comment [Our analytics counted US visitors twice every evening](https://hashnode.com/posts/our-analytics-counted-us-visitors-twice-every-evening/6ad2483064d43830064d19da)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/our-analytics-counted-us-visitors-twice-every-evening/6ad2483064d43830064d19da/comment/6ad2b86786a25f986438aaa9)

The table of what midnight UTC means locally makes the bug obvious in a way prose would not: for Los Angeles the daily\_key rotates at 4 to 5 pm, right in the middle of an evening session. It is a nice example of a privacy choice (rotating the key daily) quietly becoming a counting choice. Deciding the day boundary once, in one place, also fixes the related reports you mention, not just the visitor count.