Delighted

6 min

Introduction

Delighted is a customer experience platform that helps businesses collect, analyze, and act on customer feedback using tools like Net Promoter Score (NPS), CSAT, CES, and more. It enables companies to send surveys via email, web, SMS, and other channels, and provides real-time insights to improve customer satisfaction and loyalty.

Getting started

To properly use Chord's Delighted destination, your account-specific Delighted API key must be provided.

API key

To find this key, follow the guidelines here:

Log into your brand's Delighted account and click on Integrations in the top ribbon

On the Integrations page, select API

Copy the key titled Your API Key

Navigate to Integrations Page

Select the API option

Connecting to the Delighted CDP Destination

Copy Your API Key

Connecting to the Delighted CDP destination

Log into the Chord data platform.

Navigate to the CDP.

Click the "Add" button next to Destinations.

Select Delighted from the destination catalog.

Enter in the destination name, the API Key and the Delay amount (if applicable)

Click "Create" to connect.

Chord events relevant for destination

Not all Chord Tracking events are used downstream in your configured destinations. The most relevant and important events in the Chord tracking plan are mapped within the CDP destination, relayed and then ingested in the destination. The Chord tracking plan events used by the Delighted API are:

Chord Tracking Event	Destination Event
All track events	person.create (survey is sent by default)
Identify	person.create (no survey sent)

Note: There is no specific event filtering within the Chord Delighted destination. All Chord track and identify events are processed regardless of the event name. Chord track events create a person in Delighted and triggers a survey to be sent. Chord identify events, by default, create a person in Delighted but does not send a survey.

Before connecting destinations in the Chord CDP, please verify with all Destination owners that all non-Chord CDP configured destinations are disabled. Running external destinations alongside configured Chord CDP destinations can result in duplicate events downstream.