---
title: CDP Notifications (Event Alerts)
slug: cdp-notifications-event-alerts
createdAt: 2025-08-22T14:33:11.058Z
---

# Overview

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

Use them as an early warning system, so you can catch issues quickly and trust that your data is complete.

:::hint{type="info"}
**No support for client-side destinations**: Chord does **not **provide monitoring for events sent directly from the browser to external tools (e.g., client-side destinations), since these events do **not **pass through the CDP.
:::

## Notification types

The Notifications tab has three sections. Each one offers different notification types.

| **Section**  | **Notification type** | **You're notified when**                                       |
| ------------ | --------------------- | -------------------------------------------------------------- |
| Sites        | No data received      | No events are received from the site for a set period of time. |
| Connections  | Delivery failures     | Events fail to deliver to the destination.                     |
| Connections  | Function errors       | User-defined functions on the connection throw errors.         |
| Connections  | Modified or deleted   | The connection is modified or deleted.                         |
| Destinations | Modified or deleted   | The destination is modified or deleted.                        |

![Chord CDP Notifications setup page]()

:::hint{type="info"}
**Note: **You will not receive an email confirming that the issue has been resolved. Once you receive an alert and resolve it, you will not receive any additional alerts (unless the source or destination error persists or occurs again).
:::

# Getting Started

## Requirements

- Your sites (sources) and destination connections must be instrumented on Chord CDP.
- You must have appropriate permissions to access alert configurations.

## Choosing what to monitor

The right setup depends on which data your brand relies on most. Start with the sites and connections that would hurt most if they stopped working, then add more as needed.

| **If this matters to you**                                                                              | **Turn on**                                                   |
| ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
| Ad platforms, email, or SMS tools that drive revenue (for example, Facebook Conversions API or Klaviyo) | **Delivery failures** on those connections                    |
| Connections that use user-defined functions to transform or filter events                               | **Function errors** on those connections                      |
| Your main storefront or app sending events steadily                                                     | **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 or team alias, not one person, so nothing is missed when someone is out.
- Sites with long quiet periods (for example, a low-traffic test site) may trigger alerts that aren't real problems. Skip them or route them to a lower-priority inbox.

## How notifications are sent

- **Issue alerts are checked every hour.** This covers no data received, delivery failures, and function errors. When Chord detects an issue, it emails every address on that notification.
- **One email per issue every 24 hours.** If the issue continues across multiple hourly checks, you get one email per notification each 24 hours, not one per check. This keeps alert fatigue down.
- **Lifecycle notifications are sent immediately.** Modified or deleted notifications go out as soon as the change happens.
- **No resolution email.** Chord does not email you when an issue is resolved. Once it's fixed, alerts stop unless the issue happens again.

Each email includes a summary of the issue. For detailed error information, go to the Live Events page in Chord CDP.

## Set up a notification

**Before you start:** your sites and connections must already be set up in Chord CDP, and you need permission to manage notifications.

1. Log into the Chord data platform and go to **Chord CDP**.
2. Click the **Notifications** tab.
3. Find the section you want (**Sites**, **Connections**, or **Destinations**) and click **+ Add Notification**.
4. Select the site, connection, or destination from the dropdown.
5. Enter one or more email addresses. Separate multiple addresses with commas.
6. Under **Notification types**, check each type you want.

::Image[]{size="60" isUploading="false" position="center" darkSrc="https://archbee-image-uploads.s3.amazonaws.com/TmutqdeXiIw-V3gBZXVjd/D8zYAwU2JofRaWPqvQdK8_screenshot-2026-10-14-at-35431-pm.png" darkWidth="1185" darkHeight="861" alt="Add Connection Notification - Example" showCaption="false"}

7. Click **Save**.

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

## Remove a notification

On the **Notifications** tab, find the notification and click the trash icon on the right.

## What notifications do not cover

- **Client-side destinations.** Events sent directly from the browser to an external tool do not pass through Chord CDP, so Chord can't monitor them.
- **Spikes or drops in event volume.** Notifications don't flag unusual increases or decreases in source events.
- **Delivery delays.** Notifications don't flag events that deliver successfully but late.