The personalization conditions
Describes personalization conditions and indicates whether they are compatible with Sitecore Experience Platform and Sitecore Experience Management.
This topic describes the personalization conditions that you can use in the Sitecore Experience Platform (xPlatform) and indicates which conditions are available in Sitecore Experience Manager (XM or CMS-only mode).
While you can use many conditions from the Rule Set Editor to personalize content when using XM, there are some conditions that are only available when you run xDB and the full XP.
If you install Commerce Connect, additional personalization conditions for Commerce Connect are installed.
In the Rule Set Editor, the personalization conditions are organized by category. The categories are:
You can use all of the rules in the following tables in the XP. The conditions that you can use in XM are marked as compatible (Yes) or not supported (No).
Condition | XM | XP |
|---|---|---|
When current interaction's campaign's custom facet field is classified under the specified custom group | Yes - only supports in-session personalization | Yes |
Condition | XM | XP |
|---|---|---|
When the current interaction is on the specified channel | Yes | Yes |
When the current interaction is on a channel in the specified channel group | Yes | Yes |
When the current interaction is on a channel in the specified channel type | Yes | Yes |
Condition | XM | XP |
|---|---|---|
When the date has passed | Yes | Yes |
When the current day of the month compares to number | Yes | Yes |
When the current day is day of the week | Yes | Yes |
When the current month is month | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the device browser compares to specific value | Yes | Yes |
Where browser supports HTML 5 audio | Yes | Yes |
Where browser supports HTML 5 video | Yes | Yes |
Where browser supports JavaScript | Yes | Yes |
Where the device is bot | Yes | Yes |
Where the device hardware model compares to specific value | Yes | Yes |
Where the device property compares to specific value | Yes | Yes |
Where the device operating system compares to specific value | Yes | Yes |
Where the device operating system vendor compares to specific value | Yes | Yes |
Where the device supports touch screen | Yes | Yes |
Where device type is value | Yes | Yes |
Where the device vendor compares to specific value | Yes | Yes |
Where the device supports touch screen | Yes | Yes |
Where device type is value | Yes | Yes |
Where the device vendor compares to specific value | Yes | Yes |
Where the hardware screen height compares to number | Yes | Yes |
Where the hardware screen width compares to number | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the specific field compares to specific value | Yes | Yes |
Where the specific field is empty | Yes | Yes |
Where the item contains a field type that compares to specific | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the area code compares to specific value | Yes | Yes |
Where the business name compares to specific value | Yes | Yes |
Where the city compares to specific city | Yes | Yes |
Where the country compares to specific country | Yes | Yes |
Where the DNS address compares to specific value | Yes | Yes |
Where the IP address compares to specific value | Yes | Yes |
Where the ISP name compares to specific value | Yes | Yes |
Where the latitude compares to specific value | Yes | Yes |
Where the longitude compares to specific value | Yes | Yes |
Where the metro code compares to specific value | Yes | Yes |
Where the postal code compares to specific value | Yes | Yes |
Where the region compares to specific value | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the item is the specific item or one of its ancestors | Yes | Yes |
Where the item is the specific item or one of its descendants | Yes | Yes |
Where the level of the item compares to number | Yes | Yes |
Where the item path compares to path | Yes | Yes |
Where the parent name compares to value | Yes | Yes |
Where the parent template is specific template | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the item ID compares to value | Yes | Yes |
Where the item name compares to value | Yes | Yes |
Where the item template is specific template | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the item language compares to value | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the current contact has registered the outcome during any interaction | Yes - reflects outcomes achieved within the session, rather than information from the xDB. | Yes |
Where the current contact has registered the outcome during any interaction where monetary value compares to value | Yes - works on in-session outcome triggering, not historical behavior from the xDB. | Yes |
Condition | XM | XP |
|---|---|---|
Where the current user is anonymous | Yes | Yes |
Where the current user domain name compares to value | Yes | Yes |
Where the user profile includes a valid email address | Yes | Yes |
Where the current user name compares to value | Yes | Yes |
Where the specific field in the user profile compares to value | Yes | Yes |
Where the specific field in the user profile is not empty | Yes | Yes |
Where the value in the specific numeric field in the user profile compares to number | Yes | Yes |
Where the current user is a member of the specific role | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the result of the expression query exists | Yes | Yes |
Condition | XM | XP |
|---|---|---|
Where the gender of the current contact is value | No | Yes |
Where the current contact is interested in value on any connected social network | No | Yes |
Where the current contact is connected to the specific social network | No | Yes |
Where the current contact's Klout Score compares to number | No | Yes |
Where the network profile specific field compares to value | No | Yes |
Condition | XM | XP |
|---|---|---|
Where calling the specific script returns true | Yes | Yes |
Where a condition in the specific rule is true | Yes | Yes |
Where the Content Search feature is enabled | Yes | Yes |
Where the current domain name compares to value | Yes | Yes |
When the Item Buckets feature is enabled | Yes | Yes |
Where predefined condition is true | Yes | Yes |
Where true (actions always execute) | Yes | Yes |
Note
The Analytics is enabled condition has been made obsolete in Sitecore 8.1. It has been replaced by the Tracking is enabled condition in the Tracking category, and the xDB is enabled condition in the xDB category.
Condition | XM | XP |
|---|---|---|
Tracking is enabled | Yes | Yes |
Condition | XM | XP |
|---|---|---|
When the current interaction is at the specified venue | Yes | Yes |
When the current interaction is at a venue in the specified venue group | Yes | Yes |
When the current interaction is at a venue in the specified venue type | Yes | Yes |
Note
Conditions in the Visit group are based on data from both the current and past visits. For conditions that take into account only the historical behavior of the visitor, see the Visitor group.
Condition | XM | XP |
|---|---|---|
Where the specific campaign was triggered during the current visit | Yes | Yes |
Where the specific campaign was triggered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number | No | Yes |
Where the specific campaign was triggered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number and the custom data compares to value | No | Yes |
Where a past or current interaction is on the specific Channel and when the number of elapsed days compares to number and when the past number of interactions compares to number | No | Yes |
Where a past or current interaction is on the specific Channel and when the number of elapsed days compares to number and when the past number of interactions compares to number and the custom data compares to value | No | Yes |
Where the number of engagement value points compares to number | Yes | Yes |
Where the specific goal was triggered during the current visit | Yes | Yes |
Where the specific goal was triggered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number | No | Yes |
Where the specific goal was triggered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number and the custom data compares to value | No | Yes |
Where the current visit matches the specific pattern card in the specific profile | Yes | Yes |
where the specific outcome was registered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number | No | Yes |
Where the specific outcome was registered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number and the custom data compares to value | No | Yes |
Where the ID of the page event is specific value | Yes | Yes |
Where the name of the page event compares to specific value | Yes | Yes |
Where the specific page event was triggered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number | No | Yes |
Where the specific page event was triggered during a past or current interaction and when the number of elapsed days compares to number and when the past number of interactions compares to number and the custom data compares to value | No | Yes |
Where the page index compares to number | Yes | Yes |
Where the specific page has been visited during the current visit | Yes | Yes |
Where the value of the specific profile key in the interaction profile compares to specific value | Yes | Yes |
Where the search keywords compares to specific value | Yes | Yes |
Where the site name compares to value | Yes | Yes |
Where the traffic type compares to number | Yes | Yes |
Where a past or current interaction is on the specific venue and when the number of elapsed days compares to number and when the past number of interactions compares to number | No | Yes |
Where a past or current interaction is on the specific venue and when the number of elapsed days compares to number and when the past number of interactions compares to number and the custom data compares to value | No | Yes |
Where the duration of the visit compares to seconds | Yes | Yes |
Where the asset was downloaded | Yes | Yes |
Where the number of downloaded assets compares to number | Yes | Yes |
Where the language was language | Yes | Yes |
Where the visit started at the entry page | Yes | Yes |
Where the visit ended at the exit page | Yes | Yes |
Where start date compares to date | Yes | Yes |
Where the referrer compares to specific value | Yes | Yes |
Where the internal search keywords compares to specific value | Yes | Yes |
Note
Conditions in the Visitor group are based on historical data accumulated in the contact's profile, which can include data from multiple visits. The default maximum time span covered by the contact profile is 30 days. For conditions that look at the visitor's behavior in the current visit also, see the Visit group.
Condition | XM | XP |
|---|---|---|
Where the number of the contact's current engagement value points compares to number | No | Yes |
Where the visit no. compares to number | No | Yes |
Where the specific tag of the visitor is not empty | No | Yes |
Where the ISP name compares to specific value | No | Yes |
Where the current contact matches the specific pattern card in the specific profile | No | Yes |
Where the value of the specific profile key in the contact behavior profile compares to specific value | No | Yes |
Where the value in the specific numeric field in the user profile compares to number | No | Yes |
Where the visitor identification compares to specific value | No | Yes |
Where the specific tag of the visitor compares to value | No | Yes |
Condition | XM | XP |
|---|---|---|
xDB is enabled | Yes | Yes |