For support questions, please consider using Gitter - Chat
I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
After calling resetUser(), there should be an other method to call to avoid each event to be tracked in a distinct visit (when the same user is doing actions)
What is the motivation / use case for changing the behavior?
When resetUser() is called then the property _paq.push(['appendToTrackingUrl', 'new_visit=1']); is set. This implies that each futur event or page tracked will create a new visit for this.
In my case, i use resetUser() when user logs out from my application. If I log back with new credentials there should be a way to reset visit like this _paq.push(['appendToTrackingUrl', '']); and track all events of new user in the same visit.
MikaStark
commented
1 year ago
For support questions, please consider using Gitter - Chat
I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior? After calling resetUser(), there should be an other method to call to avoid each event to be tracked in a distinct visit (when the same user is doing actions)
What is the motivation / use case for changing the behavior? When resetUser() is called then the property
_paq.push(['appendToTrackingUrl', 'new_visit=1']);is set. This implies that each futur event or page tracked will create a new visit for this.In my case, i use resetUser() when user logs out from my application. If I log back with new credentials there should be a way to reset visit like this
_paq.push(['appendToTrackingUrl', '']);and track all events of new user in the same visit.please run the following and copy the output