# Updating Email Addresses for Different Users with the Same IP **URL:** \ **Category:** Product Support\ **Created:** [May 30, 2023, 9:29am UTC](https://forum.mautic.org/t/updating-email-addresses-for-different-users-with-the-same-ip/28177 "2023-05-30T09:29:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![desancheztorres](https://avatars.discourse-cdn.com/v4/letter/d/3be4f8/32.png) [@desancheztorres](https://forum.mautic.org/u/desancheztorres)\ **Post date:** [May 30, 2023, 9:29am UTC](https://forum.mautic.org/t/updating-email-addresses-for-different-users-with-the-same-ip/28177/1 "2023-05-30T09:29:58Z")
**Your software** My Mautic version is: 4.4.3 My PHP version is: 8.0.23 My Database type and version is: 10.8.4-MariaDB **Your problem** My problem is: We have a Drupal page tracked by Mautic. Drupal uses the script in the head section to track that page. Mautic correctly receives the data from the Drupal user, which is considered a contact. Let’s imagine that I’m the one who enters a tracked Drupal page: **Email** : [des@gmail.com](mailto:des@gmail.com) **IP** : 88.90.90.90 Mautic receives my data, both the IP and the email, correctly. In the Mautic reports section, the table displays: **Email** : [des@gmail.com](mailto:des@gmail.com) **IP** : 88.90.90.90 Now, I log out of my Drupal user session and log in with a different user. This user has a different email but the same IP. **Email** : [oscar@gmail.com](mailto:oscar@gmail.com) **IP** : 88.90.90.90 Mautic receives the data from Drupal again, and although it receives the data correctly, instead of adding it as a new report with the same IP and a different email, Mautic updates all the email addresses associated with the IP that matches the last one sent: **Report 1:** **Email** : [oscar@gmail.com](mailto:oscar@gmail.com) **IP** : 88.90.90.90 **Report 2:** **Email** : [oscar@gmail.com](mailto:oscar@gmail.com) **IP** : 88.90.90.90 But it should be like this: **Report 1:** **Email** : [des@gmail.com](mailto:des@gmail.com) **IP** : 88.90.90.90 **Report 2:** **Email** : [oscar@gmail.com](mailto:oscar@gmail.com) **IP** : 88.90.90.90 As you can see, it updates all emails associated with the same IP address, without considering that the previous IPs belonged to different users. Steps I have tried to fix the problem: Disabling the IP tracking option in Mautic. \*\*Github issue: \*\* [Updating Email Addresses for Different Users with the Same IP · Issue #12350 · mautic/mautic · GitHub](https://github.com/mautic/mautic/issues/12350) ---
**Author:** ![Yosu\_Cadilla](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/yosu_cadilla/32/6206_2.png) [@Yosu\_Cadilla](https://forum.mautic.org/u/Yosu_Cadilla)\ **Post date:** [May 30, 2023, 10:10am UTC](https://forum.mautic.org/t/updating-email-addresses-for-different-users-with-the-same-ip/28177/2 "2023-05-30T10:10:37Z")
When multiple users are behind a firewall and share one IP, Mautic uses cookies to identify contacts. ---
**Author:** ![Yosu\_Cadilla](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/yosu_cadilla/32/6206_2.png) [@Yosu\_Cadilla](https://forum.mautic.org/u/Yosu_Cadilla)\ **Post date:** [May 30, 2023, 10:14am UTC](https://forum.mautic.org/t/updating-email-addresses-for-different-users-with-the-same-ip/28177/3 "2023-05-30T10:14:57Z")
> [@desancheztorres](#): > > Mautic mistakenly updates all the emails associated with that IP address. Can you provide some examples of: “Mautic mistakenly updates all the emails associated with that IP address.” Thahk you! ---
**Author:** ![dirk\_s](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/dirk_s/32/748_2.png) [@dirk\_s](https://forum.mautic.org/u/dirk_s)\ **Post date:** [June 4, 2023, 10:01am UTC](https://forum.mautic.org/t/updating-email-addresses-for-different-users-with-the-same-ip/28177/4 "2023-06-04T10:01:47Z")
Hi, I can’t confirm this. Did you clear cache after disabling IP based tracking? I do test with different browser instances (using different user profiles) with IP disabled. I never had this behaviour… Did you test with different browser instances? Otherwise you are still using the same cookie, which would explain the behaviour.