Skip to content

Utilize your customer experience data

This chapter describes how you can fetch data from and use it to show customer experience data to the users of the system.

NPS Feedback App

The feedback app is built as an easy way for systems to visualize customer responses data to the users. Not all system has the functionality to use the Feedback App. In this case, go to the next chapter.

To see more technical documentation on the Feedback App please click here.

If you want to see how it is used in our Dixa integration click here.

Below is an example of the Feedback App:

Feedback App

Get data with our API

With data back we refer to a third-party system consuming data from and displaying it to its user. The complexity of how to display data from depends on the functionalities available in the system.

Below is the flow from triggering a survey to retrieving the response back into the system:

Get data flow

To retrieve data from to use for an external system our API gives you several solutions.

For adding responses directly to other systems use the following endpoint:

GET responses (all campaigns):

Use our /bi/ endpoints

Many of our customers are retrieving data to their data warehouse to use the data from there. Here a mix of our v2/bi/ endpoints can be used to retrieve the data you need.

Often a combination of the endpoints below are used as, for example, the campaign member endpoint contains the custom data field which is often used to map meta data on a respondent when added to from an external system.

GET responses:

GET Campaign members:

GET Campaign:

GET Employee:

GET Response categories:

Unique identifiers

To combine data from the different /v2/bi/ endpoints you can use unique identifiers.

  • Use campaignMemberId as the unique identifier to combine data between the campaign member and the response
  • Use employeeId to combine data between the campaign member and the employee.
  • Use campaignId to combine data between the campaign member and the campaign.
  • Use categoryId to combine data between the response and the category.


Get responses with a webhook

To retrieve data from an account you can create a webhook subscription.

Here is an example on how a "create webhook subscription" could look like:

curl --location '' \
--data '{
    "action": "Create",
    "model": "Response",
    "url": "",
    "filter": {
        "include": {
            "campaignId": 1234
        "exclude": {
            "id": 1232345125

"Create subscriptions" uses the following endpoint:
  • action: this is the database operation
  • model: this is the database entity
  • url: a POST request is sent to this URL
  • filter: the purpose of filter is to include or exclude certain webhook calls when a database operation has occurred
  • include: decides what criteria you want to INCLUDE in your webhook subscription
  • exclude: decides what criteria you want to EXCLUDE in your webhook subscription

Above subscription example listens to created responses on a campaign with the ID "1234" and excludes responses with responseID "1232345125".

After creating the webhook subscription, these conditions will trigger webhook calls from that point on. Every time these conditions are fulfilled, a POST request will be sent to the URL given. In above example the URL is "".

For more information on how to create a webhook subscription click here.

For more information on other webhook endpoints click here.

Data by campaign

In your campaign builder you can use webhooks to listen to specific campaigns.

If your system does not provide you with an API you can retrieve responses with a webhook in Please read the this guide.