This guide explains how preferences are evaluated when workflows trigger notifications. For an overview of preferences, see User Preferences.Documentation Index
Fetch the complete documentation index at: https://docs.suprsend.com/llms.txt
Use this file to discover all available pages before exploring further.
How preferences are evaluated
When a workflow triggers, SuprSend evaluates preferences for each recipient before each delivery node.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.
Factoring in tenant preferences
If you are triggering notifications for a tenant, tenant default preferences override category-level default preferences.
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.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.
Subscriber preference update in request logs.Preference precedence order
The system evaluates preferences in this order:- User preference - Individual user’s explicit preference setting
- Tenant default preference - Default preference set at tenant level
- Category default preference - Default preference set at the category level
Channel-level opt-outs (e.g., email unsubscribe, SMS STOP, mobile OS push opt-out) override all category and tenant preferences.