Track NPS

Overview

Birdie allows you to connect your Track NPS account so that survey responses can be ingested and analyzed alongside your other feedback sources.

Requirements

To connect Track NPS to Birdie, you need:

• An active Track NPS account with access to the Apps area.

• Permission to install the API v2 app and create or access an API token that Birdie will use as the access token for the connector.

Setup in Track NPS

1

Access Apps

Once you're logged in, access your User menu and choose the option Apps.

User menu → Apps

2

Install API v2

In the Apps page, click on "Instalar API v2".

Install API v2

3

Create or Select a Token

Select an existing token or create a new one. Birdie will use this token value as the Access token when setting up your Track connector.

Select or create token

Connect to Birdie

After you have selected or created a token in Track NPS, securely share this token with the Birdie team. Birdie will configure the connector using this value as the access token and confirm once data is flowing.

Data in scope

Birdie connectors, by default, will skip any columns containing PII or sensitive data. NPS/CSAT responses will be ingested along with anonymized user and company IDs only.

Birdie connector for Track NPS will ingest:

• answer_id

• answer_date

• survey_type: nps or csat

• rating: answer score

• comment: answer comment

• account_id (optional): some ID to reference the client

• [custom fields] (optional): List of fields defined by the client to be used as filter for analysis

Along the ingestion pipeline, the first step detects, replaces and discards any PII or sensitive information existing within the comment field.