@joelanman opened this Issue on July 28th 2015

Using Piwik 2.8.3-1

On our project we've set up an AB test, where a page we think might be a problem is skipped for A and not for B.

The A journeys trigger a virtual page view on Piwik (say "skipped page" ) , but when we segment on [Page name is " skipped page"] the only page these users see according to the report is "skipped page" - no other pages in their journeys are shown.

Segmenting on page title/url in general doesn't seem to be working. It's as if you just ran a search on title/url: the page you search for appears, but no other pages on the journey, which is what I'd expect.

Should segmenting by page title work?

@Veda commented on August 26th 2015

An update on the issue raised by @joelanman.

We upgraded piwik to 2.14.3 hoping url truncation and segment issues around page title/url would be fixed. Issues seem to still exist.
We would appreciate if someone could take a look and respond to confirm that they are known issue. If not please point us in the right direction.

Many Thanks.

@mattab commented on September 11th 2015 Member

Could you paste a screenshot showing the problem? Ie. visitor log for a given user, without segment, and then for a given segment. Or maybe you can reproduce on demo.piwik.org and send links to reproduce?

@Veda commented on September 11th 2015

Hi Matthieu,

Thanks for your response.

In order for us to reproduce the issue, we need to create a custom segment which needs login credentials in your demo environment. We have attached the screenshots of the behaviour we have in one of our test environments. Let us know if you need any extra information.

The segment in the journey attached is created with pageURL and doesn't work as expected. The issue issue exists for pageName too. We expect it to work like EntryPageUrl segments do (return all page urls in the entire journey that contain segmented page url/name).


Many Thanks

@joelanman commented on September 14th 2015

@mattab thanks for looking into this - appreciate any pointers you could give to help us investigate further

@mattab commented on September 14th 2015 Member

The segment in the journey attached is created with pageURL and doesn't work as expected.

It seems to work as expected from your screenshots?

when you segment on "Entry page Url" then it selects all visits who started their visit on this entry page url. it's expected you get all other kinds of URLs that were visited by the users during their visit.

@joelanman commented on September 15th 2015

the Entry page URL example (2nd and 3rd screens) seem to work

the Page URL example (4th and 5th screens) do not. The only URL listed in the report is sign-in. As you say, it ought to be all the other URLs that were visited by users (who saw sign-in) during their visit.

@mattab commented on September 15th 2015 Member

In this case, no: the report only shows those URLs you filter to.

Maybe what you want is something like Segment Sequence #7533

@Veda commented on September 15th 2015

Thanks @mattab for clarifying the way page URL/Name segments are supposed to work.

@joelanman commented on September 15th 2015

@mattab To confirm, does that mean segments work differently to Google Analytics here?

Normally, a segment means 'filter all reports to just sessions where X applies'.

So normally, a page URL segment would filter to 'sessions where the page URL X was seen' - this is the behaviour seen in GA.

I don't really understand how a segment is just showing one URL in this report - as no sessions saw just this one URL. If this is by design, whats the difference between a page URL segment on the Pages report, and a simple search (in the box at the bottom) on Pages report?

This Issue was closed on September 15th 2015
Powered by GitHub Issue Mirror