Trackier Destination

On this page

Trackier 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, please reach out to their team.

NOTE: The Trackier Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on May 14, 2019. If you are interested in joining their beta program or have any feedback to help improve the Trackier Destination and its documentation, please let their team know!

Getting Started

The first step is to make sure Trackier supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

Web Mobile Server
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Trackier” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your Trackier dashboard Profile section -> Global Security Token


If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

  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


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.


Segment lets you change these destination settings from your Segment dashboard without having to touch any code.


Go to profile and copy and paste the Global Security Token here.

Adding Trackier to the integrations object

To add Trackier to the integrations JSON object (for example, to filter data from a specific source), use one of the following valid names for this integration:

  • trackier

  • Trackier

This page was last modified: 21 Nov 2019

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account