
- Overview: Generic information about the broadcast execution:
- Broadcast slug, tenant ID and List ID (clickable)
- Broadcast Execution ID (share this with SuprSend support if you need help in debugging the broadcast or want to report an issue)
- Idempotency key (unique identifier of the request passed to SuprSend)
- Status (Triggered, Skipped, Failed)
- Start time (broadcast start timestamp)
- Preference category
- Execution history: Chronological logs of broadcast start, template loading, user profile fetching (with progress percentage), channel computation, template rendering, and notification triggering.
- Aggregate statistics: Summary of the broadcast performance:
- Total users processed (percentage and count) at each stage of the broadcast execution
- At delivery stage: Preference evaluation, messages triggered and delivery status (delivered, seen, clicked)
| Status | Meaning |
|---|---|
| 🟢 Triggered | Users who received notifications on at least one channel |
| 🟠 Skipped | Excluded due to missing channels or opt-out |
| 🔴 Failed | Trigger failed due to errors (for example, template rendering failures) |
| Error Type | Examples |
|---|---|
| Template rendering failures | Missing variables, syntax errors |
| Channel computation issues | No active channels, User Preference opt-outs, Tenant Preference opt-outs |
| Vendor Config issue | Vendor not configured for the channel and preference category or broadcast not supported for that vendor |
| Reason | Description |
|---|---|
| Unsubscribed | User has unsubscribed from that preference category or the required channel in the category |
| Missing channel | User does not have that channel or that is marked inactive due to hard bounce in the past (for example, no email address, no phone number) |