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

Entry pages segmented visitor log is showing wrong URLS #15027

Closed
KarthikRaja1388 opened this issue Oct 21, 2019 · 6 comments
Closed

Entry pages segmented visitor log is showing wrong URLS #15027

KarthikRaja1388 opened this issue Oct 21, 2019 · 6 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. worksforme The issue cannot be reproduced and things work as intended.
Milestone

Comments

@KarthikRaja1388
Copy link

Issue: When viewing the segmented visits log for a particular URL under "Behaviour > Entry pages", it's displaying the wrong URLs as the entry page.

Steps to reproduce:

  1. Navigate to Behavior->Entry Pages
  2. Ensure the View Mode is Flat (not Hierarchical)
  3. Sort by Entrances descending (most common entrance page at the top)
  4. View Segmented Visitor Log for first item
  5. Observe that the header of the page is "Visit Log showing visits where Entry Page URL is "[correct URL]" the entry page for the first URL is not correct

Note: this is reproducible in the demo site at https://demo.matomo.org (Site: Demo-Site, date: 2019-09-25, Segment: All Visits)

Screenshot
Screenshot from 2019-10-21 14-03-01

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Oct 21, 2019
@tsteur tsteur added this to the 4.1.0 milestone Oct 21, 2019
@tsteur
Copy link
Member

tsteur commented Oct 21, 2019

Thanks @KarthikRaja1388

@pebosi
Copy link
Contributor

pebosi commented Mar 2, 2020

Seems to be fixed, can't reproduce in demo or my own installation

@dktcoding
Copy link

This is happening to me too, even when using Only track visits and actions when the action URL starts with one of the above URLs.

So far I tried invalidating the reports and regenerating them (which took almost 4 days to no effect).

Any clues on how to solve it?

We currently track a few moodle installations from a public university (around half a million students) and with the current epidemiological situation people started having time for statistics...

@dktcoding
Copy link

In the example it shows that the user was first seen 4 days ago, but the visit log show an entry from one year ago, on another site.

Screenshot_20200404_031805

I tried deleting all the caches, doing mysqlcheck -o and when doing:

SELECT * FROM matomo_log_visit 
LEFT JOIN matomo_log_link_visit_action ON matomo_log_visit.idvisit = matomo_log_link_visit_action.idvisit 
LEFT JOIN matomo_log_action ON matomo_log_action.idaction = matomo_log_link_visit_action.idaction_url 
LEFT JOIN matomo_log_conversion ON matomo_log_visit.idvisit = matomo_log_conversion.idvisit 
WHERE idvisitor = UNHEX('ee9a851e8ae7131c');

It retrieves all of the correct results that are shown (not the incorrect ones)...

Any clues? I would really hate to loose 3 years worth of statistics and then have it happening again...

@tsteur
Copy link
Member

tsteur commented Apr 5, 2020

@dktcoding this sounds like a different issue and I recommend you create a new issue for this. We may need access to your Matomo if possible to understand things. Like you could create a user with view access for us and send us the credentials to hello at matomo dot org.

@mattab
Copy link
Member

mattab commented Aug 20, 2020

This seems fixed, @KarthikRaja1388 please re-open if you can still reproduce this

@mattab mattab closed this as completed Aug 20, 2020
@mattab mattab added the worksforme The issue cannot be reproduced and things work as intended. label Aug 20, 2020
@mattab mattab modified the milestones: 4.1.0, 4.0.0 Sep 9, 2020
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. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

5 participants