# Trackier Destination

## Destination Info

* Accepts [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **trackier**, **Trackier** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[Trackier](https://trackier.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is customisable performance marketing software used by ad networks, agencies and advertisers to manage publisher relations.

This destination is maintained by Trackier. For any issues with the destination, [contact the Trackier Support team](mailto:support@trackier.com).

## Getting Started

1. From the Segment web app, click **Catalog**.
2. Search for "Trackier" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the "API Key" into your Segment Settings UI which you can find from your Trackier dashboard Profile section -> Global Security Token

## Track

If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/segment/connections/spec/track/) does. An example call would look like:

```text
  analytics.track("Item Sold", {
    click_id: '1233443',
    sale_amount: $12.54,
    txn_id: 'random',
    goal_id: '123234',
    goal_value: 'goal name'
  });
```

**NOTE:** `click_id` is a required property while all other properties in the example above are optional.

Track calls will be sent to Trackier as a `track` event. Some optional properties you can include are:

* `sale_amount`: for tracking product sales value, is used in reporting profit
* `txn_id`: unique transaction ID, set the default value as 'random' to track upsells on a single click
* `goal_id`: unique constant id for each campaign goals
* `goal_value`: short name for goals

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Trackier  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field   | Description                                                      | Required | Type   |
| ------- | ---------------------------------------------------------------- | -------- | ------ |
| API Key | Go to profile and copy and paste the Global Security Token here. | Yes      | string |