1. Add your Track CXM access
- In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the Track CXM option from the list of connectors.
-
Click Next and you’ll be prompted to add your access:
- Organization ID: Your organization identifier within Track CXM.
- Auth token: Your token used to authenticate requests to the Track CXM API.
- Distribution type: Whether Nekt should create regular or LinkList distributions.
You need an API Integration in order to obtain your authentication token. - Click Next.
2. Select your catalog tables
-
The next step is letting us know which tables contain the data that can be used to create the distributions on Track CXM.
Tip: The table can be found more easily by typing its name.
Regular distributions
Regular distributions
Check more details in the Track CXM API docs.
| Field | Required | Type | Notes | |
|---|---|---|---|---|
survey_uuid | Yes | UUID string | ||
distribution_channel | Yes | String | Allowed values: email, smslink, whatsapp | |
reminder_channel | No | String | Allowed values: email, smslink, whatsapp | |
distribution_name | No | String | ||
schedule_at | No | Integer | Unix timestamp | |
validity_at | No | Integer | Unix timestamp | |
reminder_at | No | Integer | Unix timestamp | |
is_anonymous | No | Boolean | False by default | |
template_invite_hash | No | String | Hash of template type invite. | |
template_reminder_hash | No | String | Hash of template type reminder. | |
template_expired_hash | No | String | Hash of template type expired. | |
template_thanks_hash | No | String | Hash of template type thanks. | |
import_lines | Yes | Array of objects | Each objects should contain interaction data, such as name, email, phone and others. | |
whatsapp_template | Conditional | Object | Required for WhatsApp distribution. | |
whatsapp_template.name | Yes | String | , | |
whatsapp_template.language | Yes | String | Example: en_US | |
whatsapp_template.variables | Yes | Array of strings | ||
whatsapp_template.id_provider | Yes | String | Template ID, ask Track support team. | |
whatsapp_integration_uuid | No | UUID string |
LinkList distributions
LinkList distributions
Check more details in the Track CXM API docs.
| Field | Required | Type | Notes |
|---|---|---|---|
survey_uuid | Yes | UUID string | |
distribution_name | No | String | |
validity_at | No | Integer | Unix timestamp |
async | No | Boolean | |
shortened_link | Yes | Boolean | |
callback_url | Conditional | URL string | Required if async is true. |
template_survey_expired_hash | No | String | Hash of template type expired. |
template_survey_thanks_hash | No | String | Hash of template type thanks. |
import_lines | Yes | Array of objects | Each objects should contain interaction data, such as name, email, phone and others. |
- Click Next.
3. Configure your Track CXM destination
- Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
- To define your Trigger, consider how frequently you need to have the data updated on the destination (every day, once a week, only at specific times, etc.).
- Click Done.
Check your new destination!
- Once completed, you’ll receive confirmation that your new destination is set up!
- You can view your new destination on the Destinations page. Now, for you to be able to see the distributions on Track CXM, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your distributions should be seen on Track CXM.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!