Personalized Recommendation FAQ
This page summarizes frequently asked questions around the topic of Personalized Recommendation. Its purpose is to be updated regularly based on the interaction between customers, partners & SAP employees and our team within the communication channels and enablement activities.
General Questions
Personalized Recommendation is a generic recommender service, part of the SAP AI Business Services portfolio on SAP Business Technology Platform (SAP BTP) that uses machine learning techniques to give your users highly personalized recommendations based on their browsing history and/or item description.
Personalized Recommendation can help:
- Enhance user engagement and engagement
- Drive user conversion and meet business goals
- Retain business control, curate relevancy, and meet KPIs
It enables customers to generate value from user interactions.
Personalized Recommendation is a generic reusable recommendation service:
- Domain-agnostic – Personalized Recommendation can be applied to a wide variety of use cases.
- Customizable – Features such as Attribute Boosting & Filtering, and Machine Learning Explainability provide our customers to tailor recommendations to their business strategies.
- Easy integration – Interactions with our service is done through standardized APIs, with model lifecycle management handled by us.
Personalized Recommendation was used to provide learning recommendations for the multinational telecommunications company Telefonica, allowing them to upskill and reskill employees.
The service can be consumed in two different ways:
- Natively embedded in SAP solutions such as SAP SuccessFactors and SAP Commerce Cloud
- As a standalone service via the SAP Business Technology Platform
For more information on sizing options, you may visit our page on the SAP Discovery Center. To learn more on how to estimate your consumption of our service, read our blog post.
The implementor will train their own models with their respective training data. This training data can vary in terms the fields used or number of fields.
Architecture Questions
As it is a cloud-based service, we don’t offer it on-premise.
Yes, the service scales up based on demand, minimizing impact on customers during higher usage periods.
Service and Compliance Questions
The Service Level Agreements can be found here.
The current certificates, Service Organizational Control reports, attestations, regulations and product and industry specific location can be found here.
As Personalized Recommendation does not store any of the user data, our service is GDPR compliant.
Data Questions
We do not collect any data used to train the model. The data collection is done by our customers or SAP teams we are collaborating with, such as SAP SuccessFactors.
There are three main sources of data that should be provided for training the model:
- Clickstream
- Item catalog
- User metadata
For optimal results, we recommend providing all three data sources.
The item catalog or clickstream data must be provided to get started with using our service. For better performance, we recommend providing both the clickstream and item catalog.
You can find more information about the data format here.
No, we do not store any of the training data for the model.
All training data will be encrypted before input to train the machine learning model and is deleted after training is completed.
Customers may choose to anonymize user identifiers in the training data and use the anonymized identifier when making inference requests.
The inference request payload is not encrypted.
Training Questions
Training times vary depending on the complexity of the data. In most cases, a rough estimate is 30 minutes. The maximum amount of time allowed for training is 7 hours.
Customer-specific training is required. Each customer trains their own model using their own datasets.
It is up to the implementer to decide how often the model should be retrained. While the model can handle cold-start situations, periodic retraining with new training data is recommended for optimal results.
There are four metrics you may use to evaluate the effectiveness of model, they are:
- Hit Rate
- Mean Reciprocal Rank
- Average Normalized Discounted Cumulative Gain
- Coverage
More information on what these metrics mean can be found here.
The model metrics depends on the quality of the data that was used to train the model. The customer can decide on their own Target Accuracy.
No. The model performance is evaluated whenever a training job is completed. When the training is completed, a data quality report and model performance is provided.
There are two scenarios to consider:
- Training overfit - We train and evaluate model performance on an unseen dataset, and save the best performing model. The training will be terminated when the performance decreases in X consecutive training epochs.
- Data leakage due to attributes in customer data - The customer or integrator should review the feature importance and revise the training data as necessary.
Inference and Serving Questions
Inferences served by the model come with a confidence score that shows how confident the model is in its inference. The ML Explainability feature offers insights and a breakdown of the contributing factors for each recommendation.
We recommend our customers and partners to create their own end-user engagement metrics to track or realize the value for this service.
No. Attribute boosting or filtering does not require retraining of the model.
Yes. If the user and item attributes are provided in the training dataset, the relation will be considered based on the clickstream which links items to the user via their interactions.
New users and catalog items are handled by our cold start feature, allowing new users and items to be added to the model without retraining the model. Regular retraining of the model with updated datasets is recommended for optimal performance.
Yes. You may use the “excluded_items” flag to exclude items from the item catalogue form being recommended.
Developer & Technical Questions
Find out more about it here.
Data is transferred by a RESTful API (HTTPS).
The communication with the server is secured via the OAuth 2.0 protocol.
SAP Business Technology Platform allows the creation of multiple tenants that can be integrated into different system landscapes.