Page tree
Skip to end of metadata
Go to start of metadata

Trigger filters allow you to layer in catalog-based business logic to your triggered campaigns. The filters can help make your triggered campaigns even more targeted and relevant, with rules available for configuration based on items in your catalog. For example, you might want to limit the products eligible for a Price Reduction trigger to those costing more than $50. Or you might want to prevent New Item in Favorite Category triggered messages from being delivered to customers who purchased in the last 90 days so as not to bombard them. Whatever your business requirements, trigger filters can help ensure you're delivering the right experience for your customers.

Interaction Studio Classic Only

  • The contents of this article are intended for customers using Interaction Studio (formerly Evergage Classic). Do not adjust your beacon version to downgrade or upgrade.
  • The Visual Editor Chrome Extension will no longer be available starting January 1, 2023. For more information, see this knowledge article.
This Article Explains

This article details how to use catalog and user behavior trigger filters in triggered campaigns.

Sections in this Article

Catalog Filters

Catalog filters add filtering logic on the trigger items using the catalog attributes and dimensions you have assigned to that item type. If you add catalog filters, the trigger item(s) must fulfill all the criteria in order for the trigger to successfully process.

  • Attributes that are available by default include Price and Average Rating. Custom attributes assigned to items can also be included.
  • All Dimensions configured for the item type are available for inclusion/exclusion filtering on specific dimensional values.

User Behavior Filters

User behavior filters add filtering logic using customer interaction with the trigger item(s). If you add user behavior filters, the user will need to fulfill each criteria assigned in order to qualify for the trigger.

  • User behavior triggers are based on the below item actions or interactions. Check with your developer on how these item actions are set up for your account.
    • View (count of views and time spent viewing)
      • Time spent viewing is not a requirement for this filter, and can be set to 0.
    • Add to cart
    • Purchase
    • Favorite
    • Get recommendations for – customer has had a recommendation returned in any channel in the last _____ days
  • User behavior triggers can be based on customer interaction with any item, or with the above (trigger) item
  • User behavior triggers can use a "did/did not" operator.

The Add to Cart user behavior filter references the user's cart, as it is stored in Interaction Studio, to ensure a positive user experience. If all possible trigger items are filtered out as a result of this check (or any other catalog or behavioral filters), the message will not be sent.

  • When selecting the did and above operators, the filter checks to see whether the trigger item(s) are present in the user's cart, and will filter it out if it is not present. 
    • This would prevent the trigger from firing if the user has removed the item from the cart.
    • This would prevent the trigger from firing if the user has purchased the item (thus the cart would be empty).
  • If the did and any operators are selected, the filter will check to see whether any items are present in the user's cart.
  • If the did not and trigger operators are selected, the filter will check to see whether the trigger item is not currently present in the user's cart.
  • If the did not and any operators are selected, the filter will check to see whether the user's cart is empty.

Note: Interaction Studio stores a user's cart as an object, which allows this filter to perform these checks.

Interaction Studio does not store a user's "saved for later" or "wishlist" as an object, meaning the Favorite item action and user behavior filter will not conduct similar checks – it will simply check whether the user completed the Favorite item action on the trigger items during the configured lookback.