Out of the box conditions
Here are the out-of-the-box conditions that you can apply to an experiment or experience. When you apply a condition to an experiment or experience you must enter values in place of variables. Not all conditions are relevant for all types of experiments and experiences.
The Category column lists the type of experiments or experiences for which the condition is compatible.
The Edge compatibility column identifies the conditions that can be executed at the edge. This edge capability reduces latency and bandwidth usage by processing data closer to its source using local servers, rather than relying on centralized cloud servers. This enables you to deliver precise, location-based personalized content from the moment a user first interacts with your site.
The edge-compatible conditions require the use of the Sitecore Cloud SDK. To use this SDK, you must have a JSS Next.js app version 21.6.0 or later connected to XM Cloud.
Using both an edge-compatible and a non-edge compatible condition together will stop them from running at the edge.
Condition name |
Category |
Edge compatibility |
Example usage |
Input options - variables are in italics |
Comments |
---|---|---|---|---|---|
Time of day (organization time zone) |
TIME (web, interactive, or triggered) |
|
The experiment or experience runs before or after a specific time. |
The visit is / is not before / after time, based on your organization's time zone |
You can find your organization's time zone under Company information. |
Month of visit (organization time zone) |
DATE (web, interactive, or triggered) |
|
The experiment or experience runs in a specific month(s). |
The visit is / is not month(s), based on your organization's time zone |
You can select more than one month. You can find your organization's time zone under Company information. |
Day of the week (organization time zone) |
DATE (web, interactive, or triggered) |
|
The experiment or experience runs on specific days of the week (for example, weekend days). |
The visit is / is not on day of the week, based on your organization's time zone |
You can select more than one day of the week. You can find your organization's time zone under Company information. |
Date and time (organization time zone) |
DATE TIME (web, interactive, or triggered) |
|
The experiment or experience runs before or after a specific date and time. |
The visit is / is not before / after date and time, based on your organization's time zone |
You can find your organization's time zone under Company information. The date and time format adheres to ISO 8601. |
Visit day of the month (organization time zone) |
DATE (web, interactive, or triggered) |
|
The experiment or experience runs on the last 3 days of the month. |
The visit is / is not on a day of the month that is equal to / is greater than / is greater than or equal to / is less than / is less than or equal to / is in between number, based on your organization's time zone |
You can find your organization's time zone under Company information. The number can be any number between 1 and 31. If you are using in between to compare dates, you must enter two numbers to define the range. |
Device |
DEVICE (web or interactive) |
|
The experiment or experience runs only on a specific device type (for example, show a link to download your app only on a mobile device). |
The visitor is / is not using device type(s) device during the current visit |
Device types include: mobile, tablet, desktop, other You can select more than one device type. |
Operating system |
DEVICE (web or interactive) |
|
The experiment or experience runs only on a specific operating system (for example, show a link to your app on Google Play only on Android phones). |
The visitor is / is not using operating system during the current visit |
Operating systems include: macOS, Windows, Android, Linux, iOS, and other. You can select more than one operating system. If the operating system is null or undefined, the condition returns false (even if other is selected). |
Country |
GEO (web or interactive) |
|
The localized experiment or experience runs in a specific country, for example: Spain. |
The visitor is / is not in country during the current visit. |
Sitecore Personalize captures geolocation based on the user's IP address.The geolocation data is collected once per active session as the user interacts with your app. It's collected from the first event in the current session and is not updated again within the same session. You can select more than one country. |
Region |
GEO (web or interactive) |
|
The localized experiment or experience only runs in a specific region, for example: South America. |
The visitor is / is not in region during the current visit |
Sitecore Personalize captures geolocation based on the user's IP address.The geolocation data is collected once per active session as the user interacts with your app. It's collected from the first event in the current session and is not updated again within the same session. Regions include: Africa, Asia, Europe, North America, Oceania, South America and other. You can select more than one region. |
Country Region |
GEO (web or interactive) |
|
The localized experiment or experience only runs in a specific region in a country, for example: Florida. |
The visitor is in country where region is / is not region(s) during the current visit. |
Sitecore Personalize captures geolocation based on the user's IP address.The geolocation data is collected once per active session as the user interacts with your app. It's collected from the first event in the current session and is not updated again within the same session. Currently, a country region refers to any state within the US, such as Florida, California, or Colorado. You can select more than one state. |
Page view |
VISIT (web or interactive) |
|
The recommendations experiment or experience runs if the visitor is viewing the product search page. |
The visitor has / has not visited the page name(s) during the current visit |
Sitecore Personalize captures page views through the page attribute in the RequestResponse
page name is a free text field that can include alphabet characters, numbers, and special characters. You can specify multiple page names, separated by a comma. |
First page |
VISIT (web or interactive) |
|
The experiment or experience runs if the visitor started the current session on a specific page. |
The visit has / has not started on a page that is equal to / contains / starts with / ends with page name during the current visit |
Sitecore Personalize captures the first page the session started on, through the page attribute in the RequestResponse
page name is a free text field that can include alphabet characters, numbers, and special characters. You can only specify one page. |
Number of page views |
VISIT (web or interactive) |
|
The limited time dealexperiment or experience runs if the visitor visited the product page 3 times over the past week. |
The visitor has / has not visited the page name within the past number of days and the total number of page views is equal to / is greater than / is less than / is greater than or equal to / is less than or equal to / is between number |
Sitecore Personalize captures page views through the page attribute in the RequestResponse
page name is a free text field that can include alphabet characters, numbers, and special characters. Only one page can be specified. The maximum number of days is 30. The number of page views can be any whole number, including 0. If you are using in between to compare page views, you must enter two numbers to define the range. |
First referrer |
USER INTERACTION (interactive-only) |
|
The interactive experiment or experience runs if the first referrer is Facebook. |
The visitor comes from a URL that is equal to / includes any of / contains / starts with / ends with / is null referrer in the current visit |
Sitecore Personalize captures the first referrer through the uniform resource identifier (URI) from which the current session started. This is captured as the referrer is a free text field that can include alphabet characters, numbers, and special characters. |
UTM value |
USER INTERACTION (interactive-only) |
|
The interactive experiment or experience runs if the UTM medium is paid. |
The visit includes a UTM type that is equal to / includes any of / contains / starts with / ends with / is null UTM value |
Sitecore Personalize captures UTM values through the RequestResponse
type can be one of the following: campaign, source, medium, or content. UTM value is a free text field that can include alphabet characters, numbers, and special characters. |
New or returning visitor |
USER INTERACTION (web or interactive) |
|
The welcome back experiment or experience runs if the visitor is a returning user. |
The visitor is type to your site |
type can be new or returning. |
Point of sale |
POINT OF SALE (web or interactive) |
|
The experiment or experience runs for a specific point of sale. |
The visit is / is not to point of sale |
You can select any of the points of sale defined for your organization's tenant. To view the point(s) of sale for your organization's tenant, on the navigation menu, click |