This guide is intended to help you connect segment.io and Totango.
Segment.io is a customer data hub through which you can send your data from any device or platform. Segment.io translates and forwards it to your apps in a language they understand
Since Totango is all about identifying users, it is important to add a few API calls to your segment implementation with the exact information Totango needs. We’ll show you how.
Overview:
As part of setup, remember that every page, track and identify call that you want to show up in Totango must be tied to a groupId (defined in Totango as the Account ID). This is done via the group call. You must include context.groupId in every call you want to be sent through to Totango so our system can link the groupId in a call made to Segment with the associated account in Totango.
For our client-side/front-end Javascript library (Analytics.js):
Sending Account data is done via the group call and pushes account attribute data to Totango.
Sending Usage data requires an identify and group call before sending the usage data to Totango via a track or page call.
For server-side/back-end/session-less and mobile libraries:
You only need to call group or identify once per session as we will cache it and attach it to future calls to other methods for the same account. Please note that if the user and/or both the user and account change, you will need to update the userId and context.groupId via the identify and group calls again.
Sending Account data is done via the group call and pushes account attribute data to Totango.
Sending Usage data requires an identify and group call before sending the usage data to Totango via a track or page call.
See code specific code examples below.
Activity Tracking (Front End Integration)
analytics.identify([user ID], {
email: [user email],
name: [user name],
}).group([account ID], {
name: [account name],
}).track([action],{
category: [module]
}).page(["__heartbeat"]);
}}();
Activity Tracking (Backend Integration) - Option A
[app object].analytics.track({
userId: [User identification],
event: [Action name],
properties: {
category: [Module name]
},
context: {
groupId: [Account identification]
}
}
Activity Tracking (Backend Integration) - Option B
[app object].analytics.page({
userId: [User identification],
name: [Action name],
category: [Module name],
context: {
groupId: [Account identification]
}
});
Attribute Tracking
[app object].analytics.track({
userId: [User identification],
[Attribute name]: [Attribute value],
context: {
groupId: [Account identification]
}
}
analytics.track({
userId: 'User ID',
event: 'action',
properties: {
"category": "module”,
//account attributes
"revenue": 19.95,
"numLayers": 10
},
"context": {
"groupId": 'Account ID',
"traits": {
//user attributes
"email": "a@a.com",
"age": 23
}
});
In Segment, navigate to Integrations → Totango and, under options, enter your service ID for Totango. You can find your Service ID under Global Settings » Integrations Hub » Javascript Console in Totango.
Start using your application to trigger the usage data to be sent to Totango and monitor that in the Developer Console.