See
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.
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
Count of visits from this visitor including current Visits that were the visitor's nth visit
1 times 179,528.00
2 times 16,412.00
3 times 6,006.00
4 times 3,389.00
5 times 2,371.00
6 times 1,819.00
7 times 1,469.00
8 times 1,236.00
9-14 times 4,590.00
15-25 times 3,997.00
26-50 times 3,880.00
51-100 times 2,665.00
101-200 times 958.00
201+ times 1,481.00
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.
where would this specific report be placed?
I would say Visitor > Engagement report page (already built using 2 plugins outputs).
(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...).