I did some experiments and know that “Visits by Visit Number” show the correct result only if visitors used cookies. If they did not use cookies or you send a request with “PHP Tracking Client”, it will be incorrect independs set UserID or not. But I think it’s wrong, cause if I set UserID, I must have absolutely full information. Can you fix this bug, please?
Lukas
(Lukas Winkler)
November 4, 2020, 9:47am
2
Hi,
This sounds a bit like
opened 10:20AM - 19 Feb 20 UTC
closed 08:03PM - 21 Jul 20 UTC
duplicate
Regression
I'm setting a User-ID, when a user visits a given Site. On a certain action, I'm… triggering a goal serverside with his User-ID as a parameter (and a token). Effect after the Update from 3.12 to 3.13.2 is that the serverside triggered action is not only stored in another visit (which would be ok), but also fails to recognize the web-visitor with the same User-ID. For reference, the before/after screenshots:
Before (Visitor recognized -> new visit but returning visitor):
![userid-before1](https://user-images.githubusercontent.com/1018973/74825044-82a6c500-5309-11ea-8c28-bc30cf131904.jpg)
After (Visitor is not recognized -> Visit is not returning -> new visit and new visitor):
![userid1](https://user-images.githubusercontent.com/1018973/74825088-9a7e4900-5309-11ea-83f9-dbbce2c70ea4.jpg)
Serverside call:
https://example.com/piwik.php?token_auth=XXX&cdt=2019-08-07 18:56:10&idgoal=3&revenue=1234&idsite=X&rec=1&r=13454&uid=1234567890
In config, trust_visitor_cookie is disabled.
The reason for that is this change: https://github.com/matomo-org/matomo/commit/ea5a14bdf8aa9608cdc2ab7d5c8236a5ff1eb3e2#diff-6700aaf1ce500fe51e284b9ec6f01b01
The change works in the right direction, but now, a User-ID is only assigned to the same visitor, when also the config_id matches. This doesn't make sense, because the main use case is for example a user who logs into a website with different devices (GDPR aside, but the User-ID is for example the customer ID). This user should be recognized as the same visitor (not necessarily the same visit, but at least the same visitor). @MichaelHeerklotz
Refs https://github.com/matomo-org/matomo/pull/14360
which has been fixed in Matomo 4