Understanding data limits in decisioning and conditions
Sitecore Personalize provides your organization with data that you can use in decisioning and conditions. This data is made available by an internal service known as the Guest Context Service.
For example, you can include guest data when you write programmables and configure decision tables. As you type your JavaScript when writing a programmable decision, predictive helpers display the real-time data you can leverage from this service.
The available attributes form this service are also available for selection when configuring input and output columns in a decision table, as shown in the following image.
There are many scenarios where you might want to use real-time data when writing JavaScript for a custom condition, including session duration, search events, or order information.
To ensure the most efficient performance, Sitecore Personalize imposes data limits on the amount of data available in decisioning and conditions. Specifically, if a decision model's result string exceeds 10,000 characters, it is replaced with an empty string. Although original values are saved, the Guest Context Service will receive truncated values.
The following table provides default guest data limits for Sitecore Personalize. Data retention limits are per tenant.
|
Data |
Data and time duration limits |
|---|---|
|
guests with |
There is no data limit or time duration for guests with customer as the guest type. These are site visitors that have passed your organization's identity rules. |
|
guests with |
Guests with visitor as the guest type are retained for six months from the last date they were active. A visitor is a guest who has not provided enough identity information to meet the organization's identity rules. There is no data limit for these guests. |
|
orders |
Last 20 orders. There is no time duration that applies to order data. |
|
sessions |
Last 40 sessions within the last 90 days. You can not use session data from the 41st most recent session. Similarly, you cannot use session data that is 91 days or older. |
|
events |
Last 100 events from a session. Events are stored in sessions. Only events from the last 40 sessions within the last 90 days are available for decisioning or in conditions. You cannot use an event from the 41st most recent session. Similarly, you cannot use an event from a session that is 91 days or older. |