Tractionboard Destination

Getting Started

Once the Segment library is integrated in your app, toggle Tractionboard on in your Segment destinations, and add your Segment Token ID which you can find in the Tractionboard Dashboard, under the Settings > Integrations.

The Segment Tractionboard destination is 100% handled through our side, you just need to take some names in consideration when sending track events.

Tractionboard supports the page, identify, track, group, alias and screen methods.


The Page method is equivalent to our visit event, which track your user iterations inside your website and app.


When you identify a user, we’ll pass that user’s information to Tractionboard with userId as Tractionboard’s External User ID, as if it were our login event. Segment’s special traits will be recognized as Tractionboard’s attributes, and you can use as many as you want.


When you track an event, we will send that event to Tractionboard as a custom event. There are certain events that trigger special actions in Tractionboard:

  • Payment Made: This is an standard event in Segment (Payment Made), and it’s translated to the Tractionboard payment event, that is used to get the earnings of certain user.
  • Refund Received: This is an standard event in Segment (Refund Received), and it’s translated to the Tractionboard refund event, that is used to subtract this amount to the revenue.
  • cancel: This event with the userId will update the user status to canceled, and it will count in the churn rate metric.
  • signup: We expect the signup event with the userId. Signup events are used to compose the UAC metric.


The information provided by this method will be saved as a user’s attribute.


With this method we will change the id to a certain user saving the old one as a attribute of the new one.


It’s the same that the page method. Currently we don’t support mobile apps, but we can get events from them.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, contact us 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.

Supported Sources and Connection Modes

The first step is to make sure Tractionboard 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

To learn more about about Connection Modes and what dictates which we support, see here.

Segment offers an optional Device-based Connection Mode for Mobile data going to Tractionboard, so that you can use Tractionboard features that collect data directly from the mobile device. To do this, you must package the Segment-Tractionboard mobile SDK with the Segment mobile SDK.


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

Token ID

You can find the Token ID in the Tractionboard Dashboard under the Settings > Integrations.

This page was last modified: 22 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