> This page is part of the [Customer.io documentation](https://docs-customerio.netlify.app). For the complete index, see [llms.txt](https://docs-customerio.netlify.app/llms.txt).
> Last updated: July 30, 2026

# Monitor live notifications

[PremiumThis feature is available for Premium plans.](/accounts/billing/plan-features/) [EnterpriseThis feature is available for Enterprise plans.](/accounts/billing/plan-features/)

Track every live notification sent to a person—including the full timeline of starts, updates, and ends—on their profile.

## Review a person’s live notifications

Go to **Profiles**, click a profile, and go to the **Live notifications** tab to see their last 30 days of live notifications.

[![ln-profile-tab.png](https://docs.customer.io/images/ln-profile-tab.png)](#ea512d531deab909245b2ef1e19c3000-lightbox)

Each row shows the activity, when it started, its last update, and its current status—`active`, `ended`, `expired`, or `failed`. You can filter the list by status, type, and time range.

Click an activity to see its details:

[![ln-profile-activity-details.png](https://docs.customer.io/images/ln-profile-activity-details.png)](#044323a6a9dacfdc45ed71e3c8d3eaa7-lightbox)

*   **The delivery timeline**—every start, update, and end delivery for the activity with the content payload each one carried. This is the full story of what your customer saw on their device.
*   **Metadata**—the activity’s ID, person, and notification type.
*   **Live activity config**—status with the start and end times.
*   **Attributes**—this is where you can find the unique activity ID, like an order number. This id doesn’t change over the life of the activity.
*   **Content state**—the fields you set or update with each content payload. This shows the most recent data.

 Use the timeline to debug live notifications

If an update didn’t appear on a device, find the activity on the intended profile and check if the notification or a specific delivery failed to send.

## Check status through the API

Your server can look up an activity’s state, failure reason, and last delivery at any time with the [status endpoint](/integrations/api/app/#tag/live-notifications/GET/v1/live_notifications/%7Binstance_id%7D), referencing the activity by its instance ID.

## Retrieve delivery records and metrics

To retrieve live-notification delivery records and their metrics, use the Messages API: [`GET /v1/messages?type=live_notification`](/integrations/api/app/#operation/listMessages) returns deliveries, and [`GET /v1/messages/{message_id}`](/integrations/api/app/#operation/getMessage) returns a single delivery.

The status endpoint serves a different purpose: it returns the current state and latest delivery for a single instance. Customer.io doesn’t currently expose a public aggregate endpoint, reporting-webhook event, or live-notification-specific CSV export.

*   *   [Review a person’s live notifications](#review-a-persons-live-notifications)
    *   [Check status through the API](#check-status-through-the-api)
    *   [Retrieve delivery records and metrics](#retrieve-delivery-records-and-metrics)

Copy page

Copy page [Download .md](/messaging/channels/live-notifications/manage-and-monitor.md)

Is this page helpful?

![](https://docs.customer.io/images/export-success.png) ![](https://docs.customer.io/images/export-failure.png)

# How can we make it better?

Close

Do you need help from Customer.io support?  No  
 Yes

What part of Customer.io do you need help with? 

How can we improve this page?

Email (optional):  Please provide a valid email address

 I am not a bot

 

We appreciate your feedback!

Our support team will contact you as soon as possible