@mattab opened this Issue on January 26th 2014 Member

Content Grouping is the ability to group pages into meaningful categories, and get analytics reports for these categories.

Currently it can be done with Piwik by using Custom Variables, where one can assign a page in one or several content categories or content tags. For more info about using Custom variables for content grouping see this blog post.

Groups could be assigned:

  • in the Javascript tracking code (similar to custom dimension action scope)
  • via an admin User interface letting user customize groups for each website (or across all websites). Groups are of two sorts:
    • Simple matches such as "page url contains X" or "page title contains Y" then group is Z
    • Regular expression matches on the URL or page Title, which can be used to extract the actual value to be used as Content group

There could also be heaps of small details that make groups valuables

  • could maybe replace custom dimensions of action scope?
  • Transitions for content groups
  • Users flow for content groups
  • New segments like "Entry page with Content group" and "Exit page with content group"
  • New reports like "Content Groups for entry pages", "Content groups for Exit pages"

More info about GA feature:


@anonymous-piwik-user commented on January 26th 2014

i like this idea of making an admin page to help define categories and sub categories base on url or page title, one additon i would add is allow people to regex the definition to allow more detailed categorization. Perhaps also allow people to define wordpress blog category abd sub category options.( since a large number of people use this as the cms). if we use that blog setup for definiton perhaps we also capture blog title as well as author.

@JMJHautier commented on July 9th 2015

Hi !
Just to say that I would very much appreciate such 'grouping' feature within the User interface (as explained in this post). In my enterprise, only the IT department would have the rights to 'have fun' with the code and set up potential "custom variables" => As a programme assistant, as long as the function is not in the UI, I am powerless. And I doubt I am the only one in this situation :)

Sure, regex & subcategory options would be very nice, but a 'manual' selection ('simple matches' as mattab said ? ) would also do the trick.

Thanks for your attention !

@mattab commented on May 14th 2018 Member

Such grouping feature would also be useful with the GDPR considerations #12600 . For example, it becomes quite important in some cases to "Anonymise" or "Pseudonymise" (#12836) the URLs, which may contain personal data. For example, in a WooCommerce store, URLs include the Order ID, which is personal data.

Using the Content Grouping feature, one could define basic rules to automatically track all pages under a directory eg. these pages/track/order/16645 and /track/order/111 would be grouped together under /track/order/order-id

-> This way, Page URLs would not anymore track personal data.

@tsteur commented on May 14th 2018 Member

I'm not quite sure I think content grouping would be a new report or would it replace rows within the Page URLs report?

I thought with content groups feature we would maybe still provide regular page URLs/page titles report.

But also additionally a similar report where some pages may be grouped into groups so you can see both the individual pages and the grouped pages. I think it is similar in GA where you can enable / disable content groups.

So we might actually need another feature which allows you the same behaviour as a content group kind of, but always rewrite the page URL or page title. Independent of whether content grouping is being viewed or not.

@matmerc commented on November 23rd 2018

has this been implemented at the end or is it still work in progress? thanks

@bmaehr commented on April 15th 2021

Is an important feature for us. Our use case: We have a start page and a login page.

Many of the graphs and statistics are not helpful, because most of the transitions, interactions and so on are between these two sites or it is not important to distinguished if the start is the starting page or the login page.

On the other hand it could be interesting how often the help page or leaving the page from login page or start page happens so in this case it would be interesting to treat them as separate pages.

Additionally we have DNS aliases from an older system to the website and there are additionally page visits with the old hostnames which again are treated as separate pages.

So a configurable grouping (perhaps even configurable for a diagram/stat) would be nice.

@TripleDotZero commented on August 20th 2021

I saw that this feature was removed from the 4.0.0 milestone. Also as of the time of writing this, this feature hasn't been added to any milestones. will this feature be worked on?

@tsteur commented on August 22nd 2021 Member

@TripleDotZero right now we're not planning to work on it but it might change in a few months. I can only suggest to keep monitoring the issue unfortunately.

Powered by GitHub Issue Mirror