Piwik now support full segmentation via the API only: http://piwik.org/docs/analytics-api/segmentation/
We want to be able to
Also, when creating a segment, you can add check 2 boxes
In the Reporting UI, there would be a new box probaby similar to current Calendar / Info box that would list the current Segment applied to the data.
It would open up (similarly to the calendar) to show the list of pre-created segments, or the "Add a new segment" link.
User can then click on the Segment link to ajax reload the report with the segment applied to all visible reports.
The list of segment will lists all Websites segment first, then all User segments.
Note: some of the UI logic to define segment can be similar to the one used to define custom alerts (#1486), in particular the "value" ajax suggestion would reuse the same code.
GA supports visitsToTransaction and daysToTransaction - is it equivalent to "visitConverted==1;daysSinceFirstVisit==X" ? maybe not
Summary: the UI will allow to create/edit/delete segments, we will add a new box next to the calendar to select currently applied segments.
BUGS to fix
At the same time, it would be nice:
Later version
In the V1, we will not compare the Segment data with the "All visits" data or allow to compare segments together. This feature would be very nice and is important to have, see also ticket to compare several date ranges #291
Requirements
I will ask Marcin to provide some mockups for the screens of this feature. Once we have them we can implement this new UI element.
Please post here any idea/feedback!
See also #2092
I'm wondering what that status of this feature is. It looks like you folks have been recently active on it.
The reason I ask is because I have need of segmentation in a 3rd party plugin I'm using/developing. I was just going to hack something together, but if you are far along I'd rather do it correctly.
No work has been done on the "UI to create Segment picker" but the backend of analytics segmentation works
I noticed in the Archive.php docs that you can set a segment. Is the segment archiving functional? It would be great to be able to use that
[http://qa.piwik.org:8080/phpdocs/Piwik/Piwik_Archive/Piwik_Archive.html#setSegment]
As per report in: http://forum.piwik.org/read.php?2,80293
there is a few issues when a segment is passed to the request with regards to graphs.
Once this is implemented, a typical workflow could be:
I really want to work on this feature so increasing priority as personal reminder :)
When implementing Segmentation UI, let's think about Visitor Log. A Frequently requested feature is to be able to "filter" the visitor log to specific countries, pages, actions, IPs, hostnames, etc. See #1839
Maybe this UI can be reused also as a real time filter UI for the Visitor Log. The backend is the same code anyway: creating a segment then applied to the Live! APIs.
See also this post
This would be great to implement both features at once!
Some ideas for pre-created segments:
See cmswire.com/cms/customer-experience/interview-brian-clifton-on-cutting-through-data-noise-and-the-future-of-analytics-017510.php
See also support.google.com/analytics/bin/answer.py?hl=en&answer=1011783
As reported in #3507 Visitors Log under Visitors tab - it would be nice if we could filter
by:
IP address
Goal (show only visits that achieved a specific goal)
Referrer URL
Keyword
Campaign (Show only visitors from a specific Campaign)
visited page (URL)
Action String (search the "action" column for specific string, p.e. "*product-name*")
This is the link to the forum request:
http://forum.piwik.org/read.php?3,88704
It would also be nice if the visitor log could be filtered by 'Provider.' At current, I have to grep through my logs for the provider name, and then compare it to the Apache logs to see what pages the visitors viewed.
Cheers,
Nathan Zachary
We are officially calling for sponsors for funding for this feature! We would love to implement this feature in Piwik. If you can help sponsor even just a few hours of work, we hope to crowdfund and find many more. [Contact us now](mailto:sponsors@piwik.org) to get started and help make this feature possible!
See also #3095
Replying to matt:
We are officially calling for sponsors for funding for this feature! We would love to implement this feature in Piwik. If you can help sponsor even just a few hours of work, we hope to crowdfund and find many more. [Contact us now](mailto:sponsors@piwik.org) to get started and help make this feature possible!
I am very interested in this feature, and also like to participate implementation.
we reached the crowdfunding goal, awesome!! http://crowdfunding.piwik.org/custom-segments-editor/
Note, to fix at the same time: #3639
See also:
In 7933de115b3fc7e5dc9bc58b7e979cdefb89d16d: Refs #2135
TODOs @mattab
In b5067e0f1c106f6d6cae2415eaf67052c96d5ace: Refs #2135
Reverting some reformat code that went wrong (as Jquery 1.9 expects HTML strings to start with < rather than a space followed by <
In 0f3d97694d69df6f06ca1e5194e14e58d6da9b28: Refs #2135 Few JS fixes for a cleaner UI/UX
In 304a03e2a5d542a62c66a54b53d35614a9623f2f: Refs #2135 forgot to to check these in
In 85a30e37744a27941d2d96e51ce9e9d2da5dfd0b: Refs #2135
Kuddos Michal & Piotr for your help!
In 3212ef63391c874937fb3eb641e925ade4bc37a9: Refs #2135
OMG this is starting to be awesome!
In b4c56616539be02b3c29ca0727baee287e04e424: Showing suggested value on click on the INPUT field Refs #2135
Here is a little feedback on a short testing period of this fantastic feature:
Features
In 028342ad359aa86515c7d404c76b780ab3addcc4: Refs #2135
In 263892f231da5f6e998342aef02f33aa7edf8622: Refs #2135
NAILED the encoding! wow that was tough for my brain, but finally got around it.
Some findings:
_GET is automatically URL decoded
QUERY_STRING contains raw URL so we'll use this one instead
I REALLY want to simplify the whole "_GET" variables within Piwik so that all code uses a static method to get input variables. Refs #3931
In d89a08b8b27ef9a7293e9f8cf351bedbd838e2cb: Fixes #3932
Refs #2135
Replying to peterb:
Here is a little feedback on a short testing period of this fantastic feature:
- Segments not created by the superuser trigger a login screen in the dashboard widgets, saying that you need at least superuser rights to access this resource (This is listed in your TODO, so I think you're aware of this one)
- as superuser, when you are viewing a segment and change to another segment, the first selected segment stays applied (even when you switch back to "all visits (default)"). This is not the case when you view a segment in admin or user permission mode.
- when you edit an existing segment, blanks and other special chanracters are urlencoded (e.g. "%20")
- The "Delete" a segment function does not seem to work. There seems to be an error while triggering the "are you sure" modal dialog
Hey Peter, thanks for testing! Could you check again, these should now be fixed!
In 10deaac891671722771ab050e147094e7eacee85: Refs #2135
Fixing couple small bugs
In 25272167844ed0cd2c24121d0600edf1e2f53ebe: Refs #2135 i18n + improvements (custom loading message when segment applied)
In 36fc4ca1db9840fe25bd0f6ac6f8e51ac5bd9a06: Refs #2135
In 028acc4e42af442c3600d4ebabed70f1ec8c9dcb: Refs #2135 Enabling plugin by default for all updates
Hi Matt, great work and very much fun to use so far! - Feedback:
This is all I found at testing so far!
Another Question: How to enable auto_archiving for a specific segment? There is a column for that in the segments table.
Will not add segment editor to email reports in v1 but we will do soon, I am sure (hopefully can get sponsoring for it).
Thanks for the bugs, will fix them asap. Also will add the selector to set a segment as "Auto archive" (this is last item of my todo list!).
please keep feedback/bug report coming
In 7c58869c60a2b6b3cdf68dca4d0a4046449942aa: refs #2135 always show autocomplete when clicking on the input element
In 229a3f213f1102c197549e282d6324416d9412cf: Refs #2135
* Fixing select boxes logic/API
* better design for anonymous user. He can apply the segments that are shared
* better message in case anonymous tries delete/edit a custom segment
* Adding ability to set a segment as "PRE-PROCESS" or "PROCESSED ON DEMAND (Real time, default)"
In 1f87f85c1a20557f34b08cdde6ea9bc137a43822: Refs #2135
* Fixes "The input field for the segment's name disappers on focus loss"
In 047412dee8725f6f69b2c8f6bfe04d905f180673: Refs #2135
* Not forwarding segment parameter to the top menu links
Note: ideally we should display the Segment Editor on the WIDGET and API pages refs <a href='/3934'>#3934</a>
In 13ba840fcb226a8d2f6217c28d7f71e54b6ab360: Fixing non working footer link refs #2135
I think the code is now complete. Please post here any suggestion or bugs you find. I will also add user documentation separately. Thanks for testing & all the best enjoying this feature and finding new insights!
In 21877807842483cc4a3c1b3d472ddc549bb4dee7: Refs #2135 fixing CSS/image which wasnt big enough for German button label
Replying to nathanzachary:
It would also be nice if the visitor log could be filtered by 'Provider.' At current, I have to grep through my logs for the provider name, and then compare it to the Apache logs to see what pages the visitors viewed.
Cheers,
Nathan Zachary
Btw this is now possible since Benaka fixed Provider support in: https://github.com/piwik/piwik/commit/9824c498d7c180a17a562872b171f31c61da13f5
Grab yourself the 1.12-b22 and enjoy!