Notification

A notification is what users receive when they are a recipient of a broadcast. Notifications are central to the MagicBell platform, representing the final communication that reaches each individual user.

Notifications have the following characteristics:

• They are addressed to a specific user.
• They inherit content from the broadcast that created them.
• They track user interactions such as read, seen, and archived states.
• They maintain status information for troubleshooting delivery issues.
• They preserve custom attributes and channel-specific overrides from the original broadcast.

Lifecycle

1. A notification is created when a broadcast targets a specific user.
2. The notification is delivered to the user through configured channels.
3. Users can interact with notifications (read, archive, etc.), updating their status.
4. Notifications maintain a full history of user interactions through timestamps.

Best Practices

• Use the notification status to track user engagement with your notifications.
• Build UI components that respect and display notification states (unread, read, archived).
• Consider implementing notification archiving to help users manage their notification history.
• Use the timestamps (sent_at, read_at, seen_at) to analyze user engagement patterns.
• Remember that notifications inherit their content and structure from broadcasts.