Skip to main content
Track.co (Track CXM) is a Brazilian customer experience management platform focused on Net Promoter Score (NPS) and other feedback surveys. It lets companies distribute surveys across multiple channels, collect responses, and analyze customer satisfaction. The connector extracts the survey interactions (responses) collected on the platform.

​
Configuring Track.co as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Track.co option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need a Track CXM API Bearer token and your Organization UUID for this connection. Generate the token in the Track CXM platform under your account’s integration/API settings, and copy the UUID of the organization you want to extract data from. The following configurations are available:
  • Auth token: The Bearer token used to authenticate against the Track CXM API.
  • Organization UUID: The UUID of the Track CXM organization to extract data from.
  • Start Date: The earliest date from which records will be synced, based on the interaction answer date. Records answered after this date will be extracted from the source.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).
The Track CXM API is updated only at the end of the day, so the most recent data available is from the previous day (d-1).
The Track CXM API accepts at most a 3-month range per request. The connector handles this automatically: it splits the full history (from your Start Date to today) into consecutive 3-month windows and, on each run, only fetches records answered after the last synced one. You do not need to create a separate stream per quarter.
Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

​
Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.

​
Fields by stream

Below you’ll find all available data streams from Track.co and their corresponding fields:
Survey interactions (responses) collected on the Track CXM platform. This stream is synced incrementally using the answered_at field.Key Fields:
  • uuid - Unique identifier of the interaction
  • answered_at - Date and time the customer responded to the survey (incremental replication key)
  • health_score - Health score associated with the interaction
  • answer_channel - Channel used by the customer to respond to the survey
Survey:
  • survey_uuid - Unique identifier of the survey the interaction belongs to
  • survey_name - Name of the survey
  • survey_public_hash - Public identifier (hash) of the survey
Customer:
  • customer_uuid - Unique identifier of the customer who answered the survey
  • customer_name - Name of the customer
  • customer_email - Email address of the customer
  • customer_phone - Phone number of the customer
  • customer_identifier - Customer identifier within the Track CXM platform
  • customer_metadata - Additional customer attributes from the imported distribution file (JSON array)
Distribution:
  • distribution_uuid - Unique identifier of the distribution the interaction belongs to
  • distribution_channel - Channel used to send the survey (e.g. email, SMS, WhatsApp, widget)
  • distributed_at - Date and time the survey was sent to the customer
  • distribution_public_hash - Public identifier (hash) of the distribution
Answers and Categorization:
  • answers - Answers given by the customer (array of objects), each with uuid, item_type, question, answer, comment, public_hash, and created_at
  • categories - Categories associated with the interaction (array of objects), each with uuid, name, value, display_text, and created_at
  • metadata - Additional interaction attributes from the imported distribution file, as a JSON array of key/value pairs

​
Skills for agents

Download Track.co skills file

Track.co connector documentation as plain markdown, for use in AI agent contexts.