This preview of pull request 1639 is meant for internal use only.

Delighted Destination

Delighted quick info

Delighted accepts Track, and Identify calls. If you reference it in the Integrations object, call it “Delighted”.

Delighted accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.

Delighted is the modern customer feedback solution used by the world’s most coveted brands to deliver stellar experiences to their customers.

This destination is maintained by Delighted. For any issues with the destination, contact the Delighted Support team

NOTE: The Delighted Destination is currently only compatible with email surveys.

Getting Started

Before you start, make sure Delighted supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️ ⬜️
☁️ Cloud-mode
  1. From the Segment web app, click Catalog.
  2. Search for “Delighted” in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. In the destination settings, enter your Delighted “API Key” in Segment’s Settings UI. You can retrieve this from your Delighted Settings > API > Your API Key. It should look like “T8jtGnuYaNerDedVMYrcgn1dRdywfGOl”.
  4. If you’re using Segment’s client-side analytics.js library, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Delighted’s Javascript library onto the page and begins sending data.

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'required@email.com',
  plan: 'free',
  language: 'EN'
});

Identify calls will add to your list of People in Delighted. The only trait that is required by Delighted is email. All additional traits will be added to Delighted surveys as metadata (Delighted calls this metadata Properties) which you can use to segment feedback.

Track

If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('Purchased Product');

Track calls will trigger a Delighted survey if you have configured the event name in your Delighted dashboard to appear exactly as the event name in your Track call.

This also enables you to define the “Sample Rate” and an optional “Delay” for the triggered surveys.

trigger-delighted-surveys-segment

NOTE: Delighted has built in protections for over surveying called Survey Throttling. This will ensure the same person won’t be surveyed more than once per month (adjustable in your Delighted account settings). Survey Throttling provides you peace of mind so that you can use frequent track calls like purchase or contact events.

Sending data from Delighted back to Segment (optional)

You can optionally configure Delighted to send feedback from Delighted email surveys to Segment. This can be useful for data warehousing, forwarding to other services (such as email marketing automation tools), or performing further analysis with the BI tools you have connected to Segment.

Simply copy the Write Key of the Segment Source where you want to send data and paste into the Delighted Segment Destination page.

Delighted will then send all email survey feedback triggered using the Segment integration into back into Segment. Refer to our Delighted Source documentation for more information.

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Key

To connect Delighted with Segment, all you need is your Delighted API Key

This page was last modified: 20 Oct 2020



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account