Chris Sharp
Aug 8, 2019
  4101
(4 votes)

Episerver Insight UI Updated for Visitor Group Tracking

If you’ve looked recently at the Episerver Insight UI, you’ll likely notice a new top-level filter for “Visitor Group”. While the Insight UI is updated automatically, the tracking of the visitor group is not automatic, and it is important to know that visitor group tracking is a developer task. To take advantage of this new filter, you will need to update your solution’s tracking events to send the user’s visitor group information, as the standard page view tracking does not add this type of tracking data by default. 

This new visitor group filter helps to address some highly requested use cases for Insight. As of right now, you can't create Insight segments based on events that are tracked on the user (note: it is on the roadmap). Segments are created based on information in the user's profile. More information on creating segments can be found here: https://world.episerver.com/documentation/developer-guides/profile-store/profile-store-api/segments/

For example, say I want to create a group of users who have visited the "Contact Us" in a specific geographic region. In Insight, this currently can't be done. BUT! It can be done using visitor groups. Furthermore, it's very possible that many of the actions/scenarios that users want can be satisfied using visitor groups. Now that we can now track visitor groups in Insight, if you wanted to see a report for those users who have done that action, just create a visitor group with the criteria, track the visitor groups, and create a segment of users in that visitor group.

The usage of this filter requires additional tracking into the Profile Store with the visitor group information. Visitor group tracking has been supported since the release of EPiServer.Profiles.Client 1.9.0 in update 271. Specifically, the visitor group tracking method is part of EPiServer.Tracking.Cms version 1.9.0. The documentation for visitor group tracking can be found here: https://world.episerver.com/documentation/developer-guides/tracking/visitor-group-tracking2/.

Aug 08, 2019

Comments

Please login to comment.
Latest blogs
Telemetry correlation for Scheduled Jobs in Optimizely

I previously demonstrated how to correlate telemetry to Azure Application Insights within a Hangfire job. But how about those jobs that are built a...

Stefan Holm Olsen | Mar 23, 2023 | Syndicated blog

Fixing Optimizely Content Syncing/Caching Issues on the DXP pre CMS.Core 12.13.0

Hi all, With our recent deployments to the DXP for .NET 6 projects (one a new build and one an upgrade) our clients had raised issues where there...

Scott Reed | Mar 23, 2023

Handle hostnames, schedule jobs and role access when synchronizing content

The Environment Synchronizer module helps you to set your environment into a known state after synchronizing databases between environments. In thi...

Ove Lartelius | Mar 23, 2023 | Syndicated blog

4 tips and tricks for Hangfire on Optimizely CMS

Here are four useful tricks I always apply to any site where I use Hangfire (code included).

Stefan Holm Olsen | Mar 21, 2023 | Syndicated blog