# Data from different users within the same organization being recorded to the same Visitor ID

**URL:** <https://community.piwik.pro/t/data-from-different-users-within-the-same-organization-being-recorded-to-the-same-visitor-id/5396>\
**Category:** Reports and working with data\
**Created:** [October 10, 2025, 10:33am UTC](https://community.piwik.pro/t/data-from-different-users-within-the-same-organization-being-recorded-to-the-same-visitor-id/5396 "2025-10-10T10:33:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mika](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mika](https://community.piwik.pro/u/Mika)\
**Post date:** [October 10, 2025, 10:33am UTC](https://community.piwik.pro/t/data-from-different-users-within-the-same-organization-being-recorded-to-the-same-visitor-id/5396/1 "2025-10-10T10:33:51Z")

</div>

What are the required conditions for visits from different users within the same organization to be recorded under the same Visitor ID?

I have noticed that this happens in some cases, but not always. For example, I asked a colleague to visit two specific pages on our website, and afterwards I visited two other pages myself. When I checked the Tracker debugger, I saw that both of our visits appeared under the same Visitor ID.

There were also other events in the same flow, triggered by other users. A few hours later, when I checked the Tracker debugger again, there were already over 200 events associated with the same Visitor ID. This is very confusing and clearly distorts the analytics statistics if many sessions done by many users is shown as one session.

---

<div class="post-metadata">

**Author:** ![rmastop](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/rmastop/32/29_2.png) [@rmastop](https://community.piwik.pro/u/rmastop)\
**Post date:** [October 10, 2025, 11:40am UTC](https://community.piwik.pro/t/data-from-different-users-within-the-same-organization-being-recorded-to-the-same-visitor-id/5396/2 "2025-10-10T11:40:33Z")

</div>

Hi @Mika

Piwik PRO by default uses a session hash to separate session from visitor one and visitor two.

In case devices that are similar, in the properties they send out, coming from the same IP address, there can be cases that they end up in the same session (as you are dealing with)

The solution would be to disable session hash and rely on cookies:

> **[How can I turn off a session hash? | Piwik PRO help center](https://help.piwik.pro/support/privacy/how-can-i-turn-off-a-session-hash/)**
>
> Sometimes, you may want to turn off a session hash and not use it to track visitor sessions. This can be due to privacy laws or other reasons. But keep in mind that without the session hash, counting visitor sessions may be less accurate. This hash...

Keep in mind when turning off Session hash, to turn on Use visitor cookies, otherwise each event will end up as a new session and visitor.

> **[How can I turn off visitor cookies? | Piwik PRO help center](https://help.piwik.pro/support/privacy/how-can-i-disable-cookies-for-visitors/#:~:text=Comparison%20of%20options)**
>
> Sometimes you may want to turn off visitor cookies and not use them to collect data. This may be because you want to comply with certain privacy laws or for other reasons. Without cookies, your data will be less accurate. That’s because cookies store...

Make sure to validate this with your privacy officer.

---

<div class="post-metadata">

**Author:** ![Mika](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mika](https://community.piwik.pro/u/Mika)\
**Post date:** [October 14, 2025, 11:40am UTC](https://community.piwik.pro/t/data-from-different-users-within-the-same-organization-being-recorded-to-the-same-visitor-id/5396/4 "2025-10-14T11:40:38Z")

</div>

@rmastop

Ok, I see. Thanks for the clarification!

We use cookie consenting on all our websites. And all sites have ‘Use a session hash’ and ‘Use visitor cookies’ enabled in the privacy/compliance settings.

Based on the article ‘How can I turn off a session hash’, I understood that disabling session hashes is safe for us. The only data loss is IP addresses that we do not use anywhere or in any way. Or am I missing something important?

---

<div class="post-metadata">

**Author:** ![rmastop](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/rmastop/32/29_2.png) [@rmastop](https://community.piwik.pro/u/rmastop)\
**Post date:** [October 14, 2025, 12:02pm UTC](https://community.piwik.pro/t/data-from-different-users-within-the-same-organization-being-recorded-to-the-same-visitor-id/5396/5 "2025-10-14T12:02:14Z")

</div>

Hi @Mika,

Indeed, when you currently have both Use session hash and Use visitor cookies, it would be best to disable the use session hash, both pre and post consent.

It will solve your merged sessions behaviour.
