smithsson68@gmail.com
Aug 18, 2011
  6338
(3 votes)

Visitor Group Usage Report

I have created a simple report to show which CMS pages EPiServer Visitor Groups are used on:

image

Clicking the Visitor Group name will take you to VG Admin for the Visitor Group. Clicking the page name will take you to CMS Edit Mode for that page.

The source code is available in the EPiServer.Samples.VisitorGroupUsageReport package on EPiServer Nuget.

Feel free to use as is, amend, rip apart etc. Feedback, as always, is welcome.

Happy reporting!

Aug 18, 2011

Comments

Aug 18, 2011 10:02 PM

Nice one Paul!

If I could add a feature it would be that the pages column only listed the first 5 pages, and then you had to click to see the rest.

Now the question is who is going to add it...

smithsson68@gmail.com
smithsson68@gmail.com Aug 18, 2011 10:13 PM

Sound like some slippery HTML / CSS trick which I suck at!!

Aug 18, 2011 10:57 PM

Well now's as good time as any to learn ;)

Aug 19, 2011 12:44 AM

Awesome stuff Paul.

This is something I've been thinking about recently.

One of the issues personalised content brings is how editors understand and manage that content. I'd always thought that having an icon in the page tree to mark if a page has personalised content would be a useful additional feature.

smithsson68@gmail.com
smithsson68@gmail.com Aug 19, 2011 12:49 AM

Hi Mark,

The Icon thing was done by Per Nergård although I haven't tried it:

http://world.episerver.com/Code/Per-Nergard/Icon-in-PageTree-for-pages-with-visitor-group-content/

/Paul.

Aug 19, 2011 01:31 PM

I like it!

Jeff Wallace
Jeff Wallace Aug 20, 2011 01:08 AM

Nice.

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |