Automation Trigger + Trigger Event Split
Merchants can use a new “Product Price Dropped” trigger event to create an automation that will be triggered whenever price is dropped on a product. When this trigger event is user will define:
Price Drop Threshold: The dollar amount or percentage a product’s price needs to drop in order to trigger the automation
Audience Definition: Define which subscribers to enroll the automation based on their previous engagement with the product whose price dropped.
Merchants can include subscribers
who started checkout with the product in their cart within the past X days
who have previously viewed the product within the past X days
the maximum lookback window is 90 days.
Merchants can exclude subscribers
who have purchased the product whose price dropped within the last X days.
the maximum lookback window is 90 days.
Price Drop Trigger Event Filter Data
Merchants can use the Price Drop trigger event data to add event filters or trigger event splits to create a price drop automation that will only trigger based on certain criteria or split the automation to deploy different messaging strategies. This allows merchants to adjust the message strategies according to the item's original price and/or the extent of the price reduction. Available trigger filters include:
product id
product type
product tag
product name
product variant id
SKU
old price
new price
Using these available filter criteria merchants could create a price drop automation that fired for a particular product. Or, using a trigger event split, merchants could develop different messages for different products within the same flow.
New Price Drop Merge Tags
Merchants can include contextual information about the price drop event and the product via new merge tags available in the send message action so that messaging content is relevant, drives engagement, and allows for creating a sense of urgency. New merge tags that are available when the Price Drop event is selected as the trigger event for the automation include:
The name of the product whose price dropped
A link to the product (product URL)
Amount of the price drop in dollars (e.g. $15.00)
Percent of the drop (e.g 15%)
Product’s new price in dollars (e.g. $10.99)
Product’s original price in dollars (e.g. $15.00)
FAQs
Add any questions, and their answers, that you think would be helpful to know or will be common questions asked
How does our Price Drop automation differ from our competitors?
Klaviyo's Price Drop feature triggers only when the price of all product variants falls to the same level; it does not recognize individual variant price changes. However, our implementation can initiate a price drop event for each variant's unique price change.
Attentive's Price Drop automation cannot target subscribers based on view history, only those who have added the product to their cart within a specific time frame.
Attentive can only trigger a Price Drop automation based on a percentage threshold for the price drop, rather than on the raw dollar value of the price drop. Our implementation supports both of these methods for defining the price drop trigger threshold.
How is the Price Drop Automation triggered?
The Price Drop automation activates whenever a product's price is decreased and meets the pre-set threshold (dollar based or percent) for the automation. If the price decrease for a product does not meet the threshold then the automation is not triggered.
Can a shop restrict the Price Drop automation to only apply to certain products?
Yes. By default, the price drop automation will be triggered for any price drop on a product that meets the threshold criteria. However using the available filters for the Price Drop event, merchants can restrict the automation to only fire for certain products. Or by using a trigger event split, merchants can create different messaging strategies for different products all in one single price drop flow.
What is the maximum time frame that can be applied when defining which subscribers to include/exclude?
90 days is the maximum lookback period that is supported when defining which subscribers to include based on view, add to cart, and purchase history.
Will price drop automations exclude customers who purchased a specific product, or will they exclude any customer who has ever made a purchase?
When a product’s price is lowered, the Price Drop automation will filter out customers who have already purchased that specific product based on the defined exclusion time frame.
When users activate a Price Drop automation, will it include subscribers who previously added a product whose price has dropped to their cart or who previously viewed the product, or will it only consider subscribers who performed those actions since the automation was enabled?
Subscriber evaluation for Price Drop automations is retroactive for the look back periods that are defined. For example, if you activate a Price Drop automation today and set the viewed product look back period to 15 days, any subscriber within the last 15 days who viewed the product that dropped by the set threshold (e.g. 15% or $5) would be enrolled in the automation.
Can users add additional subscriber filters to price automations or are they limited to “started a checkout” or “view product” filters?
Price Drop automations will support subscriber filters in addition to the required audience targeting filters (Viewed Product or Added Product to Cart). However, these filters will further restrict the potential audience that can be enrolled in the automation.