UX Calculation

We start by looking into configuring the customer experience calculation process. You will learn what calculation actions are available out of the box, the actions called by default when a user logs in, and the details of each action’s operation

We’ve seen that the login process invokes UX calculation actions. But what about after that? The responsibility of determining when to recalculate personalization with minimal impact on system performance falls to voters. Let’s see the voters available in SAP Commerce.

An important feature of the SAP Commerce personalization module is the ability to vary the content shown on a page depending on the segments a user belongs to. Determining which variations are relevant for a given user requires triggers. Let’s see how these work.

Last but not least, we need to deal with the personalization calculation results in the database as well. What does it mean?

• Personalization-related data stored in database
  • Lots of old personalization calculation results stored in database for each user (especially for anonymous user)
  • Each asynchronous personalization calculation creates a new business process that is stored in the database
• Problem

  Database table could easily grow to an unmanageable size and reduce performance

• Solution
  • Clean old personalization calculation results (particularly for anonymous users)

    Use a ‘session close’ listener or the CxResultsCleaningCronJob

  • Clean old business processes from asynchronous personalization calculations

    Use the CxPersonalizationProcessCleanupCronJob