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

Segmented visitor log in a goal page doesn't forward the selected segment #18776

tsteur opened this issue Feb 11, 2022 · 0 comments
Bug For errors / faults / flaws.


Copy link

tsteur commented Feb 11, 2022

To reproduce visit a goal page and have a segment applied. For example

Then click on the link for segmented visits log.

It makes a request like this where it only contains the segment for the currently viewed segment, but I would have expected that it also prepends the originally selected segment. Meaning I would have expected it combines visitConvertedGoalId%3D%3D7 and visitConvertedGoalId%3D%3D4 using AND. However, it only has visitConvertedGoalId%3D%3D4 in the request currently.

As a result, I can't actually view the visits that converted this goal using the applied segment and I get a much higher number of visits in the visits log than I should get. I thought we had an issue for this already, or fixed it in the past, but doesn't seem to be the case (couldn't find it).

Update: I'm actually thinking the segment might not work correctly when combined. Possible that we can't fix this easily as I think Matomo can't find visitors that converted two different goals in the visit (or performed two different actions in one visit) because I think Matomo can only find people based off one action. Refs #7533 .
In that case appending above segment would always show "no data" in the visits log possibly. Meaning until #7533 is fixed we would possibly need to hide the "segmented visits log" link when a segment is selected as it cannot show the right data.

@tsteur tsteur added the Potential Bug Something that might be a bug, but can't be reproduced (yet). label Feb 11, 2022
@sgiehl sgiehl added Bug For errors / faults / flaws. and removed Potential Bug Something that might be a bug, but can't be reproduced (yet). labels Nov 11, 2022
@sgiehl sgiehl added this to the For Prioritization milestone Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Bug For errors / faults / flaws.
None yet

No branches or pull requests

2 participants