The personalization conditions

Abstract

The personalization conditions that are available in Sitecore XP and Sitecore XM.

This topic lists the personalization conditions that are available in Sitecore Experience Platform (XP) and in Sitecore Experience Manager (XM).

In a fully configured Sitecore XP installation, you can use all the personalization conditions in the Rule Set Editor and you can implement historic and in-session personalization.

However, in a Sitecore XM installation, the personalization conditions that you can use are different depending on how you installed Sitecore XM:

  • If you used the Sitecore XP topology packages (XP Scaled or XP Single) to install Sitecore XP and then configured it to run in CMS-only mode, some of the personalization conditions are available and you can implement in-session personalization.

  • If you used the Sitecore XM Scaled topology packages to install Sitecore XM, no personalization conditions are available and you cannot implement any personalization.

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 XP. The conditions that you can use in XM are marked as compatible (Yes) or not supported (No).

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where predefined rule is true

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

When current interaction's campaign's custom facet field is classified under the specified custom group

No

Yes - only supports in-session personalization

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

When the current interaction is on the specified channel

No

Yes

Yes

When the current interaction is on a channel in the specified channel group

No

Yes

Yes

When the current interaction is on a channel in the specified channel type

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

When the date has passed

No

Yes

Yes

When the current day of the month compares to number

No

Yes

Yes

When the current day is day of the week

No

Yes

Yes

When the current month is month

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the device browser compares to specific value

No

Yes

Yes

Where browser supports HTML 5 audio

No

Yes

Yes

Where browser supports HTML 5 video

No

Yes

Yes

Where browser supports JavaScript

No

Yes

Yes

Where the device is bot

No

Yes

Yes

Where the device hardware model compares to specific value

No

Yes

Yes

Where the device property compares to specific value

No

Yes

Yes

Where the device operating system compares to specific value

No

Yes

Yes

Where the device operating system vendor compares to specific value

No

Yes

Yes

Where the device supports touch screen

No

Yes

Yes

Where device type is one of the list

No

Yes

Yes

Where the device vendor compares to specific value

No

Yes

Yes

Where the hardware screen height compares to number

No

Yes

Yes

Where the hardware screen width compares to number

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the specific field compares to specific value

No

Yes

Yes

Where the specific field is empty

No

Yes

Yes

Where the item contains a field type that compares to specific

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the area code compares to specific value

No

Yes

Yes

Where the business name compares to specific value

No

Yes

Yes

Where the city compares to specific city

No

Yes

Yes

Where the country compares to specific countries

No

Yes

Yes

Where the DNS address compares to specific value

No

Yes

Yes

Where the IP address compares to specific value

No

Yes

Yes

Where the ISP name compares to specific value

No

Yes

Yes

Where the latitude compares to specific value

No

Yes

Yes

Where the longitude compares to specific value

No

Yes

Yes

Where the metro code compares to specific value

No

Yes

Yes

Where the postal code compares to specific value

No

Yes

Yes

Where the region compares to specific value

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the item is the specific item or one of its ancestors

No

Yes

Yes

Where the item is the specific item or one of its descendants

No

Yes

Yes

Where the level of the item compares to number

No

Yes

Yes

Where the item path compares to path

No

Yes

Yes

Where the parent name compares to value

No

Yes

Yes

Where the parent template is specific template

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the item ID compares to value

No

Yes

Yes

Where the item name compares to value

No

Yes

Yes

Where the item template is specific template

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the item language compares to value

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the contact has previously been in the specific Automation campaign and exited between start date and end date

No

No

Yes

Where the contact is currently in the specific Automation campaign

No

No

Yes

Where the contact is currently enrolled and waiting in the specific activity of the specific Automation campaign

No

No

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the current user is anonymous

No

Yes

Yes

Where the current user domain name compares to value

No

Yes

Yes

Where the user profile includes a valid email address

No

Yes

Yes

Where the current user name compares to value

No

Yes

Yes

Where the specific field in the user profile compares to value

No

Yes

Yes

Where the specific field in the user profile is not empty

No

Yes

Yes

Where the value in the specific numeric field in the user profile compares to number

No

Yes

Yes

Where the current user is a member of the specific role

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the result of the expression query exists

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where calling the specific script returns true

No

Yes

Yes

Where a condition in the specific rule is true

No

Yes

Yes

When the Content Search feature is enabled

No

Yes

Yes

Where the current domain name compares to value

No

Yes

Yes

When the Item Buckets feature is enabled

No

Yes

Yes

Where true (actions always execute)

No

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

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Tracking is enabled

No

Yes

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

When the current interaction is at the specified venue

No

Yes

Yes

When the current interaction is at a venue in the specified venue group

No

Yes

Yes

When the current interaction is at a venue in the specified venue type

No

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

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where at least one of the campaigns in list was triggered during the current visit

No

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

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

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

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

No

Yes

Where the number of engagement value points compares to number

No

Yes

Yes

Where the specific goal was triggered during the current visit

No

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

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

No

Yes

Where the current visit matches the specific pattern card in the specific profile

No

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

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

No

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

No

Yes

Where the page index compares to number

No

Yes

Yes

Where the specific page has been visited during the current visit

No

Yes

Yes

Where the value of the specific profile key in the interaction profile compares to specific value

No

Yes

Yes

Where the search keywords compares to specific value

No

Yes

Yes

Where the site name compares to value

No

Yes

Yes

Where the traffic type compares to number

No

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

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

No

Yes

Where the Visit started at one of pages in list

No

Yes

Yes

Where the start date compares to date

No

Yes

Yes

Where the referrer compares to specific value

No

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

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

Where the number of the contact's current engagement value points compares to number

No

No

Yes

When the current contact is in the specified contact list

No

No

Yes

Where the visit no. compares to number

No

No

Yes

Where the specific tag of the visitor is not empty

No

No

Yes

Where the ISP name compares to specific value

No

No

Yes

Where the current contact matches at least one of the profile pattern card in list

No

No

Yes

Where the value of the specific profile key in the contact behavior profile compares to specific value

No

No

Yes

Where the value in the specific numeric field in the user profile compares to number

No

No

Yes

Where the visitor identification compares to specific value

No

No

Yes

Where the specific tag of the visitor compares to value

No

No

Yes

Condition

XM

Installed with the Sitecore XM topology packages

XM

Sitecore XP configured to run in CMS-only mode

XP

xDB is enabled

No

Yes

Yes