---
title: CDP Live Events
slug: cdp-live-events
createdAt: 2025-12-10T17:12:16.391Z
---

The CDP Live Events view provides real-time visibility into all events captured by Chord CDP, filterable by source. Use this view to monitor data collection, debug integration issues, and verify that events are being tracked correctly.

# Overview

Incoming events are the raw data signals collected by [CDP Sources](docId\:Ho4HIWVPV4IbGWwn67IAh). These include page views, track events and identify events. Each event is captured, processed, and then routed to your [CDP Destinations](docId:8Q9LBD5xxsaBWfr5xsA1Y).

## Viewing Events

The events table displays the following information for each captured event:

- **Date (UTC):** The timestamp when the event was received by Chord CDP
- **Type:** The event type (e.g., page, track, identify)
- **Page Path:** The URL path on your site where the event originated
- **Summary:** Quick reference chips showing key event context

## Filtering Events

:::hint{type="info"}
The **Live Events** graph is designed as a **real-time debugging tool **showing the past 12 hours of data with fast, responsive search. 

For historical event analysis, we recommend querying your data warehouse (eg. Snowflake) or destination systems, which are optimized for that purpose without impacting real-time event processing
:::

Use the toolbar to filter and search your events:

- **Sites**: Select which source to view events from (if you have multiple sites configured)
- **Status**: Filter by "All" events or only "Errors" to quickly find issues
- **Search**: Search within event data (searches events from the past 12 hours)
- **Refresh**: Reload the event list to see the latest data

## Event Details

Click any row to open the event details drawer, which shows:

**Core Information**

- **Date (UTC)**: When the event was received
- **Source**: Origin of the event (browser for client-side, s2s for server-to-server)
- **Message ID**: Unique identifier for this event
- **Type**
- **Event Name**

**User Information**

- User ID / Anonymous ID
- Email

**Page Context**

- Page Title
- Page URL

**Routing Information**

- **Destinations**: Which [CDP Destinations](docId:8Q9LBD5xxsaBWfr5xsA1Y) will receieve this event
- **Chord CDP Domain**: The CDP domain that processed the event
- **Write Key**: The API key used for this event stream

**Technical Details**

- **HTTP Headers**: Request headers sent with the event
- **Event Payload**: The complete raw event data in JSON format

## Common Use Cases

**Debugging Integration Issues**

Filter by "Errors" status to quickly find events that failed processing. The error message will help identify configuration problems.

**Verifying Event Tracking**

After implementation, use this view to confirm events are being captured with the correct properties.

**Monitoring Data Flow**

Verify that events are being routed to the expected destinations.