> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/live-events.md).

# Live Events

Live Events shows events as Chord receives them and as it sends them on. Use it to check that tracking works, find errors and see what each destination received.

To open it, go to **CDP** in Chord and click the **Live Events** tab. It has three tabs of its own.

{% hint style="info" %}
Live Events is a debugging tool. It shows recent events and searches only the past 12 hours. For older events, query your data warehouse or the destination.
{% endhint %}

## Incoming Events

These are the events your sources send to Chord, such as page views, track events and identify events. The table shows:

* **Date (UTC)**: when Chord received the event.
* **Type**: page, track or identify.
* **Page Path**: the page the event came from.
* **Summary**: chips with key details.

Use the toolbar to narrow the list:

* **Sites**: pick one source, if you have more than one.
* **Status**: show All events or only Errors.
* **Search**: look inside event data. It only searches the past 12 hours.
* **Refresh**: load the latest events.

Click a row to open the event. The details include:

* **Core information**: date, source (browser, or s2s for server to server), message ID, type and event name.
* **User**: user ID or anonymous ID, and email.
* **Page**: title and URL.
* **Routing**: the destinations that will receive the event, the Chord domain and the write key.
* **Technical details**: the HTTP headers and the full event as JSON.

## API Destinations & Functions Logs

This tab shows what happened when Chord sent events to server destinations and ran your [functions](/activate/event-streaming/functions.md). Each row has the date, the function or destination, a level such as an error or warning, and a summary. Click a row for details.

Use it to find out why a destination rejected an event, or to read what your function logged. Warnings about [property mappings](/activate/event-streaming/property-mappings.md) on server destinations show here too.

## Batches & Data Warehouse Events

This tab shows loads to data warehouses, which arrive in batches. Each row shows the date, batch size, status, table name and a summary. You can filter by connection, by status and by mode (Batch or Stream).

## Common uses

* **Fix a broken setup.** Filter Incoming Events by Errors, then read the error message.
* **Check tracking after you launch.** Confirm events arrive with the right properties.
* **Check routing.** Open an event and look at its destinations.

Browser destinations send events straight from the visitor's browser, so they don't appear on the destination tabs. See [Browser and server destinations](/activate/event-streaming/browser-and-server-destinations.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/activate/event-streaming/live-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.