You can configure when an abandoned browse automation should be triggered with multiple criteria. This article will explain the details regarding these criteria. For more insights into the Abandoned browse trigger see "Configure the abandoned browse trigger"
The available entry criteria are based on:
- The aggregated session data
- A product view within the session
- The contact
- The frequency cap for the automation
A session is considered abandoned if there is no activity for 30 minutes. At that point, the session will be passed to the automation trigger as long as:
- the user is identified
- no product was added to the cart during the last 24 hours
- the SKUs in the session can be found in the product feed
- the session hasn't been sent to the automation trigger during the last 24 hours
In the abandoned browse trigger additional conditions, which the session also needs to match, can be applied. These are now explained:
Locale – Filter the automation to only start if the session contains a specific locale. Can also be used in a value split.
Views – Number of product views in the session.
SKUs – Number of SKUs included in the session.
External referrer – Trigger the automation only if the session starts with an external referrer/domain that contains keywords, or a specific URL.
Top category – The category from the sessions with the most product views.
Product view – In a session, there are one or multiple product views. These conditions will only trigger the flow if at least one product view matches the product view criteria.
-
Ecom – Data comes from the site/ecom:
- SKU – One or several specific SKUs are viewed during the session. (Is hidden if grouping SKUs is enabled, read more)
- Web category – A view must come from a specific web category, based on site configuration. Can also be used in a value split.
- Views – Number of product views for a specific product. The condition could be: trigger automation if the visitor has visited any product more than X times (in the same session).
-
Product feed – The product view event is enriched by data from the product feed:
- Item group Id - Multiple variants grouped (Shown if grouping SKUs is enabled, read more)
-
Title – The Product title from the product feed must for example contain certain keywords or match a specific one.
- Description – The product description from the product feed must for example contain certain keywords or match a specific one.
- Link – The link (URL) from the product feed must for example contain certain keywords or match a specific one.
- Price – The product price.
- Sales price – The product's sales price.
- Brand – The brand from the product feed must for example contain certain keywords or match a specific one.
- Color – The color from the product feed must for example contain certain keywords or match a specific one.
- Main category – The main category is the category added to the feed, by the PIM for example. The category from the product feed must for example contain certain keywords or match a specific one.
- Size – The size (text) from the product feed must for example contain certain text or match a specific one, like medium.
- Spare 1/2/3/etc. – If product spare fields are used, they can be part of the configuration as well. The spare field from the product feed must for example contain certain text or match a specific one.
These are the same as for the filtering tool. Read more about that here.
Make sure you send the right number of emails to your customers by setting a frequency cap that controls how many times a contact can be included in an automation during a set time period, for example, once every 30 days. Read more about frequency and how to succeed with your abandoned browse campaign here.
If you want to use different emails based on languages or web category, use value splits instead of creating different automations. Then you have one global frequency cap and have better control of how many emails your contacts can receive.
Article last reviewed
Comments
0 comments
Please sign in to leave a comment.