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.75k stars 2.63k forks source link

New_Visit=1 parameter in connection with Content-tracking / events (2.12.0) #7557

Open peterbo opened 9 years ago

peterbo commented 9 years ago

When the parameter new_visit=1 is appended, and content / event tracking is in use, a new visit is created for every single request (goal / event / content impression) resulting in a lot of new visits with 0 actions (since these are not counted as action).

The expected behavior would be if the new_visit=1 parameter would only account for the main tracking request (or request counted as "action") and not for "sub"-requests like event / goal / content requests.

This is open for discussion since I'm not 100% sure, what to expect from this behavior and what the overall use cases are.

mattab commented 9 years ago

Hi @peterbo

Thanks for the suggestion.

a Workaround may be to append new_visit=0 after tracking the pageView and right before the Contents pieces are tracked with trackAllContentImpressions or via trackVisibleContentImpressions

This is open for discussion since I'm not 100% sure, what to expect from this behavior and what the overall use cases are.

+1