Catalog triggers

Catalog triggers start a scenario on their own when your product catalog changes — a price drops, an item is back in stock, a new product lands, stock runs low, or an offer nears its end date. They reach only customers who showed interest in the item, such as viewing it or adding it to cart.

Here's what catalog triggers are, the trigger types you can use, what you need before you start, and the limits that apply. To build one, see Configure a catalog trigger.

Prerequisites

• Item collections in Data hub: Catalog triggers need Data hub item collections (unified product data). They don't support legacy catalogs.

How catalog triggers work

Each time your catalog is updated, the following sequence runs:

1. The system ingests the catalog change.
2. Affected items are grouped into batches of up to 1000 items within a window of up to 15 minutes.
3. A safety window holds the trigger until the change has persisted beyond the stability window, preventing transient changes from firing a message.
4. The platform evaluates your item filters and customer interest, per item and per customer.
5. The scenario runs once per batch for each qualifying customer. Matched items are available for use in message personalization.

Trigger types

Catalog triggers are used in scenarios. Under Triggers, click Catalog, and select one of the following triggers, each with its own settings and filters:

Batching

When a single large item collection update affects many items, the platform groups them into batches of up to 10,000 items, sorted by overall customer interest. The scenario runs once per batch for each qualifying customer, allowing you to present multiple items of interest in a single message.

Each batching window lasts up to 15 minutes. If an update streams continuously beyond that window, it rolls into additional batches — each capped at 10,000 items.

Limits