Course contentsShow
← System Design
Lesson 1724 of 1,91941. Real-World System: Notification SystemFree lesson

Notification Analytics Events

Define key events to track: sent, delivered, opened, clicked, and failed for each notification and channel.

Notification Analytics Events

What you'll learn: You'll learn which key events to track in your notification system to measure and optimize delivery success across all channels.

Why Track Events?

To improve your notification system, you need visibility into what happens at every stage of the delivery pipeline. Think of it like tracking a package shipment: you want to know when it left the warehouse, when it arrived at the destination, and whether the recipient opened it. Without this data, you're flying blind.

The Five Critical Events

Every notification—whether push, SMS, email, or in-app—should track these lifecycle events:

  1. Sent: The notification left your system and was handed off to the channel provider (APNs, FCM, Twilio, SendGrid, etc.). This confirms your system processed it.

  2. Delivered: The provider successfully delivered the message to the user's device or inbox. The phone received the push, the SMS arrived, the email landed.

  3. Opened: The user interacted with the notification by opening or viewing it. This measures engagement and relevance.

  4. Clicked: The user took action on a link or button within the notification (e.g., "View Order"). This tracks conversion and intent.

  5. Failed: The notification could not be delivered—device token invalid, phone number inactive, email bounced, etc. Critical for identifying and cleaning bad addresses.

Why Per-Channel Tracking Matters

Track these events separately for each channel. A user might receive an email (delivered) but never open it, while the same message via push gets opened immediately. This data drives decisions: "Should we shift budget from email to push for this user segment?"

Key Takeaway: Track sent, delivered, opened, clicked, and failed events for every notification and channel to measure delivery success, optimize engagement, and identify failures in your notification pipeline.