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 on Acquisition > Websites sub-table does not open the right visits #14918

Closed
mattab opened this issue Sep 29, 2019 · 1 comment · Fixed by #14933
Closed
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Sep 29, 2019

I think this is a regression but not sure exactly when it was introduced.

Reproduce

  • in acquisition > websites > click on a website Domain, it opens the sub-tables with list of pages for that website
  • Open Segmented Visitor Log
  • Reproduce URL

Got:
Screenshot from 2019-09-30 11-59-02

The segment is incorrect, it says referrerUrl==here_is_path_of_the_page but we expected instead the segment to include the full Referrer URL, not only the path.

Expected the Segmented Visitor Log to use the right "segment" to fliter only people who came from this page.

@mattab mattab added Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should. labels Sep 29, 2019
@mattab mattab added this to the 3.12.0 milestone Sep 29, 2019
@tsteur
Copy link
Member

tsteur commented Sep 30, 2019

FYI: If it's not easy fixable we will simply remove the segment completely.

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. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants