# How catalog triggers work

> What a catalog trigger is, the catalog and audience rules, when Releva checks them, the event each one produces, how triggered workflows use it, and what the Events dispatched number means.

A **catalog trigger** connects two things Releva already knows: what changed in your product catalog, and which customers interacted with those products. Three times a day it looks for products that recently changed in the way you describe, finds the profiles that acted on those products, and writes one event per profile. A **triggered workflow** that listens for that event then sends the message: “the shirt you looked at is back in stock”, “the headphones on your wishlist are 20 % cheaper”.

You manage catalog triggers under **Data Platform › Catalog Triggers**. The guides show the clicks: [Create a catalog trigger](https://releva.ai/documentation/guides/catalog-triggers/create-a-catalog-trigger/) and [Change a catalog trigger](https://releva.ai/documentation/guides/catalog-triggers/change-a-catalog-trigger/).

## Two rule lists

A trigger has a name and two lists of rules.

| List               | Question it answers                 | Rules                                                                                                                                                                                                      |
| ------------------ | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Catalog Rules**  | Which products?                     | **Price increase**, **Price decrease**, **Became in stock**, **Became out of stock**, **Product attributes**                                                                                               |
| **Audience Rules** | Which profiles, for those products? | The behaviour rules you know from segments: **Viewed product**, **Added to cart**, **Added to wishlist**, **Purchased**, **Profile Attributes**, **Belongs to Segment**, **Performed action: …** and so on |

The four change rules match **catalog events**. Releva writes one whenever a product update changes its price or its availability: a price change gives a price-increase or price-decrease event that carries the **Discount amount** (old price minus new price) and, for decreases, the **Discount %** of the old price; an availability change gives an in-stock or out-of-stock event. A product update that changes neither produces no catalog event, so a trigger never fires for it. How updates reach Releva is explained in [How your catalog gets into Releva](https://releva.ai/documentation/learn/catalog/how-your-catalog-gets-into-releva/).

Each rule can take filters. Price rules offer **Price**, **Discount amount** and **Discount %**; every change rule also offers product and event custom fields; **Product attributes** offers **Categories**, **Price**, **Discount amount** and **Discount %**. Catalog rules cannot be inverted (there is no **Mode** switch), and when you add several, a product has to match all of them.

Audience rules work as in a segment, with one difference that matters: the first action rule in its normal mode is the **baseline**. Releva matches the products of that action against the catalog rules, so a profile qualifies only for the products it viewed, carted, wishlisted or bought. That is why a trigger must have at least one action rule that is not set to **Not …**; without one, saving fails. Further action rules narrow the pairs of profile and product (a **Not Purchased** rule removes the products the profile already bought), and **Profile Attributes** or **Belongs to Segment** rules narrow the profiles.

The help text under **Audience Rules** gives the classic example: “if you wish to target profiles who have viewed a product which is now in stock, you need to select ‘In stock’ under Catalog Rules and ‘Viewed Product’ under Audience Rules”. The option labels are **Became in stock** and **Viewed product**.

## When Releva checks

Releva evaluates every catalog trigger at **02:00, 10:00 and 18:00** (server time). Each run looks at catalog events from the previous **8 hours**, ending 10 minutes before the run so that late updates are included. A product that came back in stock at 11:00 is therefore picked up by the 18:00 run. If a run is delayed by more than 8 hours it is skipped, because the catalog may already have changed again.

There is no manual “run now”; saving a trigger does not evaluate it.

## A trigger only runs for a running workflow

A catalog trigger is evaluated only when at least one **triggered** workflow that is switched **On** uses its event. Otherwise the run skips it and nothing is counted. To put a trigger to work:

1. Create the trigger.
2. Create a workflow under **Workflows › Triggered** and, in **Event**, pick **Catalog trigger - \<name>**. Catalog trigger events appear in the picker under their own name, without the “Custom Event:” prefix, and are always allowed as trigger events.
3. Switch the workflow **On**.

Read [How workflows work](https://releva.ai/documentation/learn/workflows/how-workflows-work/) for the workflow side.

## The event a trigger produces

For every profile that matches, the run writes one event named **Catalog trigger - \<name>** to that profile. The event carries the matched products (up to 50 per profile, with their current catalog data such as name, price and image), so an email step in the workflow can show exactly the products that changed. A profile that matched no product gets no event.

The event is an ordinary profile event afterwards. You can see it on the profile’s timeline, use it as a **Performed action: Catalog trigger - \<name>** rule in segments, and pick it as a trigger event in other workflows.

Renaming a trigger renames its event. Triggered workflows that used the old name are updated to the new one automatically. Deleting a trigger stops the events; workflows that used it are not changed, they just never fire again.

## Statistics

The **Catalog Triggers** list has a date picker (the last 30 days by default) and shows **Events dispatched** per trigger: the number of trigger events written in that period. Until a running workflow uses the trigger, the number stays at 0. **Export** on the list, and the **Catalog Triggers** scope in **Analytics › Exports**, give a CSV with **Unique Events** and **Unique profiles** per trigger; see [How exports work](https://releva.ai/documentation/learn/exports/how-exports-work/).

## Next steps

* [Create a catalog trigger](https://releva.ai/documentation/guides/catalog-triggers/create-a-catalog-trigger/): Pair a product change with an audience action for a triggered workflow.
* [Change a catalog trigger](https://releva.ai/documentation/guides/catalog-triggers/change-a-catalog-trigger/): Narrow a trigger’s rule with a filter, or copy or delete the trigger.
* [How your catalog gets into Releva](https://releva.ai/documentation/learn/catalog/how-your-catalog-gets-into-releva/): Learn how product updates reach Releva, which is what a trigger watches.
* [How workflows work](https://releva.ai/documentation/learn/workflows/how-workflows-work/): Learn how a triggered workflow runs and when its steps send.