ClientSuccess quick info
This destination is maintained by ClientSuccess.
Getting Started (for CSMs)
If your engineers have already set up Segment, adding Segment data to ClientSuccess is straightforward. All you need to do is turn on the destination.
To turn on the destination, do the following:
- Go to the Segment destinations catalog and enable ClientSuccess.
- Add your
ClientSuccess Source Idand
ClientSuccess API Key(these can be found within ClientSuccess under the top right menu, Apps & Integrations > Usage).
Note: Because ClientSuccess focuses on group level events, you must pass group information before your events will show up. If you turn on the ClientSuccess destination in Segment and don’t see events in ClientSuccess after 24 hours, it may be that your engineers need to send group information to Segment using Segment’s
Getting Started (for Developers)
ClientSuccess supports the
page methods of Segment.
group method is required for any data to stick in ClientSuccess. Any
page events fired before the
group method is called for a particular user, will be lost.
identify a user, Segment will pass that user’s information to ClientSuccess with
userId as an external user Id for ClientSuccess usage. ClientSuccess uses the following of Segment’s standard user profile fields (in parentheses):
All other traits will be sent to ClientSuccess as custom attributes and may be ignored.
track an event, Segment will send that event to ClientSuccess as a custom event.
When you track a
page event, Segment will send that event to ClientSuccess as a custom event.
When you call
group, Segment will send that group’s information to ClientSuccess with
groupId as the id and
name as the group name. Both
name are required for ClientSuccess.
For user-property destinations, an 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, Personas 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), Personas sets that value to
When you first create an audience, Personas 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.
Supported Sources and Connection Modes
Segment offers an optional Device-based Connection Mode for Mobile data going to ClientSuccess, so that you can use ClientSuccess features that collect data directly from the mobile device. To do this, you must package the Segment-ClientSuccess mobile SDK with the Segment mobile library.
Segment lets you change these destination settings from the Segment app without having to touch any code.
|Direct Integration Channels||
The channels this direct integration supports.
|Direct Integration Endpoint||
The API endpoint of the direct integration.
This page was last modified: 20 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!