> 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/notifications.md).

# Notifications

Notifications email your team when data stops flowing or a setup changes. You can set them up for sites (your sources), connections and destinations, and send each one to any email addresses you choose.

Use them as an early warning, so you catch problems quickly.

{% hint style="info" %}
Notifications don't cover browser destinations. Those send events straight from the visitor's browser, so the events don't pass through Chord. See [Browser and server destinations](/activate/event-streaming/browser-and-server-destinations.md).
{% endhint %}

## Notification types

The **Notifications** tab has three sections. Each offers different types.

| Section      | Type                | You're notified when                                                                    |
| ------------ | ------------------- | --------------------------------------------------------------------------------------- |
| Sites        | No data received    | A site sends no events for a set period.                                                |
| Connections  | Delivery failures   | Events fail to reach the destination.                                                   |
| Connections  | Function errors     | A [function](/activate/event-streaming/functions.md) on the connection throws an error. |
| Connections  | Modified or deleted | The connection is changed or deleted.                                                   |
| Destinations | Modified or deleted | The destination is changed or deleted.                                                  |

## Choose what to watch

Start with the sites and connections that would hurt most if they stopped working.

| If this matters to you                                                             | Turn on                                                       |
| ---------------------------------------------------------------------------------- | ------------------------------------------------------------- |
| Ad, email or SMS tools that drive revenue, such as Meta Conversions API or Klaviyo | **Delivery failures** on those connections                    |
| Connections that use functions to change or filter events                          | **Function errors** on those connections                      |
| Your main storefront or app, which should send events all day                      | **No data received** on those sites                           |
| Knowing when someone edits or removes a key integration                            | **Modified or deleted** on those connections and destinations |

Tips:

* Send alerts to a shared inbox, not one person, so nothing is missed when someone is out.
* A quiet site, such as a low-traffic test site, can trigger alerts that aren't real problems. Skip it, or send its alerts to a lower-priority inbox.

## How notifications are sent

* **Chord checks for problems every hour.** This covers no data received, delivery failures and function errors. When it finds one, it emails every address on that notification.
* **You get one email per issue every 24 hours.** If a problem lasts, you don't get a new email each hour.
* **Modified or deleted notifications go out right away.**
* **There is no "fixed" email.** Once you fix a problem, the alerts stop unless it happens again.

Each email has a short summary. For the details, open [Live Events](/activate/event-streaming/live-events.md).

## Set up a notification

You need permission to manage notifications, and your sites and connections must already be set up.

1. In Chord, go to **CDP** and open the **Notifications** tab.
2. Find the section you want (**Sites**, **Connections** or **Destinations**) and click **Add Notification**.
3. Choose the site, connection or destination from the list.
4. Enter one or more email addresses, separated by commas.
5. Under **Notification types**, check each type you want.
6. Click **Save**.

![The Add Connection Notification panel](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-08cc4da99d69b31d4becba5776df72a057f81a52%2Fadd-connection-notification.png?alt=media)

Your notification now appears in its section, with its types and email addresses.

To remove a notification, click the trash icon on its right.

## What notifications don't cover

* **Browser destinations**, as noted above.
* **Rises or drops in event volume.** Chord doesn't flag unusual spikes or dips.
* **Late delivery.** Chord doesn't flag events that arrive, but late.


---

# 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/notifications.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.