Here Comes the Active Personalized Experiences List in Sitecore 9.2

Sitecore Personalization is one of the most popular features with our clients, so seeing advancement with the tools available to them is always good news. The Active Personalized Experiences List is another welcome addition in Sitecore 9.2, which provides a new ability to see all Personalization on the entire site.

The Old Way of Viewing Personalization

In a clean Sitecore 9.2 installation, if we take a look at the Presentation Details for the Home item, we'll see there is a Rendering called Sample Rendering where Personalization is applied. I've added a Rule that will hide this Rendering if the User is from Canada. Not for you, Canucks!

Opening the Personalize option on this Rendering will show you the Rules Editor, where you can review what has been applied to this page. Up until now this was the way you observe what Personalization is in place.

Here comes Active Personalized Experiences List

This new dashboard gives you a global overview for the entire site, instead of aimlessly navigating around the IA! This is really useful for our team while supporting clients since we may have to jump in and have a look at why a view is different than expected. They also like this as it's just easier to monitor all Rules in effect.

Each row represents a page with Personalization, with basic information, such as:

  • The name of the page that contains personalized components.
  • The website that the page is on.
  • The number of personalized experiences this page contains.
  • The number of components personalized on the page.
  • Effect in Test, which is the highest effect rate if there is a personalization test running.


Highlighting a page will provide a preview on the right for the changes seen when a Rule is triggered, and using the Edit command launches the Experience Editor for the context item.


One Final Note

One thing that tripped me up, is this dashboard reflects what is published, so if you're editing a page's Personalization the changes will not be immediately visible here. This was my assumption but it's worth noting.