Used to target a customer based on their affinity to particular categories or brands, based on their browsing behaviour. You can specify which tag you want to target, where that appears in the rankings for that customer, any tags you want to exclude and which time period you want to analyze.

Used to target a customer based on the device, browser, or operating system they're using to access the content. This rule also enables you to check for certain proxy services used by common ISPs.

Used to target customers that have made a purchase in the last year but have not made a purchase in the specified analytics period.

Used to target customers who have made their first purchase in the defined analytics period.

Used to target customers based on any related person field. This includes language, currency and many others. You can also use this rule type to target custom data fields imported into the platform.

Examples of common Person Field data

For core fields, the Person Field value rule requires three pieces of information: the person field to check, the type of comparison to use and the value to compare it with.

For custom (extend) fields, the Person Field value rule requires the above three pieces of information as well as the type that the value is expected to be.

Used to target customers who are in the top 10% of buyers on site within the defined analytics period.

Used to target customers that have visited the site in the last year but have not visited within the specified analytics period.

Used to target customers that we are able to link to an email address and/or a mobile number.

Used to target customers that belong to a particular segment that you specify.

Used to target customers on a particular experience.

Used to target customers based on whether their price prediction is low, medium or high.

Used to target customers based on what the average monetary value per session of either their browsed, carted, or purchased products were over a given time period.

Used to target customers that have been sent a triggered email or SMS over a specified time period. This can be refined by trigger stage and by trigger type.

Used to target customers who have browsed a particular product, a product with a specific tag value, or any product at all within the specified time period.

If matching on tag or tag value, this counts up all the products matching any of the tags or tag values specified in the rule. To match a value against individual tags, you must create a separate rule for each tag or tag value. The rule counts each visit to the product details page as one browse event so if product X with tag value of Y is browsed three times, this counts as three.

Used to target customers who have carted a particular product, a product with a specific tag value or any product at all within the specified time period.

If matching on tag or tag value in this rule, it counts up all the products matching any of the tags or tag values specified in the rule. To match a value against individual tags, you must create a separate rule for each tag or tag value. The rule doesn’t consider the quantity of each product that is carted, so if product X with tag value of Y is carted three times, this only counts as one.

Multiple visits to the cart result in the number of times a product matches increasing, as do multiple cart visits in different sessions, i.e. if someone carts one of product X and returns to their cart five times over the course of several sessions, this counts as being carted five times, even though they may have only added it once.

Used to target customers who have purchased a particular product, a product with a specific tag value or any product at all within the specified time period.

If matching on tag or tag value in this rule, it counts up all the products matching any of the tags or tag values specified in the rule. To match a value against individual tags, you must create a separate rule for each tag or tag value. The rule doesn’t consider the quantity of each product that is purchased, so if product X with tag value of Y is purchased three times within one transaction, this only counts as one. If it is purchased once in three separate transactions, it counts as three.

Used to target customers that have performed a custom defined action.

Used to target customers based on the number of sessions they have started within the pre-defined time period.

Used to target customers that have had their first visit within a set time period.

Used to target customers that have either been sent, opened or clicked-through from an email in the defined time period.

Used to target customers that have had a cart total or average value of a specified amount within a specified time period. This rule can also check whether the customer carted one or more products with a specified value.

Used to target customers that have had a total or average purchase value of a specified amount within a defined time period. This rule can also check whether the customer purchased one or more products with a specified value.

Used to target customers that match the specified currency on the triggered email. Can only be used on triggered email campaigns; cart abandon, browse abandon, purchase complete.

Used to target customers that match the specified language on the triggered email. Can only be used on triggered email campaigns; cart abandon, browse abandon, purchase complete.

Used to target customers that match the merged field value on the Slot merge code. The field needs to be added to the Slot’s properties and a value merged into the link and image URLs. This value can then be checked against the desired value.

The Merge Field Value rule requires four pieces of information: the merge field to check, the type of data that field holds, how to compare against the merge field value and the value to compare it with.

Used to target customers that match the specified site brand, for example, US site, on the triggered email. Can only be used on triggered email campaigns; cart abandon, browse abandon, purchase complete.

Used to target customers that match the specified currency. This is typically passed from the site automatically through our script.

Used to target customers that match the specified language. This is typically passed from the site automatically through our script.

Used to deploy SmartBlocks based on whether a specific merge field value is present in the Slot URL. Typically this is done by our script, so may require updates to pass back specific values. Check with Support if you’re unsure if the value you require is being passed or not.

The Merge Field Value rule requires four pieces of information: the merge field to check, the type of data that field holds, how to compare against the merge field value and the value to compare it with.

Used to target customers on a specific site brand.

Used to deploy different SmartBlocks on different page types.

Used to deploy SmartBlocks based on the URL or parts of the URL of the page the customer is on, for example, query parameters to target customers who came in from a specific source or medium.

A URL can be broken down into four sections: the protocol, domain, path and query. As an example, for the URL:

https://www.example.com/page/about?id=3&name=page

The Current Page URL rule lets you compare one of these sections of the URL, or the full URL, against a specific value.

Used to target customers that entered the site from a specific page, or a page containing a specified text string in the URL.

Used to target a customer based on how many pages they've viewed in their current session.

Used to target a customer based on whether they have browsed a product page or not, and what products, including products with specific tags or other values, they've browsed in their current session.

Used to display different SmartBlock content based on the time of day.

Used to display different SmartBlock content based on a monthly schedule.

Used to display different SmartBlock content based on a defined date range.

Used to display different SmartBlock content based on a weekly schedule.

Used to display different SmartBlock content based on the temperature in a customer's location.

Used to display different SmartBlock content based on the weather in a customer's location.

Used to target customers within a specified country, based on either a derived or imported location value.

Used to target a customer based on their proximity to an area or a single location from a predefined location set.

Used to target customers where we know their location.

Used to target a customer based on their proximity to a set location.

Used to display SmartBlocks based on a field related to the product currently being displayed, or a specific product that is specified in the rule.

When configuring a rule, it might be necessary to specify a comparison, to tell the rule what to do with the data it receives.

For example, targeting a customer who’s browsing a product with a name that contains the word football would be a contains comparison between product.name and football.

Different types of data have different available comparisons. For example, a date could be before or after another date, while a number could be greater than or less than another number.

Marketing Rules support four standard data types: