Jan 8, 2019
(2 votes)

Episerver Advance content recommendations block

As you probably have heard we launched Episerver Advance earlier this year. Advance is the latest addition to our personalization suite and is a service for content personalization and enables you to recommend content to your visitors at any given time that vary based on their experience and needs.

How it works

The process can be described with the following steps:

  1. Track – every interaction with your site is tracked back to Episerver Advance.
  2. Create – your editors create content, preferably lots of it and diverse.
  3. Analyze – the machine learning algorithms analyze tracking behavior and content.
  4. Visualize – the service sends recommendations back to the user based on the analysis.

Getting started

As an example and help you get stared with Episerver Advance we have created a block available on Github, The block shows a number of recommended pages set by the editor to the visitor. No styling has been added to the block but what that’s not a priority here.

I have set the content recommendations block up on a clean Alloy site. The first thing that needs to be done is getting an Advance account. When ordering Advance, you will get configs for both tracking and getting recommendations that need to add to your web.config.

The next step is to install nuget-packages. The packages needed are EPiServer.Tracking.PageView and Episerver.Personalization.CMS. EPiServer.Tracking.PageView is for tracking and Episerver.Personalization.CMS is the one used for getting the recommendations. The packages need the configs for your Advance account and can now be set.


<add key="episerver:profiles.TrackingApiBaseUrl" value="ChangeThis" />
<add key="episerver:profiles.TrackingApiSubscriptionKey" value="ChangeThis" />
<add key="episerver:profiles.ProfileStoreTrackingEnabled" value="false" />


<add key="episerver:RecommendationServiceKey" value="ChangeThis" />
<add key="episerver:RecommendationServiceSecret" value="ChangeThis" />
<add key="episerver:RecommendationServiceUri" value="ChangeThis" />

The tracking needed for Advance is, as you might have figured from the name of the package, pageviews. Using the package, we add [PageViewTracking] to the page controller methods we want to track, as below. Add tracking to all as many of your pages as possible, the more the better.

public class DefaultPageController : PageControllerBase<SitePageData>
        public ViewResult Index(SitePageData currentPage)

Next, I just added the project to my alloy site. The content recommendation block is using an API-call to get the recommendations, so I needed to add the following to the route config:

System.Web.Http.GlobalConfiguration.Configure(config =>
	    config.Routes.MapHttpRoute(name: “DefaultApi”, routeTemplate: “api/{controller}/{action}”, defaults: new { id = RouteParameter.Optional });

That’s it! When creating the block on the site there is only one property available for the editor.

And then on the site the block containing the links.

Jan 08, 2019


Janne Kuusela Kuusela
Janne Kuusela Kuusela Nov 14, 2019 08:21 AM

It is great that I can install some ready-made package and get recommendations. However it would be really interesting to understand a bit more the added value of this, for example by getting answer to the following:

  • What is the logic behind the gives you the recommendations?
  • How if anyway can developer or content editor affect the recommendations?
  • Is this any how related to the personalization portal? If we have Advance and personalization portal provisioned for our customer, what should we expect to see on the personalization portal?

Episerver has ramped up a variety of personalization products and services, but most of the really good and well explained examples are related to commerce, where the logics behind recommendations are somewhat more clear and common (popular products, both together with currently browsed product etc.)

I am personally having really hard time to find any solid documentation, examples and explanations for Episerver personalization products for customer that just dont have commerce. Sure there is load of articles about setting up this and that, but still it is really difficult to create solid picture of what to expect from personalization of content, not products.

Please login to comment.
Latest blogs
Configured Commerce - Introduction to Long-Term Support (LTS) Releases

First off, for those who have not had a chance to meet me yet, my name is John McCarroll, and I am the Technical Product Manager for the Optimizely...

John McCarroll | Sep 29, 2023

Auto-translate with OpenAI in Optimizely CMS

You can now auto-translate content using your favorite online AI service, inside the old trustworthy Episerver.Labs.LanguageManager!

Tomas Hensrud Gulla | Sep 29, 2023 | Syndicated blog

Vulnerability in CMS 12 shell module configuration

Introduction A potential security vulnerability has been identified in Optimizely CMS 12, triggered by a certain shell module configuration. To be...

Magnus Rahl | Sep 28, 2023

AI-Assistant: The 'Change Tone' Shortcut

The AI-Assistant for Optimizely is constantly evolving, adjusting, and transforming to meet your digital needs, providing a cutting-edge advantage...

Luc Gosso (MVP) | Sep 27, 2023 | Syndicated blog