Using CMS-only mode to run Sitecore without the xDB

Platform Administration and Architecture
Role scaling and configuration
Running Sitecore without the xDB
Using CMS-only mode to run Sitecore without the xDB
The personalization conditions

The personalization conditions

Version:

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 or XP installation, the personalization conditions that you can use are different depending on how you installed Sitecore:

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, a smaller set of personalization conditions are available as part of in-session personalization.

In the Rule Set Editor, the personalization conditions are organized by category.

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).

Predefined Rules

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where predefined rule is true	Yes	Yes	Yes

Campaign

Condition	XM Installed with the Sitecore XM topology packages	XP 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

Channel

Condition	XM Installed with the Sitecore XM topology packages	XP 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

Date

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
When the date has passed	Yes	Yes	Yes
When the current day of the month compares to number	Yes	Yes	Yes
When the current day is day of the week	Yes	Yes	Yes
When the current month is month	Yes	Yes	Yes

Device

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the device browser compares to specific value	Yes	Yes	Yes
Where browser supports HTML 5 audio	Yes	Yes	Yes
Where browser supports HTML 5 video	Yes	Yes	Yes
Where browser supports JavaScript	Yes	Yes	Yes
Where the device is bot	Yes	Yes	Yes
Where the device hardware model compares to specific value	Yes	Yes	Yes
Where the device property compares to specific value	Yes	Yes	Yes
Where the device operating system compares to specific value	Yes	Yes	Yes
Where the device operating system vendor compares to specific value	Yes	Yes	Yes
Where the device supports touch screen	Yes	Yes	Yes
Where device type is one of the list	Yes	Yes	Yes
Where the device vendor compares to specific value	Yes	Yes	Yes
Where the hardware screen height compares to number	Yes	Yes	Yes
Where the hardware screen width compares to number	Yes	Yes	Yes

Fields

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the specific field compares to specific value	Yes	Yes	Yes
Where the specific field is empty	Yes	Yes	Yes
Where the item contains a field type that compares to specific	Yes	Yes	Yes

IP Geolocation

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the area code compares to specific value	Yes	Yes	Yes
Where the business name compares to specific value	Yes	Yes	Yes
Where the city compares to specific city	Yes	Yes	Yes
Where the country compares to specific countries	Yes	Yes	Yes
Where the DNS address compares to specific value	Yes	Yes	Yes
Where the IP address compares to specific value	Yes	Yes	Yes
Where the ISP name compares to specific value	Yes	Yes	Yes
Where the latitude compares to specific value	Yes	Yes	Yes
Where the longitude compares to specific value	Yes	Yes	Yes
Where the metro code compares to specific value	Yes	Yes	Yes
Where the postal code compares to specific value	Yes	Yes	Yes
Where the region compares to specific value	Yes	Yes	Yes

Note

The GeoIP feature is disabled in XM by default and can be enabled in configuration.

Item hierarchy

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the item is the specific item or one of its ancestors	Yes	Yes	Yes
Where the item is the specific item or one of its descendants	Yes	Yes	Yes
Where the level of the item compares to number	Yes	Yes	Yes
Where the item path compares to path	Yes	Yes	Yes
Where the parent name compares to value	Yes	Yes	Yes
Where the parent template is specific template	Yes	Yes	Yes

Item information

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the item ID compares to value	Yes	Yes	Yes
Where the item name compares to value	Yes	Yes	Yes
Where the item template is specific template	Yes	Yes	Yes

Item version

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the item language compares to value	Yes	Yes	Yes

Marketing Automation

Condition	XM Installed with the Sitecore XM topology packages	XP 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

Security

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the current user is anonymous	Yes	Yes	Yes
Where the current user domain name compares to value	Yes	Yes	Yes
Where the user profile includes a valid email address	Yes	Yes	Yes
Where the current user name compares to value	Yes	Yes	Yes
Where the specific field in the user profile compares to value	Yes	Yes	Yes
Where the specific field in the user profile is not empty	Yes	Yes	Yes
Where the value in the specific numeric field in the user profile compares to number	Yes	Yes	Yes
Where the current user is a member of the specific role	Yes	Yes	Yes

Sitecore query

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where the result of the expression query exists	Yes	Yes	Yes

System

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Where calling the specific script returns true	Yes	Yes	Yes
Where a condition in the specific rule is true	Yes	Yes	Yes
When the Content Search feature is enabled	Yes	Yes	Yes
Where the current domain name compares to value	Yes	Yes	Yes
When the Item Buckets feature is enabled	Yes	Yes	Yes
Where true (actions always execute)	Yes	Yes	Yes

Tracking

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
Tracking is enabled	No	Yes	Yes

Venue

Condition	XM Installed with the Sitecore XM topology packages	XP 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

Visit

Note

Conditions in the Visit group are based on data from both the current and past visits. The default maximum time span covered by the contact profile is 30 days, For conditions that take into account only the historical behavior of the visitor, see the Visitor group.

Past visits removal using the XConnect API does not affect conditions as condition-related data is stored on the Contact facet.

Condition	XM Installed with the Sitecore XM topology packages	XP 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 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 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 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 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

Visitor

Note

Conditions in the Visitor group are based on historical data accumulated in the contact's profile, which can include data from multiple visits. For conditions that look at the visitor's behavior in the current visit also, see the Visit group.

Past visit removal using the XConnect API does not affect conditions as condition-related data is stored on the Contact facet.

Condition	XM Installed with the Sitecore XM topology packages	XP 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 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

xDB

Condition	XM Installed with the Sitecore XM topology packages	XP Sitecore XP configured to run in CMS-only mode	XP
xDB is enabled	No	Yes	Yes

If you have suggestions for improving this article, let us know!