-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
BugFor errors / faults / flaws / inconsistencies etc.For errors / faults / flaws / inconsistencies etc.RegressionIndicates a feature used to work in a certain way but it no longer does even though it should.Indicates a feature used to work in a certain way but it no longer does even though it should.
Milestone
Description
If "disableBrowserFeatureDetection" is enabled and remember(Cookie)ConsentGiven is called, a new visitor is recognized
Expected Behavior
After calling remember(Cookie)ConsentGiven, the same visitor should be recognized and no new (unique) visitor should be created.
Possible Solution
When re-enabling browserFeatureDetection, try to sync / match the "old" config_id without browserFeatures in the fingerprint.
Steps to Reproduce (for Bugs)
- Enable disableBrowserFeatureDetection
- Call remember(Cookie)ConsentGiven
Context
Giving consent enables the browserFeatureDetection - https://github.com/matomo-org/matomo/blob/4.x-dev/js/piwik.js#L6030 - That's why the current visior is not recognized again (and a new visitor is created), because the config_id (fingerprint) changed.
Your Environment
- Matomo Version: 4.10.1
- Browser: Multiple tested
Metadata
Metadata
Assignees
Labels
BugFor errors / faults / flaws / inconsistencies etc.For errors / faults / flaws / inconsistencies etc.RegressionIndicates a feature used to work in a certain way but it no longer does even though it should.Indicates a feature used to work in a certain way but it no longer does even though it should.