Listrak’s Alerts Suite is a marketing strategy designed to recoup lost revenue. Included with the Alerts Suite are Back-in-Stock, Price Drop, and Low Inventory Alerts. Customers are automatically notified when their desired products are back-in-stock or when the price of an item they’ve browsed drops or the quantity drops below a specified level.

💡 In order to configure your alerts suite, you will first need to complete the JavaScript Integration and then complete the Alerts Integration

Click on the link below to jump to information on how to configure specific alert types. Configuring alert allows you to create an event to trigger a Conductor conversation to automate follow ups. If you are configuring an Alert Journey, the alert setup can be completed directly in the Journey Hub interface.

Back-In-Stock Alerts

Price Drop Alerts

Low Inventory Alerts


Creating a List

Before configuring your alert, be sure to have created a new list, just for your alerts campaigns. This ensures that all of your alerts settings and analytics are in one place.

Lists can be created under Manage > Lists.


Back-In-Stock Alerts

The Back-In-Stock Alert can be triggered based on the item a contact browses or signs up for notification about when a product is back in stock. This solution can also help you identify which products are more popular, helping them to determine how much to order in the future.

💡 Back-in-Stock alerts are determined by the quantity on hand listed in the data you send to Listrak.

Creating an Alert

  1. Navigate to Solutions > Alerts.

  2. Click New Alert.

  3. On the Create Page

    1. Enter a name for the alert.

    2. Select Back-in-Stock for the Alert Type.

    3. Select the type of action that Listrak will track for the alert: Sign-Up or Browse.

      💡 The Sign-Up action allows you to send additional types of messages and configure advanced properties for notifying contacts when an item is back in stock.

      ⚠️ Only one alert action type can be configured for back-in-stock per list.

    4. Select your list from the drop-down menu.

    5. Click Continue.

  4. On the configure page:

    1. Enter BIS for the Alert Definition Code.

    2. Next, you will create the subscription point. This is necessary when using an alert campaign in Listrak Conductor. The steps below guide you through creating a new event.

      ⚠️ This is only available when using the sign up action type.

      1. Click Create New under the Subscription Event section.

      2. Enter a name to help you identify the subscription event.

      3. Click Save.

    3. You will now create an Alert Event. This event is used to enter contacts into a Conductor thread.

      1. Click Create New under the Alert Event section.

      2. Enter a name to help you identify the event.

      3. Click Save.

  5. Next, specify a Quantity Threshold.

    💡 This is the number of items that must be in stock before the Back-in-Stock Alert is deployed.

  6. Then, if using the signup action, set contacts notified type.

    1. All will send a notification email to all contacts who have signed up for notification.

    2. Custom allows you to specify how many contacts will receive notifications.

      1. Contacts per Unit In-Stock: This setting allows you to send a number of notifications per individual item in stock. For example, a value of 2 would send two notifications for each item in stock.

      2. Contact Notification Priority Order: This setting allows you to determine who should receive notifications first. FirstInLastOut sends notification based on who signed up most recently, whereas FirstInIFirstOut sends notifications based on who signed up first.

  7. If using the signup action, you can enable additional types of messages. You will need to create a new event following step 4c for each of these messages you enable.

    💡 Enable Follow-up Reminders: this feature allows you to include follow-up messages in your conductor conversation.

    💡 Enable Discontinued Products: this feature allows you to create a Conductor conversation that send automated messages if a contact's product is discontinued.

  8. Once you have confirmed your settings, click Continue.

  9. On the Save page, confirm your settings and click Save.

After you've configured your alert, the next step is to create a message and set up the conversation.


Price Drop Alerts

Price Drop notification emails are sent to shoppers when the price of a product has dropped by an amount, determined by either a set dollar amount or a percentage of price. Reach out to your customers at the right time to let them know about this change and re-engage their interest in a product. Price drop alerts can be triggered by a contact's browsing activity or for items placed in a cart.

Creating an Alert

  1. Navigate to Solutions > Alerts.

  2. Click New Alert.

  3. On the create step:

    1. Enter a name for the alert.

    2. Select Price Drop from the drop-down menu for the Alert Type.

    3. Select the type of action that will trigger an alert, either Browse or Carted Item.

    4. ⚠️ Only one alert action type can be configured for price drop per list.

    5. Select the previously created Alerts list.

    6. Click Continue.

  4. On the Configure page:

    1. You will now create an Alert Event. This event is used to enter contacts into a Conductor thread.

      1. Click Create New under the Alert Event section.

      2. Enter a name to help you identify the event.

      3. Click Save.

    2. Next, enter a Drop Threshold. This is the numeric value that determines the amount the price must change by in order to trigger the price drop event.

    3. Then, select a Threshold Type from the drop-down. This determines if the number provided represents a dollar amount or percentage of price.

    4. Lastly, set a Relevancy Window.

      💡 The relevancy window determines how long after a contact takes the specified action (browed or carted an item) Listrak will check to see if the price has changed. This window starts the day customers are entered into the queue, and if the price of the product doesn't drop by the threshold within this window, they will be removed from the queue for that product.

    5. Click Continue.

  5. On the Save page, confirm your settings and click Save.

After you've configured your alert, the next step is to create a message and set up the conversation.


Low Inventory Alert

Low Inventory Alerts are triggered when inventory levels reach a threshold to warn contacts that the product is almost sold out. Low Inventory Alerts can be triggered by a contact's browse activity or based on the items placed in their cart.

Creating an Alert

  1. Navigate to Solutions > Alerts.

  2. Click New Alert.

  3. On the create step:

    1. Enter a name for the alert.

    2. Select Low Inventory from the drop-down menu for the Alert Type.

    3. Select the type of action that will trigger an alert, either Browse or Carted Item.

      ⚠️ Only one alert action type can be configured for low inventory per list.

    4. Select the previously created Alerts list.

    5. Click Continue.

  4. On the Configure page:

    1. You will now create an Alert Event. This event is used to enter contacts into a Conductor thread.

      1. Click Create New under the Alert Event section.

      2. Enter a name to help you identify the event.

      3. Click Save.

    2. Next, enter a Quantity Threshold. This is the number of items the quantity on hand has to drop to or below in order for the Low Inventory Alert to be triggered.

    3. Lastly, set a Relevancy Window.

      💡 The relevancy window determines how long after a contact takes the specified action (browed or carted an item) Listrak will check to see if the price has changed. This window starts the day customers are entered into the queue, and if the price of the product doesn't drop by the threshold within this window, they will be removed from the queue for that product.

    4. Click Continue.

  5. On the Save page, confirm your settings and click Save.

After you've configured your alert, the next step is to create a message and set up the conversation.

Did this answer your question?