Skip to main content

Catalog Triggers

Joryio watches your product catalog and fires an event the moment a product comes back in stock or its price drops. Use these as entry events for a campaign or journey - they appear in the event picker like any other trigger - and the audience assembles itself.

  • Back in stock - fires when a product goes from out-of-stock to available.
  • Price drop - fires when a variant's price falls by at least the configured percentage (default 10%) and is purchasable.
Selecting them in the trigger picker

Joryio's own events like back_in_stock and price_drop show up as first-class options (labeled · System) when you choose the trigger/entry event - you don't have to have received one first or type the exact name. You can also build trigger conditions on their properties (e.g. product_id) before the first one ever fires.

Who gets notified​

For each transition, Joryio resolves the audience automatically and skips anyone who already purchased the product or is on a short per-user cooldown (so stock/price flapping can't re-alert the same shopper).

There are two ways the back-in-stock audience is built:

The highest-intent audience is shoppers who explicitly asked to be told. When a shopper taps a "Notify me when back in stock" button on your storefront, emit a back_in_stock_subscribed event carrying the product id:

joryio.track('back_in_stock_subscribed', { product_id: 'PRODUCT_ID' });

Joryio records the subscription. When the product restocks, those subscribers are messaged first. The subscription is one-shot - a shopper is notified once and re-subscribes if they want to be told about a future restock. To let a shopper cancel, emit back_in_stock_unsubscribed with the same product_id.

Custom event names

If your storefront already emits differently-named events for this, you don't have to rename them. Go to Products → Back-in-stock alerts and set your own subscribe / unsubscribe event names. Leave the fields blank to use the defaults (back_in_stock_subscribed / back_in_stock_unsubscribed).

2. Inferred intent (automatic fallback)​

When there are no explicit subscribers, Joryio falls back to shoppers who viewed or added the product to cart recently (default 30 days) but didn't buy

  • using the product-view and add-to-cart events your tracking already sends.

Price-drop always uses the inferred-intent audience.

note

Both paths depend on your storefront sending events (product views, add-to-cart, and - for explicit subscriptions - the back_in_stock_subscribed event). Where the storefront isn't instrumented for a product, that product produces no audience.

Choosing who gets the alert​

In Products → Back-in-stock alerts, choose who a restock alert goes to:

  • Only people who asked to be notified - shoppers who never pressed "Notify me" are not messaged, even if they looked at the product.
  • People who asked; if nobody asked, people who showed interest - the default, and how alerts worked before the setting existed.
  • Both - everyone who asked plus everyone who showed interest. A shopper in both groups gets one alert.

Look-back window (days) sets how far back "showed interest" counts, from 1 to 180 days (blank = 30). It applies to back-in-stock and price-drop alerts.

Every back_in_stock and price_drop event carries an audience property: subscribed for someone who asked, interested for someone who only showed interest (price-drop is always interested). Split a journey on it to send each group different copy - "The item you asked about is back" versus "Still thinking about it? It's back in stock".

Setting it up​

  1. Build a campaign or journey and pick Back in stock or Price drop as the entry event.
  2. (Recommended) Add a "Notify me when back in stock" button to your product pages that emits back_in_stock_subscribed.
  3. That's it - when a product restocks or drops in price, the enrolled audience is assembled and messaged automatically.