search

matomo-org / matomo

Empowering People Ethically with the leading open source alternative to Google Analytics that gives you full control over your data. Matomo lets you easily collect data from websites & apps and visualise this data and extract insights. Privacy is built-in. Liberating Web Analytics. Star us on Github? +1. And we love Pull Requests!
https://matomo.org/
GNU General Public License v3.0
19.7k stars 2.62k forks source link

Device and other visitor information gets lost when using userId feature as two visits from two different visits get merged #9834

Open bruthe57 opened 8 years ago

bruthe57 commented 8 years ago

I have an issue on visitor profile with userid activated. if userA from his deviceA browse my website, I can find in visitor log, his profile with some information related to device A (browser, os, ip, etc ..) if userA switch browsing from device A to another deviceB, this traffic is shown in the visit initiated with deviceA and I can't find any trace of deviceB !!!

After some test, I found that is related to the session. if I wait the session timeout (default 30min), and userA use his deviceB, I can find a new visit with deviceB.

The information of the device seems to be related to the entire visit and not to the pageview...

hpvd commented 8 years ago

One idea for optimizing visitor profile would be to 1) ad a list of used devices (similar to list of locations, see https://github.com/piwik/piwik/issues/9702) 2) and show the used device at head of each visit shown in visitor profile

=> what do you think?

bruthe57 commented 8 years ago

these optimizations would be the chery on cake, but my main problem is that when I use the userid, piwik merge two sessions from differents devices in the same visit! and we lose information about the second device ... :-/

tsteur commented 8 years ago

That's a bug and it won't be trivial to fix unfortunately. I think we already have an issue for this but I can't find it right now.

FYI: I changed the title so it'll be easier to find this one.

AAudusseau commented 4 years ago

Hi! Any news for this issue? Is there a workaround? Thanks

tsteur commented 4 years ago

@AAudusseau The only way to fix this would be to create a new visit every time a user "logs in".

AAudusseau commented 4 years ago

I see. Thanks for the answer