Delighted is the fastest and easiest way to gather actionable feedback from your customers. Use the feedback you gather from customers in all of your decision making processes. Send your feedback to your BI and data warehouses automatically.
This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.
This source is maintained by Delighted. For any issues with the source, you may contact their team.
This document was last updated on October 19, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!
- From your Segment UI’s Sources page click on “Add Source”.
- Search for Delighted within the Sources Catalog and confirm by clicking “Connect”.
- Give the Source a nickname and follow the setup steps to “Add Source”. The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be anything, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
- Sign in to your Delighted account and visit the Segment destination to connect.
- Once you connect with Segment you need to choose which ‘track’ events you’d like to use as triggers for surveys to be sent people. Then you can configure Delighted to send feedback back to Segment by following the next 2 steps.
- Enable the “Sync feedback to Segment” option.
- Copy the Write Key from your Delighted source within Segment and paste it into the provided box within Delighted
NOTE: We only send feedback back to Segment on surveys triggered from Segment initially. This ensures all feedback we send to Segment is identified and enriched with Segment information.
Delighted uses our stream Source component to send events to Segment. These events are then available in any Destination that accepts server-side events, including your data warehouse.
Below is a table of events that Delighted sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations.
Delighted always sends the values received from Segment for the
anonymous_id identifiers. All calls sent to Segment from Delighted will include the original value, Delighted never generates these.
Additionally, they also send
|Survey Question Answered||A user answered a question on a survey they received.|
Below are tables outlining the properties included in the events listed above.
|The Delighted identifier for the survey.|
|The name of the survey.|
|The type of the survey. For example, “NPS” or “CES”.|
|The medium used for the survey. For example, “Email” or “SMS”.|
|The name of the survey tool. This will always be “Delighted”.|
|The Delighted identifier for the question.|
|The name of the question.|
|The exact text shown to the user for this question.|
|A permanent URL to view the survey response on Delighted.|
|An array of tags added to the survey response in Delighted.|
|An array of notes added to the survey response in Delighted.|
|An object containing optional data attached to the survey. This will include all properties sent in the triggering “track” call.|
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.
If there are any issues with how the events are arriving to Segment, please contact the Delighted team.
Sending Data To Delighted
The Delighted Source works only when you also connect Delighted as a downstream destination within Segment. With the Delighted Destination, you can send Delighted user and event data, which you can use to trigger surveys. Head on over to our Delighted destination docs.
If you have any questions, or see anywhere we can improve our documentation, please let us know!