Skalin Destination

Skalin calculates your customer health score and alerts you as needed. This allows you to be more proactive, save time, and generate more revenue.

This destination is maintained by Skalin. For any issues with the destination, contact the Skalin Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for Skalin in the Destinations Catalog, and select the Skalin destination.
3. Choose which Source should send data to the Skalin destination.
4. Go to the Segment integration page in the Skalin platform, and click Connect to create a configuration. Find and copy the API Key and and Skalin Client ID in the Segment connection section.
5. Enter the API Key and ClientID in the Skalin destination settings in Segment.

Supported methods

Skalin supports the following methods, as specified in the Segment Spec.

Page

Send Page calls to Skalin. For example:

analytics.page('myFeature')

Segment sends Page calls to Skalin as a feature.

Screen

Send Screen calls to Skalin. For example:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Segment sends Screen calls to Skalin as a feature.

Identify

Send Identify calls to Skalin. For example:

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

Optionally, you can provide your CustomerID:

analytics.identify('userId123', {
  email: 'john.doe@example.com',
  trait: {
      groupId: 'myCustomerID'
  }
});

Segment sends Identify calls to Skalin as an identity.

Track

Send Track calls to Skalin. For example:

analytics.track('myFeature')

Segment sends Track calls to Skalin as a feature event.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

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, Engage 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), Engage sets that value to false.

When you first create an audience, Engage 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.

Settings

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