Area: Episerver CMS
Applies to versions: Not applicable

Installing and configuring the Content Recommendations package

Recommendations [hide]

Note: The package is currently only available as a prerelease. Enable the prerelease option when searching for or installing the package.

This topic describes the NuGet packages and initial configuration for the setup of the Content Recommendations integration for Episerver CMS.

What is included in the integration NuGet package

  • A UI module that integrates the Content Recommendations dashboards and configuration in the Episerver Platform navigation.
  • Automatically adds visitor behavior tracking to pages, to build user behavior profiles that can give relevant content recommendations.
  • A Content Recommendations block that editors can add to pages where they want content recommendations to appear.


  • A subscription to the Content Recommendations service and the appropriate configuration information for the environment (see Configuration section below), and user login credentials for the Content Recommendations UI.
  • An episerver CMS website implementation that uses RenderRequiredClientResources in the HTML head element. (This is where the tracking script will be injected.)
  • The website implementation has been set up for Collecting metadata.
  • The website is open to the public internet so the Content Recommendations service can reach it and index the site content.

Important: Before installing Content Recommendations, make sure you have widget deliveries set up. Otherwise, you will not see any widget deliveries in the drop-down widget selector.


Install the EPiServer.Personalization.Content.UI package in your Episerver solution. If you have already set up your NuGet feed, skip to Step 6.

  1. In Visual Studio, select Tools > NuGet Package Manager > Package Manager Settings.
  2. Select Package Manager > Package Sources.
  3. Click Add (+) to add a new package source.
  4. Add Episerver as Name, and the package Source https://nuget.episerver.com/feed/packages.svc/.
  5. Click OK.

    Note: NuGet package manager has to be version 2.8.50126.477 or higher to install Episerver packages.

  6. Open the solution file in Visual Studio and make sure the solution file is saved (required to make the NuGet tools available).
  7. In the Solution Explorer, right-click on References for the project, and select Manage NuGet Packages.

  8. Select Updates for the Episerver package source, to locate available updates for your solution, and click Update for the desired packages.

  9. When the installation/update is completed, rebuild the solution.
  10. See product-specific updating steps for steps required to finalize the update. 

Add the required configuration keys (see the Configuration section).


The following web.config appSetting keys are used to set up the integration:

Key Description
episerver:personalization.content.Environment The environment for the account. For production environments this is idio.co but could be staging.idio.co for staging/preproduction environments, and so on.
episerver:personalization.content.ClientId   The identifier for the client environment in the service, such as mywebsite.
episerver:personalization.content.ApiToken   The token used to authenticate to the API endpoint that provides available recommendation widgets to the property on the Content Recommendations block.
episerver:personalization.content.DisableDefaultTracking   Optional. If set to true, the default tracking script is not rendered in the HTML head section. Use this if you want to customize the tracking script or already have the tracking script included and do not want to remove it.

Adding recommendations to a page


At least one widget delivery needs to be set up in the Engage/Deliveries view of the Content Recommendations UI, see Setting up deliveries.

Adding a recommendation block

  1. In CMS edit view, create and place a new instance of the Content Recommendations block on a page.
  2. Use the All Properties view for the block to set:
    • The number of recommendations to show.
    • Which widget delivery to pull recommendations from.
    • An HTML fragment using templates for content properties to render the recommendation. 

      Note: Omit the script element surrounding the template because it is automatically included by the integration.


  3. Publish the block and the page.
Do you find this information helpful? Please log in to provide feedback.

Last updated: Jan 31, 2020

Recommendations [hide]