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

Jump to bottom

pageUrl segment does not work with =@ contains operator for the Site Search Keyword Panel #9189

Closed
andrewbrown12 opened this issue Nov 9, 2015 · 8 comments
Closed

pageUrl segment does not work with =@ contains operator for the Site Search Keyword Panel #9189

andrewbrown12 opened this issue Nov 9, 2015 · 8 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone
Backlog (Help wan...

Comments

@andrewbrown12
Copy link
Contributor

pageUrl segment does not work with =@ contains operator for the Site Search Keyword Panel

Issue #2727 is a similar issue that has fixed this problem in other areas, but it is still present ont he Site Search Keyword Panel.

If I add a segment based on the URL containing one of our base URLs no results are show, however the Pages Following a Search panel correctly segments the data. To prove this issue I have swapped to doesn't contain operator and still get no results in the Site Search Keyword panel
@mattab
Copy link
Member

mattab commented Nov 25, 2015

Could you please paste one or two screenshots showing the problem? (ie. segment editor + site search results segmented and un-segmented?)

@andrewbrown12
Copy link
Contributor Author

Hi Matt,

Here is the Site Search Keyword with no Segment
piwik1

The config for contains mydomain segment

piwik2

This results in no entries in the panel even though most of the searches are from this domain
piwik3

Trying the inverse doesn't contain mydomain segment
piwik4

Still returns no results, which indicates to me that the Segmentation by Page URL isn't working.
piwik5

Andy

@mattab
Copy link
Member

mattab commented Nov 27, 2015

can you try to remove https from the segment, does it work better?

@andrewbrown12
Copy link
Contributor Author

I've just tried without https and still doesn't work.

Andy

@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Dec 23, 2015
@mattab mattab added this to the Short term milestone Dec 23, 2015
@mattab
Copy link
Member

mattab commented Dec 23, 2015

Maybe this issue is related to #8878 and #8972

@mattab
Copy link
Member

mattab commented Jul 1, 2016

This was also reported in the forums:

I've tried doing so by building a segment where 'Page URL' 'equals' << page URL name >>. I think I have segmented visitors that have visited this page, among other pages and expect the other pages to also show in the pages overview. However, I can only see this specific page in the Actions > Pages overview.

The issue lies in how Piwik implements segmentation when one is segmenting based on actions dimensions. We will likely fix this issue in a next version. this PR will help us: #10264 cc @tsteur

@mattab mattab modified the milestones: 3.0.0, Mid term Jul 1, 2016
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Jul 1, 2016
@mattab mattab mentioned this issue Jul 1, 2016
Closed
@mattab
Copy link
Member

mattab commented Sep 22, 2017

Marking as duplicate of #11900

@mattab mattab closed this as completed Sep 22, 2017
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Oct 12, 2017
@mattab
Copy link
Member

mattab commented Oct 27, 2019

This should be fixed in Matomo 3.12.0 which will be released tomorrow - if you still experience this issue then, let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
2 participants
@mattab @andrewbrown12