Skip to main content
Use this flow to automatically notify customers when the price drops on a product they previously viewed on your site. It is one of the highest-converting triggered communications you can launch, because the customer has already shown direct intent on the exact item that is now cheaper.

​
Before you start

Before you build the flow, create the automated campaign you intend to send. The flow itself only handles the trigger and the conditions — the message is sent by the campaign you select inside it. The campaign can use any channel supported by Maestra:
  • Email
  • SMS
  • Viber
  • Mobile push
  • Web push
Inside the campaign, insert the viewed product using the ProductView parameter, or build the block visually with the drag-and-drop email builder so you do not have to work with parameters at all.
You can enrich the campaign with related products or personalized recommendations. Both can be added as parameters or, more easily, dropped in as ready-made blocks in the drag-and-drop builder.

​
How the flow works

The flow listens for the Viewed Product Changed — Price Decreased event. The event fires when the current price of a product the customer has viewed becomes lower than the price at the moment the customer viewed it. Key behaviors of the event:
  • It triggers repeatedly. If the price drops, rises, then drops again below the original viewed price, the event fires each time the drop happens.
  • It triggers per product. If the prices of several viewed products go down, the flow runs once for each product.
  • It does not fire on the initial price load. The event requires an actual price change after the product data has been recorded — the first price ingestion is not treated as a decrease.
  • It respects regional pricing. If the customer has an assigned zone and the product has zone-specific prices, the event tracks price changes for that customer’s zone. If there is no zone-specific price, the event uses the price from the primary feed.

​
Build the flow

1

Add the trigger

Start the flow with the Viewed Product Changed — Price Decreased event.
2

Limit how often the flow can run per customer

Add a frequency cap so a single customer does not receive multiple price-drop messages at the same time. Without a cap, a customer who viewed many products could be hit with several emails in quick succession if prices change in a batch update.
3

Restrict delivery times

Add a time window so the flow does not send messages outside of acceptable hours — for example, overnight. The flow will pause and wait for the allowed window before continuing.
If you also run price-drop campaigns based on lists, add a delay here so the list-based mechanics fire first. This prevents the triggered flow from racing ahead of your scheduled list campaigns.
4

Check the product and the view

Add conditions that confirm:
  • The customer viewed the product recently (so you are not messaging about a product they looked at months ago).
  • The product is currently in stock and available for purchase.
Both checks together prevent you from sending an irrelevant message about a stale view or an out-of-stock item.
5

Check the subscription and contact

Add a condition that verifies the customer:
  • Is subscribed to the channel you are about to use.
  • Has a valid contact (email address, phone number, push token, etc.) for that channel.
6

Send the campaign

Add the send step and select the automated campaign you prepared earlier. The viewed product is passed into the campaign automatically, so it appears in the message.
7

Activate the flow

Once all steps are configured, activate the flow so it starts listening for price-drop events.

​
Adding recommendations

To increase relevance and average order value, supplement the viewed product with extra items:
  • Related products — products related to the viewed item, inserted via a related-products parameter or a related-products block in the drag-and-drop builder.
  • Personalized recommendations — products recommended specifically for the recipient, inserted via a recipient-level recommendations parameter or a recommendations block in the builder.
Both options work in the same flow; you can use one or both.

​
A/B testing

Use A/B testing on the campaign to compare subject lines, copy, hero blocks, or recommendation strategies, and let Maestra surface the variant that performs best.