New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Loyalty report "Visitors who visited the website 1 time, 2 times, etc." #536
Comments
Moved Recency report requirement in #583 |
This is also easy to implement now, because log_visit contains the field piwik_log_visit.visitor_count_visits which is the count of visits. This is set using the first party cookies counter. We can therefore query GROUP by this field and get the report. The GA breakdown is as follows: Count of visits from this visitor including current Visits that were the visitor's nth visit Percentage of all visits
We can reuse the same breakdown as it is relevant and consistent. See also similar #584, #2031 |
Got a question about this issue: where would this specific report be placed? Thanks in advance. |
|
(In [5378]) Fixes #584, #536, #2031 - Kuddos to Benaka akka capedfuzz for this great patch!!! I did a few minor modifications in wording and metadata output
Notes
|
It seems Visitors > Engagement > "Visits by visit number" column titles are not clickable/sortable, is it by design ? The other two reports are ok. |
I disabled sorting for that report since the other two VisitorInterest reports also disable it. I don't know if this is the desired behavior, but I could make some changes when I submit a patch for #583 (shouldn't be too long now...). |
Milestone 1.8.x Piwik 1.8.x deleted |
- Loyalty: M people visited N times
See
- [Recency Frequency Monetary](http://en.wikipedia.org/wiki/RFM)
- [I Got No Ecommerce. How Do I Measure Success?](http://www.kaushik.net/avinash/2007/07/i-got-no-ecommerce-how-do-i-measure-success.html)
We probably need to keep track of the count of visits for each visitor in a new table, to be able to tell this stat on more than 1 day range.
The text was updated successfully, but these errors were encountered: