This topic describes the NuGet packages and initial configuration for the setup of product recommendations and personalized search results with the Episerver Personalization suite. To get personalization running for a site, you need to configure access to the tracking API, so that you can post usage data and get recommendations back.
In this topic
To install and configure, you need the configuration keys and credentials provided by Episerver during onboarding of the service. Contact Episerver for questions regarding the onboarding process.
See Installing Episerver to set up Visual studio with Episerver extensions and the NuGet feed source. See below for NuGet packages needed when implementing product and email recommendations, and personalized search results.
See Content recommendations how to implement Episerver Content Recommendations.
In addition to onboarding the service, you need to install a set of NuGet packages for the tracking and personalization features. Available packages are listed below.
Installing a main native integration package also installs other packages based on dependencies. The package sets provide product-specific access to the tracking APIs, the required set depending on products:
These are general personalization system integration methods that you can use to connect with the tracking service. Instead of using the native integrations, you call the HTTP endpoints directly to integrate with the core personalization tracking API, and send and receive tracking data and recommendations in JSON format.
For Episerver Commerce sites, the core part of the personalization functionality consists of a catalog product feed providing the input data, combined with a tracking script that enables Episerver to track behavior and serve suitable recommendations. When you set up the personalization, you configure the feed and import the source data.
See Data import guides.
The Personalization API is used for personalization customization. This API contains header information, endpoints, and response messages for tracking and recommendations. The client calls the Personalization API that (primarily) returns product or content recommendations, to be used in various output channels.
See Personalization API.
See Visitor Intelligence and Personalization to learn how to set up tracking clients and the profile management user interface.
Below are instructions for some product/feature-specific configurations.
Enabling use of hashed IDs when using Episerver Campaign. Contact Episerver to provide the mapping of email addresses to pseudonymized IDs, and Episerver will configure this in the Personalization Portal.
Contact Episerver to configure these features:
Last updated: Jan 31, 2019