Kustomer Destination

1. From the Segment web app, click Catalog.
2. Search for "Kustomer" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. If this is the first time setting up Kustomer as a destination, you'll need to install the Segment App in your Kustomer Account.
4. In your Kustomer account, go to Settings > Apps Directory and install the Segment App.
5. After installing the Segment App, you need to go to the Segment App Settings Page listed directly underneath the Apps Directory page. From this page you will need to click the large green "Enable with Segment" button.

NOTE: Kustomer stores anonymous activity for 30 days but you will not see this activity in their UI unless the customer is identified using the Identify call.

If you're not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:

1
analytics.page('Pricing', {
2
  title: 'Segment Pricing',
3
  url: 'https://segment.com/pricing',
4
  kustomer_session_id: 'abc123'
5
});

Page calls will sent as a tracking event to Kustomer on the timeline of the customer who was tracked. If the kustomer_session_id is included, it will cluster this tracking event into a single "session" on the customer's timeline. If no kustomer_session_id is supplied, we will automatically generate session IDs based on time between tracking events. (Read why Segment doesn't have session tracking on the Segment blog).

If you're not familiar with the Segment Specs, take a look to understand what the Screen method does. An example call would look like:

1
[[SEGAnalytics sharedAnalytics] screen:@"Home"
2
properties:@{ @"kustomer_session_id": @"abc123" }];

Screen calls will sent as a tracking event to Kustomer on the timeline of the customer who was tracked. If the kustomer_session_id is included, it will cluster this tracking event into a single "session" on the customer's timeline. If no kustomer_session_id is supplied, we will automatically generate session IDs based on time between tracking events. (Read why Segment doesn't have session tracking on the Segment blog.)

If you're not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com'
3
});

Identify calls will be sent to Kustomer which will create or update a standard customer object record. If a record with a corresponding userId exists, that record will be updated. If a customer record doesn't already exist, a new customer record will be created.

All of the overlapping attributes in the Segment traits documentation are mapped to standard Kustomer attributes by default. In addition to the Segment traits, the following attributes are automatically mapped from Segment to Kustomer:

If you're not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

1
analytics.track("Registered", {
2
  plan: "Pro Annual",
3
  accountType: "Facebook",
4
  kustomer_session_id:"abc123"
5
});

Track calls send as a tracking event to Kustomer on the timeline of the customer who was tracked. If the kustomer_session_id is included, it clusters this tracking event into a single "session" on the customer's timeline. If no kustomer_session_id is supplied, Segment automatically generates session IDs based on time between tracking events. See why Segment doesn't have session tracking.

The Kustomer destination only accepts standard properties such as name, email, and phone. It doesn't support custom properties. Any Audience or Computed Trait created in Engage is considered a customer property by Kustomer destination and isn't supported.

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