Skip to content
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

Visitor Profile "First visit" does not always show the very first visit #12373

Closed
mattab opened this issue Dec 19, 2017 · 4 comments · Fixed by #12375
Closed

Visitor Profile "First visit" does not always show the very first visit #12373

mattab opened this issue Dec 19, 2017 · 4 comments · Fixed by #12375
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Dec 19, 2017

As reported in #11996 (comment) by @blynch11p

I've been tinkering with v3.2 and I have many users that top 100 visits. The Visit count is starting at #100 (not a big deal, really) but the secondary issue is that the "First Visit" date is (in my case) whatever the date for Visit #91 is in the Visitor Profile window (ie: the date for the oldest of the 10 visits that load initially. This does not update when I click 'Load more visits'). So if the user visits a site every day, visit #91 / First Visit is only 10 days back, rather than >100 days or > 3 years or whatever. I believe in prior Piwik versions (I'm coming from 3.0.4) "First Visit" only ever showed the text Visit #100 for these use cases, but now "First Visit" is less accurate.

Current behavior

Currently "First visit" will only be the 10th oldest visit, but there could have been 50 visits or more.

Expected behavior

  • The First visit panel in the Visitor Profile should refer the very first visit of the user.
    • ideally it's possible to query this very first visit very quickly in Mysql,
    • but if not we can always use the first visit in the live_visitor_profile_max_visits_to_aggregate limit (100 by default) which would restore the previous behavior before we recently regressed
@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Dec 19, 2017
@mattab mattab added this to the 3.2.2 milestone Dec 19, 2017
@sgiehl
Copy link
Member

sgiehl commented Dec 20, 2017

Showing the very first visit would be possible, but I won't change it that way, as it would make the visitor profile inconsistent. All data would be calculated based in the last 100 visits. Why should the first visit should show something different. But I will add a small text in the beginning of the summary showing a notice that the profile shows only X of Y visits (if there are more visits than defined in config)

@blynch11p
Copy link

Matt, thanks for creating the issue ticket.

To put a screenshot to it, the info on the left (First Visit) is my primary concern. Since First Visit is not actually the FIRST, but the 10th most recent. For this user, their true First Visit was March 8, 2017, not November 22, 2017.

The info on the right (showing Visit 100, rather than some number greater than 100), while not entirely correct, isn't my concern here.

screenshot from 2017-12-20 12-13-29

@mattab
Copy link
Member Author

mattab commented Jan 8, 2018

All data would be calculated based in the last 100 visits. Why should the first visit should show something different.

@sgiehl in that case we want to implement a "First" visit reporting, as in, showing the very first visit. This is because how user found the website in the first place is very valuable info, and often there is only a single channel used during 100+ visits. The first visit is where the only referrer may be found... Also, knowing the time of the first visit is interesting and the info only found in this visit.
so ideally we still write "First visit" and load the very first visit summary there.

edit: reported by customer too

@mattab mattab modified the milestones: 3.4.0, 3.3.1 Feb 1, 2018
@mattab
Copy link
Member Author

mattab commented Mar 22, 2018

This great little improvement has been made! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants