Preference Evaluation

​

How preferences are evaluated

1

Evaluating Recipient preferences

If user preferences aren’t set, the system picks the default preference setting. Once a user sets a preference for a category, future changes to default preferences do not override the user’s choice.

2

Factoring in tenant preferences

If you are triggering notifications for a tenant, tenant default preferences override category-level default preferences.

3

Resolving preference conflicts

The order of precedence is always user > tenant > category default. However, if you turn off notifications in a category from the tenant page, users will not receive notifications in that category, even if they previously opted in.

4

Debugging preference evaluation in workflow runs

User preferences may change over time. When debugging a workflow run, you can inspect the exact preferences that were active at that moment. You can view this using the step-by-step debugger in workflow executions.

Use the “Preference Evaluation” panel in each workflow step to see what preference blocked or allowed the notification.

You can also track when a user updated their preference by filtering on Subscriber preference update in request logs.

​

Preference precedence order

1. User preference - Individual user’s explicit preference setting
2. Tenant default preference - Default preference set at tenant level
3. Category default preference - Default preference set at the category level