Activation limits

Learn how to set activation limits for reactors in the Loyalty Engine, including tenant-wide and per-user limits to control how many times a reactor can trigger.

Activation limits allow you to control how many times a reactor can trigger before it should stop, either for all users (tenant-level) or on a per-user basis.

Specifying an activation limit of once per user

Editing a reactor resets the activation history, as a new reactor is created each time a reactor is edited.

If a user previously triggered the reactor and an activation limit is in place (e.g., one activation per user), they will be able to activate the newly created reactor again.

---

Tenant activation limit

A tenant activation limit applies across your entire tenant, meaning that once the reactor has been triggered a set number of times, it will stop running for all users.

When a tenant activation limit is in place, there is no limit on how many times individual users can trigger the reactor unless additional criteria are specified.

---

Subject activation limit

A subject activation limit applies on a per-user basis, meaning each user can trigger the reactor a set number of times before it will stop processing events from that user.

When a subject activation limit is in place, the tenant limit is unlimited, and the reactor will run indefinitely unless otherwise restricted.

If you need both tenant and subject activation limits, set a tenant activation limit and use audience criteria to control subject-based limits.

For example, you can create an audience where users are only eligible to trigger the reactor if they’ve reported an event fewer than X times.

See Limit a reactor an audience.

When setting activation limits, consider whether allowing unlimited activations could leave the reactor open to abuse or unintended behaviour.

Setting appropriate limits can help manage the lifecycle of your reactors and ensure they only trigger under controlled conditions.

---

FAQs

Can I edit an activation limit after the reactor is created?

Yes, but remember that editing a reactor ends the original and creates a new one, which resets the activation history.

Can I set both tenant and subject activation limits simultaneously?

Yes, but you’ll need to use audience criteria to handle subject-based limits, as the Loyalty Engine doesn’t directly support both limits at once.

What happens if I don’t set any activation limits?

Without activation limits, the reactor will run indefinitely, which may be fine for certain use cases but could lead to misuse if not properly monitored.

What happens when a reactor reaches its tenant activation limit?

It is ended and stops listening to the event stream.