> 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/destinations/email-and-marketing/delighted.md).

# Delighted

**Delighted** is a customer experience platform that helps businesses collect, analyze and act on customer feedback using Net Promoter Score (NPS), CSAT, CES and more. It sends surveys by email, web, SMS and other channels. This destination creates people in Delighted from your Chord events, which can trigger surveys.

## Getting started

You need your account-specific Delighted API key.

1. Log into your Delighted account and click **Integrations** in the top ribbon.
2. On the Integrations page, select **API**.
3. Copy the key titled **Your API Key**.

![The Integrations tab in Delighted](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-36c8d10db06af3887431e48ea16d09eb6cb62125%2Fdelighted-integrations-tab.png?alt=media)

![The API option on the Integrations page](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-36e37aa15fa7b2b8cbf0fd4278a7e3e9783d144c%2Fdelighted-api-option.png?alt=media)

![The API key field on the API documentation page](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-f7abf3c6ddd8b1ee1a961932827dea6e34c7a1ff%2Fdelighted-api-key.png?alt=media)

## Settings

* **Destination Name** (required): a name to tell this destination apart.
* **API Key** (required): your Delighted API key.
* **Delay** (optional): the delay, in seconds, before Delighted sends the survey.
* **Consent Requirements** (optional): the consent categories a visitor must accept before Chord sends data to this destination. See [Consent](/activate/event-streaming/consent.md).

## Connect

Add **Delighted** from the destination catalog, using the settings above. See [Connect a destination](/activate/event-streaming/connect-a-destination.md) for the full steps.

## Event mapping

Not all Chord events are used by Delighted. The events the [Delighted API](https://app.delighted.com/docs/api/sending-to-people) uses are:

| Chord event      | Delighted event                             | Notes |
| ---------------- | ------------------------------------------- | ----- |
| All track events | `person.create` (survey is sent by default) |       |
| `identify`       | `person.create` (no survey sent)            |       |

**There is no event filtering in the Delighted destination.** Chord processes all `track` and `identify` events regardless of event name. A `track` event creates a person in Delighted and triggers a survey. An `identify` event, by default, creates a person in Delighted but does not send a survey. Chord rejects other event types, such as `page`, and retries them.

## Person fields

| Chord source (priority order)                                | Delighted field | Notes                                                                                                                 |
| ------------------------------------------------------------ | --------------- | --------------------------------------------------------------------------------------------------------------------- |
| `properties.email` > `context.traits.email` > `traits.email` | `email`         | Chord sends no phone number, so the person's email is the only contact detail                                         |
| First name and last name, joined                             | `name`          | First name: `properties.first_name` > `context.traits.first_name` > `traits.first_name`. Last name works the same way |
| The **Delay** setting                                        | `delay`         | In seconds. Defaults to `0`                                                                                           |


---

# 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/destinations/email-and-marketing/delighted.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.