May 07, 2015
You know what would be awesome? If in Sitecore, you could clearly get clear data on how your dynamic personalized content was doing in optimizing the user experience. Which personalization variants are doing well? Which are not? You've gone through the work of creating more relevant content and defining conditions by which they will be triggered and increase the likelihood of your user reaching their intended goal - a conversion. But it sure would be nice to see how much of a difference it made. Well, looks like you can do just that!
While in the Experience Editor on a page that has your personalized components, click the Optimization tab and the Personalization command in the Page Reports chunk.
And voila (almost)! You'll get a report like what you see below that shows:
- Each component on the page that has personalization applied to it
- The name of each personalization condition
- The number of visitors who have encountered the personalized content
- The variation (+/-) in engagement value the visitors have produced in comparison to the default (not personalized) content
However, you'll notice my screenshot says "No Data". I'm working with Sitecore Support to find out how to enable this data collection.
A Little History
This functionality did exist prior to Sitecore 8. However, it came via a module called a SBOS Accelerator. And with that accelerator installed, each component's personalization window had a checkbox "Enable personalization tracking" which obviously did the trick. In Sitecore 8, that checkbox is gone so I'm off to find out where that handy little on/off switch has moved to. Stay tuned! I'll follow up. More Sitecore Experience Marketing strategies and tactics can be found on our blog under topics, Sitecore 8 and Digital Marketing.
May 21, 2015 - Upon further review and discussion with Sitecore Support, it is determined that "it is only possible to track personalization statistics for pages with running Page Test." But this capability I described has been submitted as an official feature request. In the meantime, I'm going to go back to the lab with our Sitecore architecture and development team and see if we can produce an interim solution.
comments powered by