Click here to see the most recent offline and historical orders documentation.
There are a number of different ways that Episerver Personalization can be integrated with Episerver and other platforms. The graphic below gives an overview of the benefits and limitations of each:
As you can see from the above table, the different integration options will suit different customers or partners. This might be because of their technical capabilities, the depth of the integration or offline personalization requirements.
Click here to see the most recent feed documentation.
Episerver Personalization integration for Commerce
If you are running Episerver Commerce v11.3 or later, there is a native integration supported which allows integration between an Episerver Commerce site and the Episerver Personalization service. This is done via a Nuget package which is installed from the Episerver Nuget feed: http://nuget.episerver.com/en/OtherPages/Package/?packageId=EPiServer.Personalization.Commerce
There are three main components of the integration:
- Export product fe...
Click here to see the most recent Server-to-Server API integration documentation.
The Personalization API is an API that the client calls which, primarily, returns product recommendations or content.
The client sends the API a request containing information about the user and the transaction. The Personalization API returns a list of recommended products. These recommendations can be shown on a call-center screen, a till/terminal in a store, an email receipt, a printed package insert, a digital mirror or any other one of countless use cases...
Click here to see the most re...